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.
Glad it worked!
The code change for has been the same ever since 1709, and many customers resolved their problems with that GPO with similar loopback software in those older releases.
It's possible that the way that McAfee opens the socket to the loopback adapter may have changed over time. Depending on what parameters are passed to the function call to our public API determines if the hard "binding" condition is created.
As for your other events you may still have another problem layered below the one you just fixed. But you are right. As long as the active probe does get out within a short period, and/or the passive probe is *also* determining internet, the connectivity status won't change. The passive probe is added protection for cases where the active probe is being stopped from going out.
Thanks Tom, setting the "Enable Global DNS" group policy did indeed fix this issue for me as it's been fine several weeks now.
It's strange that this was necessary though because that group policy was added in the 1709 update, and this problem only began with the 2004 update, so it appears as though that change in 1709 was actually not working correctly until the 2004 update.
Also, for every ActiveDnsProbeSucceeded entry in the event log there are still 10+ ActiveHttpProbeFailed entries, but at least NCSI is assuming that any success is good enough to say there is internet access. As mentioned previously, loading the http probe url in a browser or powershell always works fine so there still seems to be some issue with NCSI http probes.
Good to hear your where able to solve it ;)