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.
That is indeed the correct entry, and 1 is correct.
Also, check this one:
SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator
NoActiveProbe should be 0 (or not exist at all)
Also under above path
DisablePassivePolling should be 0 (or not exist)
Good luck with that request for Spotify. Although it sounds easy on first glance it's no small task to test for network connectivity. You have to contend with many different situations such as intermittent network issues, routing failures, DNS resolution, being behind hotspots or proxies, and many other possiblities.
This is why NCSI was created in the first place. So that other companies don't have to reinvent the expensive wheel. Instead they call our API and we tell them the state of the network.
The unfortunate part of this is these many nuances listed above in addition to changing environmental conditions and/or configuration can affect the ability for an active HTTP probe to properly get out to the internet (or the response to be delivered properly up the network stack if encountering third party network filters).
This is not to say NCSI hasn't had bugs (although these days they are far and few between). The Sep update for build 2004 had a fix for the *passive* probe (not active). This will help certain problem scenarios..maybe not yours. But I would update anyway to be sure.
I'll repeat what I mentioned in another comment:
Most commonly active probe failures are due to either DNS resolution, routing, or proxy interaction. Network captures can help in this regard (look for msftconnecttest.com).
Microsoft/Windows/NCSI/Operational events can also help in diagnosing these issues.
The way I solved this :
Enable the 'Specify Global DNS' setting, then run gpupdate /force. Note, a reboot is required to clear the existing issue.