Windows 10: Keeps connecting to an open WiFi that's not on the "known" list

I've got a weird problem I can't figure out:

New Surface Book running Windows 10. Every time it boots, it connects to "xfinitywifi" (an open WiFi access point apparently belonging to a neighbor). This AP has "limited connectivity", though, so no internet access (and I don't want to be connected to it, anyways!).

I've previously connected to my home WiFi, and this is the only network listed in my "Manage known networks" list. When I manually "disconnect" from xfinitywifi, Windows automatically connects to my home WiFi. For some reason, though, on boot up, it automatically connects to this open network (despite being set to NOT connect to open networks), and it prefers this open network over my (secured) known network.

I have disabled the "Wi-Fi Sense" "feature".

Any ideas?

:)

 

Enter on keypad " no. + # "

petrib is correct. It is a shortcut to SIM numbers.

Numbers on your SIM might not be in the position you think. Just because they appear sorted in alphabetical order in the contacts list doesn't mean that they appear in that same order on the SIM. On the SIM they appear in the order in which you input them,
unless you delete a number in which case the next one entered takes its place.

 

Enter on keypad " no. + # "

Hello guys :smileyhappy:

There's something make me crazy :s
When I click a certain number on keypad on any NOKIA mobile
Then click the symbol " # ", then a number of
a contact "in my contact list" will be appeared.
Is there anyone know how is that???
I feel curious toward this puzzle :smileyvery-happy:
OK., if anyone know about this topic, please tell me :smileysad:
Anyway thanks :smileywink:

 

XfinityWifi does not belong to anyone but Comcast. If you look up at the wire runs for Comcast, you will see a rectangular gray box. That is a Access Point that Comcast is using to allow their footprint to be expanded. On their leased equipment, they use two VLAN's for Guest access with a username and password with the providers that are allowed to use that connection. One is Xfinitywifi, the other is CableWifi.

There really is no such thing as a Known list. Windows 10 will only list those Access Points that it sees within the range of the device. If you are not connecting to your Gateway, then either you have poor signal, or somehow the wifi got turned off.

Can you connect to it with Ethernet and check to see if WiFi is turned on? If this is equipment that you are leasing from Comcast, I would take it in and get it swapped out. Or even better, just purchase your own equipment and save yourself some money in the long term.

This explains the alliance that is working together to allow users leased equipment to be used for public hotspots, and also the Gray Access Points up on poles are public Hotspots. Cable WiFi | Internet access brought to consumers through a collaboration among U.S. Internet service providers

Access the Internet Using XFINITY WiFi Hotspots

 

Sorry, I might not have been clear:

-I do not have Comcast. I own my own WiFi access point. WiFi is on and working. No problems.

-When I boot up, Windows automatically connects to "xfinitywifi". When I manually disconnect from xfinitywifi, Windows automatically connects to my home WiFi network (let's call it "home-wifi"). I don't even have to click on "home-wifi" and press connect - Windows remembers that I've previously connected to "home-wifi" and just automatically connects to it as soon as I disconnect from "xfinitywifi"

-I do not ever want to connect to "xfinitywifi". I want to always connect to "home-wifi".

-There is a "Manage Known Networks" option in "Network and Internet" \ "WiFi" \ "Manage WiFi Settings". Only "home-wifi" is listed here.


Somehow, despite me NEVER having chosen to connect to "xfinitywifi", Windows connects to it every time I boot.

 

There is a way to blacklist SSID's

Open an elevated PowerShell and paste this code into it

Code: netsh wlan add filter permission=block ssid="SSID-of-Black-listed-Network" networktype=infrastructure[/quote] Edit:
I just noticed Brink made a Tutorial about this
https://www.tenforums.com/tutorials/3...dows-10-a.html

 

Clear about what. You were clear enough that you have a problem and that you are connecting to Comcast's hotspot. If you do not own the equipment and cannot go in to turn on Wifi, take the leased equipment back into the Comcast Walk-in Center and walk out with a new eMTA.

There is also no such thing as Known Networks. All that Wifi will list, is available hotspots that the radio in the wifi card can pick up.

 

[/quote] They do not want to black list anything, because that is not the issue. The XfinityWifi and CableWifi are public hotspots for customers with Comcast and other affiliates that can use those hotspots in areas that are served. Black listing the Xfinitywifi & CableWifi hotspots will actually break their wifi, not fix it.

If Wifi is active on the eMTA, but not being picked up, others can be seen by the radio in the wifi, the problem is with the OP equipment. If leased, they need to take it back to Comcast and pick up a new one to replace the old one.

 

I feel like you're not reading what I wrote. I do not have Comcast. No service from them AT ALL. No cable. No xfinity. No box. No grey box on my house. Nothing. I have a DSL line from a local ISP that plugs into my personal access point.

 

Thank you You beat me to it.

Did you try my command

 

No, not yet. I appreciate the reply and will try it if no one has any other solutions.

I just don't get why this is happening, though. Why would Windows decide it's OK to connect to this? Perhaps trying to understand Windows is a fool's errand...

 

I am not going to sit here and go back and forth with you. Again if your equipment is not working and you are picking up the Comcast Public Hotspots, you have equipment problems.

Stop thinking that I did not read what you posted. The point is that you are ignoring what I posted and I am done explaining over and over that the problem is with your Gateway. There is most likely nothing wrong with Windows 10 or the Wifi radio, since it is picking up all available Hotspots that it can see.

Wifi works like your FM radio when you tune into a station. If you can pick up a station and hear it, that means that it is within enough range that you are able to hear it. If you get static or nothing, that means that either the signal is down or that you are too far out of range.

There is also no such thing as Known networks as I have stated already two times. You get a list of available Wifi networks and that is all that shows up in that list.

 

It will break their wifi. They need to not run that command. It will cause nothing but problems for the OP.

 

Who's Wifi the neighbours LOL it's not his wifi how on earth can blocking a Wifi SSID he does not want his computer to connect to that does not belong to him break something on his computer

 

If the name you gave in the first post is correct here is the command you need
Code: netsh wlan add filter permission=block ssid="xfinitywifi" networktype=infrastructure[/quote] To set it back the way it was do this
Code: netsh wlan delete filter permission=block ssid="xfinitywifi" networktype=infrastructure[/quote]
Edit:
I just noticed Brink made a Tutorial about this
https://www.tenforums.com/tutorials/3...dows-10-a.html