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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-02-04T08:06:46+00:00

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2021-01-27T20:11:27+00:00

    As this seems to be a problem created from a windows update. Undoing the changes in the registry that may be causing the problem that the update set is a easy solution. Having away to reset to defaults is a good thing. Granted a last resort type of thing yes but still a good thing. I agree you should beware of these but the company seems sound and not one of these fly by night install **** malware company's. I am just reporting what worked for me. I have not taken the time to check what changes the factory defaults actually change. If someone wanted to take the time to actually track the changes they may be able to find the problem or at least narrow down the fix.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2021-01-13T22:24:52+00:00

    I believe you when you say you've verified the regkeys.

    There have been may cases I've worked on in which no probe packets ever made it to the wire because of intereception in the network stack.

    Ex: Third party product that installs a DNS intercept filter on the loopback and pipes it back into the stack again will not work because without Global DNS GPO enabled this violates TCP<-->NCSI broker that the destination network interface chosen needs to be the one TCP receives.  Loopback messes that up.

    Third party products I've seen do this include Cisco Umbrella, Z-scaler, F5 Big IP agent, McAfee something something, etc.

    (Global DNS fixes this)

    Another Ex:  NCSI uses WinhttpAutoProxySvc to know if there's a proxy and to send the probe that way.  But if there's a problem with the proxy configuration in the environment and autoproxy can't get the info accurately, neither can NCSI, and this sometimes results in autoproxy returning proxy autodetect failure back to NCSI..failing the probe.   Manual proxy gets around this, but the right way to fix is to fix autodiscovery.

    These may not apply to you.  But there are other possibilities.   Third party products installing filters in the network stack that intercept and drop certain packets.  

    Regarding tracing, the best we have for external consumption at this point are the NCSI diagnostic/operational events.   They aren't all that verbose.  

    I could also recommend elevated prompt:

    netsh trace start wireless_dbg, bounce adapter, netsh trace stop, netsh trace convert <resulting etl file>.  In Win10 20H1 (2004) builds this has gotten a little better verbiage but still not much compared to our internal tracing that we use with customers that open cases with us.

    If nobody saw me put this elsewhere...

    HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet\MinimumInternetHopCount

    DWORD 3

    and reboot

    helps the passive probe. (note that active probe isn't just firing on periodic basis...it's triggered by mostly network changes.  Passive probe is in play by watching received packets and learning from those in between active probes).

    Default of that regval is 8, which IMHO is way too big.

    I hope this helps somewhat.  

    Almost every NCSI case I've ever gotten I've root caused...but I can't do that here because it requires me getiing into internal tracing 1:1 with everyone...and that's unfortunately just not feasible.

    I'm here for top-of-head quick-fire answers I can give, and any value I can add.

    And of course, if I come across a bug fix that does get published on occasion I'm more than happy to light that up here when that happens.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments