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.
Hmm.. I see.
I think I found the culprit. as you said that it should be HTTP right.
I think the lastest KB that fix the probing is replacing the root domain from www.msftconnecttest.com to msftconnecttest.com and also the connecttest.txt is also replaced with redirect for some reason. if you gone to http://msftconnecttest.com/connecttest.txt it will close the connection directly, and if it's redirect, the content is MSN pages (because header send to msn.com) I think this's why most people still facing this issue, and I think my answer seems misleading.
But now I can confirm that the culprit is this config, so I change the probepath and probehost back to old before KB update to fix NCSI, and yeah it will work normally with EnableActiveProbing = 1
If you are speaking of registry path HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet\ActiveWebProbeHost being changed it is not by our KB. Sounds like a config, script, or policy from another vendor changed this.
If one of our monthly KB's suddenly changed this we'd be hearing about reports of this from all over the news.
If this can happen again you can enable an audit on that regkey to see who changes it.
Hmm.. I see.
I think I found the culprit. as you said that it should be HTTP right.
I think the lastest KB that fix the probing is replacing the root domain from www.msftconnecttest.com to msftconnecttest.com and also the connecttest.txt is also replaced with redirect for some reason. if you gone to http://msftconnecttest.com/connecttest.txt it will close the connection directly, and if it's redirect, the content is MSN pages (because header send to msn.com) I think this's why most people still facing this issue, and I think my answer seems misleading.
But now I can confirm that the culprit is this config, so I change the probepath and probehost back to old before KB update to fix NCSI, and yeah it will work normally with EnableActiveProbing = 1