Windows 10: 10061 change wireless AP

Doesn't seem to want to let you see available SSIDs to enable you to choose. (dbl click wifi symbol in notifications). Fine in 10049 but my 10061 has regressed.

Anyone else see this?

:)

 

Cannot connect to any WiFi network anymore

Do not know if this is a dead thread or not, but I had the same problem. WP7 would refuse to connect to one of my wireless networks(when it had in the past). I reset the AP(access point), tried changing the password on the AP, turn off/on the wifi (on WP7),
deleted the wireless info for that AP from my phone, etc... What finally worked was removing the battery from my phone, waiting 30 seconds to 1 minute, put the battery back, turned on the phone and tried again. It connected without a hitch.



Cheers!

 

No Internet Connection

Well, this doesn't address your problems with the annoying message about having exceeded the number of allowable connections. But, I have solved my problem with downloading the Maps Guides.

I changed my default AP from my home wireless router to a 3G AP. Maps then retrieved the list of available Guides. I then switched the default AP back to my home router, and it connected and downloaded further info, prices, trial period, etc. w/o a hitch.

 

A few things on the task bar weren't working e.g. start menu and the wireless. I did an install from ISO and all seems to be as expected, now. Must say that the notifications etc are different with this ver.

 

They're moving stuff around ... in 10061 the Network flyout is back (and I'm guessing that the notification WiFi became redundant. Of course redundant never stopped MS before *Wink There must be 5 ways to do anything and everything.

Try this:
left click on the network icon in the system tray to see the available SSIDs - form there you should be able to dbl click to select the AP you want to connect.

 

Yes, certainly 'things' are being shifted around. Notifications are looking better each release, I think.

Something went wrong with my laptop upgrade, however. Saw another member had this problem, too. A clan install fixed it.

Glad my main machine upgrades have all gone well!