Windows 10 says I have no internet connection, but I have.

Anonymous
2020-05-21T19:20:56+00:00

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!

Windows for home | Windows 10 | Internet and connectivity

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.

0 comments
Answer accepted by question author
Anonymous
2020-06-18T19:27:38+00:00

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

Was this answer helpful?

100+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2021-06-07T17:45:06+00:00

The proper one is

"HKLM:\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator\” -Name UseGlobalDNS -PropertyType DWORD -Value 1 -Force

But the more appropriate way to do this is not through registry directly, but through group policy config:

Was this answer helpful?

20+ people found this answer helpful.
0 comments

335 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-09-29T12:53:15+00:00

    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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-09-29T02:08:43+00:00

    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

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-09-28T12:29:00+00:00

    The "Core Networking Diagnostics" firewall rules cannot block NCSI. They are designed to block ICMP traffic, while NCSI's probe is HTTP, These rules are designed for security-hardened servers that you don't want to answer to random pings coming from bad actors looking for live servers (IP address scanning).

    NCSI probes can fail for various environmental reasons. Search for my name in this thread for a number of common causes and solutions.

    Was this answer helpful?

    0 comments