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.
Remke,
This is the third time I've asked you if you've collected the tracing I requested on our private chat.
If you have and you send it to me I will solve your problem.
If you haven't and are no longer interested then I don't understand the purpose of your continued comments on this thread.
I won't reply to this account again unless you really want the help you were asking for.
Since yesterday (and after Windows update !) no longer a NCSI working .. and this time i have al the settings like Tom Fair has advised.
It's just buggy ... no other words to describe
20H2
19042.928
"!!! in dutch: information about DISABLINGactive probe (official Microsoft documentation)
I've spoken about our GPO that allows for active probe disable earlier in this thread, but I'll repeat it here:
A long time ago (Win7) we introduced this GPO because some big public sector customers demanded it. This was back in the day when Windows didn't send out a lot of unsolicited packets to the internet without prior admin configuration, and so the behavior was not desired by high-security environments. Today this unsolicited outbound packet behavior has been normalized considerably with the development of all kinds of Windows components that do this...AOVPN and DirectAccess are big ones and must do this to "manage out" client machines.
Although we added this GPO, we certainly put the buyer beware verbiage very clearly in it:
"This may reduce the ability of NCSI, and of other components that use NCSI, to determine Internet access."