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

Microsoft has included a new policy setting, Specify Global DNS, for Windows 10 build 1709 or later, which allows the NCSI feature to perform lookups over any network interface.

• Specify Global DNS: This policy setting enables you to specify DNS binding behavior. NCSI by default will restrict DNS lookups to the interface it is currently probing on. If you enable this setting, NCSI will allow the DNS lookups to happen on any interface.

.. i wonder why ...

At home i also have wired interfaces AND wifi interfaces .. both connected ..

Hmmm,

A large company like Cisco is telling us:
https://support.umbrella.com/hc/en-us/articles/230900948-Umbrella-Roaming-Client-Microsoft-Windows-Limited-Network-Connectivity-Warning-Yellow-Triangle-#Fix

---%<---

A Fix from Microsoft (Windows 10 Fall 2017 Creators Update)

Microsoft has included a new policy setting which resolves the root cause. This is the preferred fix for Windows 10 users.

To obtain the fix please update Windows 10 to version 1709 (build 16299) or later.  

---%<---

https://support.umbrella.com/hc/en-us/articles/230900948-Umbrella-Roaming-Client-Microsoft-Windows-Limited-Network-Connectivity-Warning-Yellow-Triangle-

+

https://community.webroot.com/troubleshooting-116/network-icon-showing-yellow-with-the-webroot-dns-protection-agent-installed-339903

+

http://www.souka.nl/results.php?q=HKLM%5CSYSTEM%5CCurrentControlSet%5CServices%5CNlaSvc%5CParameters%5CInternet%5CMinimumInternetHopCount&cx=partner-pub-8613501904892077%3Aaorts6-98la&cof=FORID%3A10&ie=ISO-8859-1&google-search=++++Zoeken++++

+

Windows 10 2004 won't detect internet even though wireless internet is working fine

https://social.microsoft.com/Forums/azure/nl-NL/03a9b3ff-2d85-4840-b776-d26faaa7c314/windows-10-2004-wont-detect-internet-even-though-wireless-internet-is-working-fine?forum=win10itprogeneral

+

(dutch)

https://admx.help/?Category=Windows\_10\_2016&Policy=Microsoft.Policies.InternetCommunicationManagement::NoActiveProbe&Language=nl-nl

I just feel like this problem is not going to be solved EVER .. just Microsoft pointing the big finger to the users struggling with this problem..

~remke

"I understand that you too are frustrated with this issue. But the reality is that there are too many of us with the issue to ignore it. True or not, blaming third party applications is not what we want to hear. Like I mention in my post from earlier on April 22, I observed heavy network traffic generated by the active probe when either it cannot reach the designated site or some other issue. While it is possible for a third party app to cause problems, I simply could not identify one. (Out of curiosity, what happens if Microsoft's servers are having the issue on their end?)"

Believe me, I'm not frustrated.  I really enjoy helping people with NCSI problems.  That's why I'm on this thread.

I know "third-party" or "something else in your environment" is not something you enjoy hearing.  That doesn't make it false.  In my experience 99% of issues are due to these two factors.  Yes, there have been NCSI bugs and I'm happy to discover, verify, fix, and commit them when I do.  But I promise I'm not blindly parroting "It's never Microsoft".  Sometimes it is.   But statistically speaking NCSI is pretty solid.  But there's a lot of things that can disrupt NCSI's ability to accurately report connectivity state.

And NCSI, unfortunately, is a victim unto itself because admittedly it is not a Windows component that gives users/admins good hints at where to start their troubleshooting outside of NCSI events....although these are definitely a good place to start.   I've been invested in pursuing improvement in this area in the future but ultimately I don't have the authority to greenlight anything.  That you couldn't identify the root cause doesn't mean that Windows is that cause by default, although I definitely understand how it's easy for people to make that assumption.  The *only* thing it means is that the root cause is not obvious.

If Microsoft NCSI probe servers on the Internet are having problems I wouldn't be spending this time in this thread right now.  I and 25 other network engineers would be deep in NCSI tickets from enterprise customers.   But you would know it first because a simple top level news item on Bing or Google would be "Windows network detection broken for millions of systems worldwide".

"it appears I did this successfully by disabling active probe within the registry settings."

I still have my doubts about whether

1. NCSI is truly not probing on those machines anymore
2. or if it is and those machines have network connectivity issues that you're simply not aware of.

But in my previous reply I gave 5 simple things to check to verify this.

"I went against the flow of your teachings and was successful. This does not mean everyone will be successful,"

Exactly my point.  And it also doesn't mean that this won't bite you sometime down the road, or is affecting your users now but you're not aware of it yet.  (But still begs the question if NCSI probing is truly disabled in your environment)

" You ask that we provide information so you can diagnose. I provided on this site the information I discovered in the process of narrowing the issue down to the active probe. I did my part to help you by providing what I found. I don't have time to spend hours on the phone with you and your team when the answer is in my grasp. I just ask Microsoft to take this issue seriously and address it. I sincerely want to use your product as you intended it to be used, but not at the cost of hours of you digging through my systems only to tell me it is a third party app, or worse yet that my system or network settings do not meet Microsoft expectations."

I'm not offering analysis on first-level information that you've given....which isn't always possible to derive root cause from.

I'm offering deeper trace analysis that external (non-Microsoft) does not have access to.  Tracing that we would collect from customer who open support tickets with us and only we can convert with our private symbols to see deeper symptoms to derive root cause.

I also don't intend to tie you up on the phone.  I'd give you simple instructions to execute on a machine and send me the data, after which I would turn around my analysis to you.

Are you interested in this?

"Finally, I highly doubt, as you imply, that Microsoft is unaware of the issue. As an engineer with many years experience, my guess is that they are already working on a fix or at the very least researching the problem. But until that fix is released, I ask you stop spreading the false information that "If you want to break your machine's network connectivity HARD disable the active probe. " You have stated this at least a few times. If your statement were true, I would not be able to be adding this entry now, nor would I and my team of engineers have had network and internet access for the past month.  "

I'm very tightly coupled with the NCSI product group and am aware of the biggest issues they’re aware of.

But you keep referring to "THE" problem as if there's just one big NCSI problem.

In fact there are many varied root causes that lead to NCSI issues.  

""Look, I and many others don't have the time nor the tools to fully diagnose Microsoft's problems...."

I know you don't have the time, which is why I offered to do deeper analysis for you.   Free of charge.   No service account hours or tickets necessary.  If you're genuinely interested having me do analysis to solve this frustration you've had to deal with, my address was in the previous comment.