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.
"Two quick changes to your registry to see if this improves the behavior:
1. Add HKLM\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator
UseGlobalDns DWORD 1
DWORD 3
And then reboot."
I just tried this, and unfortunately it did not improve behavior. All of my Windows 10 machines act the same way including virtual machines. Note that my wife's MacOS and my Debian machine do not function like this. It's been almost two years of this problem. I've practically given up and would just reboot my router every time I reboot my PC to "fix" the problem temporarily.
Thanks Tom for the kind comments.
I have got a solution adding a key from PS
New-ItemProperty -Path “HKLM:\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator\” -Name UseGlobalDNS -PropertyType DWORD -Value 1 -Force
It appears the last Windows Update fixed the problem. Anybody else notice the difference?