Hello, use Registry Editor, go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet
and modify: EnableActiveProbing
then change "Value data" from "0" to "1"
and restart your computer
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am running on Windows 10 Enterprise, Version 2004, OS Build 19041.264.
I recently changed to the Windows Insider Program and updated Windows. In the taskbar, the Wi-Fi icon shows No Internet Access, but I have a stable internet connection wirelessly (Ex: I can browse the internet, ping IP Addresses, etc.). Another problem is when I try to open Cortana it also says that I have no internet connection (By the way, I can also open Microsoft's website).
As I know Windows checks internet connectivity with this URL: http://msftconnecttest.com/connecttest.txt. But this gives Error 404, File Not Found. Maybe it is because of this?
If you know the problem or an answer, please help. Thanks!
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I just wanted to reiterate the solution to this issue, at least for me.
It appears that some privacy tools that worked perfectly in 1903/1909 don't work as intended in 2004. Once I removed a particular NCSI setting (set by a privacy tool) my internet was recognized again at my home location. Maybe the NCSI passive polling is now broken in 2004..? Maybe Microsoft changed how NCSI works? I can only speculate at this point.
Microsoft doesn't want us to connect to public open WiFi networks (with no password) or to networks with WEP-only autentication: "Connected, No Internet", because of poor security standards on such networks.
Command ipconfig indicates that IP address was successfully assigned by DHCP protocol, but Default Gateway is empty and Internet is inaccessible.
In order to connect to a public open WiFi network, or to a network with hidden SSID, such connection has to be created manually. I haven't found such option in Settings > Network & Internet > WiFi > Manage known networks (at least in Version 1903), but it can be done in Control Panel.
At first, click on the WiFi tray-icon and if the connection is visible, Forget it. Then create a new profile:
Control Panel >
Network and Sharing Centre >
Set up a new connection or network >
Manually connect to a wireless network
(Connect to a hidden network or create a new wireless profile)
This opens a dialogue where we can fill in all network properties:
Network name (SSID), Security type, including Open WiFi without authentication, Encryption type and Security Key (password).
We may see stored profiles in console window with command
netsh wlan show profiles
and check its properties with
netsh wlan show profile key=clear name="Network name"
Having been connected by a manually created profile, Windows no longer complains about low WiFi security.
I only connect via my secure AT&T account and I have all the necessary security options active from the access point to the laptop and all the extra bells and whistles connected in between. As I stated previously, if I connect an ethernet cable from my router/hotspot while keeping the wi-fi connected the error message clears itself up but if I remove the cable after successful connectivity the error pops back up. both options are private and secure. It has to be a problem with just the wi-fi option because it doesn't exist otherwise. Try it and see if anyone gets the same scenario. I wonder if I tweaked a "host file" in the c:*Windows*\System32\Drivers\etc**hosts**location it might make a difference. (rhetorical)
My laptop is WiFi-only (no Ethernet socket) and the connection to WiFi hotspot is Connected, secured, although the URL used to check connectivity is not available:
curl -i http://www.msftconnecttest.com
HTTP/1.1 404 Not Found
At least this address replies to ping and TCP port 80 is open:
Pinging 4-c-0003.c-msedge.net [13.107.4.52] with 32 bytes of data:
Reply from 13.107.4.52: bytes=32 time=11ms TTL=121
I forgot to mention that I have disabled IPv6, so no need to tweak etc/hosts. Perhaps you could try to (temporarily) uncheck Internet Protocol Version 6 (TCP/IPv6) on your WiFi adapter's Properties to see if that helps.
It has to be a problem with just the wi-fi option because it doesn't exist otherwise. Try it and see if anyone gets the same scenario. I wonder if I tweaked a "host file" in the c:*Windows*\System32\Drivers\etc**hosts**location it might make a difference. (rhetorical)