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.
This one is odd - the suggestion by the Russian person to edit the registry.
In my case, it is already set to 1, but they say you should change it from zero to one.
I almost think they have that wrong.
"EnableActiveProbing" - setting that to one(true) should mean you are ENABLING that, which seems to be at the root of the problem.
I would have thought you would set that to ZERO - to disable active probing......
Disabling it, should mean that W10 no longer tries to do that, and so won't decide that this is a reason for you not having internet access.
Setting it to one suggests that you are telling W10 to actively try to do that probing - hence the problem when it can't, so it throws up the not-connected glob icon in the system tray.
Can anyone else comment on that?
Your real problem is failure to resolve the DNS query. Overriding it with the hosts file may work but if the server address were to change in the future you'd be stuck again.
To fix this properly run a packet capture and determine why the DNS query is timing out. So long as your DNS server returns the proper response this should work.
Tom (NCSI SME) Fairman
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.