"Can't Connect to this Network" on Windows 10 Partition

Yes, Windows 10 on my Mac used to connect just fine. It worked for several months until just recently, when I posted this question.

WLANService is set to automatic.

Microsoft Windows [Version 10.0.14393] (c) 2016 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>netsh wlan dump # ---------------------------------------- # Wireless LAN configuration # ---------------------------------------- pushd wlan # Allow filter list # ---------------------------------------- # Block filter list # ---------------------------------------- popd # End of Wireless LAN Configuration C:\WINDOWS\system32>

Also, UPDATE:

After checking WLANService, I decided to try connecting to the internet again, even though nothing had changed since the last time I tried. Surprisingly, it was able to connect. I tried loading some webpages, but after a few minutes it started loading very slowly. Then it failed to load a page, and the Wi-Fi disconnected after a minute. I disconnected my phone from Wi-Fi (for an unrelated reason) and after a minute my computer reconnected. I don't know if these are related, though I don't think so, as I've since reconnected my phone and have had no issues. The computer disconnected once more while I was downloading some of the programs I had lost when I reset Windows. The computer went to sleep while downloading, and I saw it was disconnected when I signed in, but it reconnected after a moment. I tried the downloads again with no issue. I also noticed this appeared after I connected:

Though I'm not sure if I should download it or not. I'm concerned about that Wi-Fi update... Could installing it cause any more issues?

MacOS indicates my Broadcom driver version as Broadcom BCM43xx 1.0 (7.21.171.130.1a1).

My SSID is 2.4G.

In the properties page for the Broadcom 802.11ac Network Adapter on Windows 10:

20/40 Coexistance is Auto

40MHz Intolerant is Disabled

Band Preference is None

Bandwidth Capability is 11a:20/40;11bg:20MHz

Disable Bands is None

IBSS Mode is 802.11a/b Only

WZC IBSS Channel Number is 11(20MHz)

I'm not sure which (if any) of this information is relevant, so I've included it all.

Yes, it connects just fine. Here's everything listed under Network Adapters in the Device Manager:

Atheros AR8152/8158 PCI-E Fast Ethernet Controller (NDIS 6.20)

Microsoft Virtual WiFi Miniport Adapter

Realtek RTL8188CE Wireless LAN 802.11n PCI-E NIC

Okay. I have downloaded Windows Message Analyzer on Windows 10 on my Mac. I'm not sure if it requires a separate computer or not, but I can install it on my laptop if need be. After opening the program, I've found it to be a little more complicated than expected. Might you be able to point me towards a guide or something explaining what I need to do with this?

Okay. I've done that, and reset Windows, but it still doesn't work. I checked the driver version. It's 7.35.118.40 dated 7/24/2015. I don't recall what it was before. I connected to the internet via my iPhone's hotspot to check for driver updates, but it said it's up to date. Is 7.35.118.40 more recent than 7.35.118.73? That seems odd. The button to roll back the driver is grayed out and unclickable, but it was like that before resetting anyways. Sadly, resetting Windows doesn't seem to have solved anything.

A google search for my router model indicates that it is only 2.4G... Occasionally on Windows 10 I see my router name twice, the other one with a '1' after it, but I've never been able to connect to that one. I've never seen it on Mac OS or any other device connecting to Wi-Fi.

Update: Just tried uninstalling and reinstalling Bootcamp drivers. This, unfortunately, has not solved the problem either. However, I did notice something strange. I tried using the Bootcamp icon on Windows to restart in macOS (Which I have never done, I've always just restarted the computer and held down the alt key to switch between partitions) but it said 'cannot locate macOS boot volume.' Not that this is an issue I'm at all concerned about, as I can switch partitions just fine using the old method. I'm just wondering though, might this have anything to do with my problem? Maybe there's an underlying issue in Bootcamp itself responsible for all this?