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

"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.

Tom,

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?)

Look, I and many others don't have the time nor the tools to fully diagnose Microsoft's problem. My job required me to address my departments NCSI issues on mission critical computers. By all accounts it appears I did this successfully by disabling active probe within the registry settings. I went against the flow of your teachings and was successful. This does not mean everyone will be successful, but 100+ computers of various vintages and manufacturers is a pretty good statistical population for my argument. And to add additional information, at least ten of the computers are Microsoft Surface's of varying types that had the issue.

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.

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.

" it does cause system slowdowns for those computers that are running software that requires heavy network interaction."

This is the very first I've ever heard of someone raising a system performance issue caused by NCSI.   I believe you when you say what you observed, but underneath the covers I am skeptical that it's actually NCSI.

"Reviewing the multitude of information on this and other blogs, people are saying to "turn on" active probing in the registry settings with some very detailed instructions. But none of them can explain why it is so essential."

NCSI is the user mode logic responsible for determining what kind of network connectivity Windows has.  Namely internet, but also local and corporate inside/outside detection.  The connectivity status assessed by NCSI is used by various applications like Outlook, Teams, Skype, Windows Update, DirectAccess, and various third-party software.

The reason NCSI was developed was to save applications the incredibly complex task of determining network configuration on their own.  Imagine developing an application that performs network operations.  Every attempt to perform a task over the network would require constant attention to whether the network was still accessible.  In a network outage, even if short or intermittent, the application would timeout the operation and have to test the network continuously until it was intact.  This seems trivial until you consider that it must perform checks for a multitude of environmental factors such as being behind a proxy or hotspot/captive portal.  And it must also know if the network it detects is one that can satisfy its requests. Does it need full internet or just a private corporate access? All the while users must wait for their actions to complete or timeout while the application makes this determination.  Why should every application reinvent the wheel?  Windows should provide common functions that all software needs for network operations and simply notify applications upon changing conditions so that they can decide how to handle restrictive or no network connectivity. 

"Additionally, our finding is that active probing was turned on by default at the time of Windows install. So if it is turned on by default, why are all of the sites saying to turn it on?!?"

Windows doesn't turn off NCSI probing.  This is done by admins, or scripts being pushed, or perhaps even a third-party process.  But there's nowhere in WIndows code that has the ability to actually disable NCSI probing without admin manual action. 

All these sites mention turning it on because somewhere in the past somebody or something turned it off.

This is correct advice.

"... we DISABLED active probing... life continues without problems now."

That you haven't noticed any problems makes me think you think it's disabled but it's not.

Do this.  Verify that it's truly disabled on a computer you think it's disabled on by

1. Checking if the Network Location Service is running.   
2. Checking if this policy is ENABLED: Computer Config->Admin Templates->System->Internet Communication Management->Internet Communication Settings->Turn off Windows NCSI active tests
3. Checking if this policy is ENABLED: Computer Config->Admin Templates->Network->NCSI->Specify passive polling and Disable checkbox is checked.
4. Checking if this registry key has value 0: HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet\EnableActiveProbing 

(If the key doesn't exist then it's on by default)

5. Checking if this registry key exists with value 1:  HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet\DisablePassiveProbing

If any of the above isn't true, NCSI is alive and well on your system.

But if it isn't, fire up Office and try to send out an email. 

"So I ask that Microsoft address the active probing issue. Until they do have a fix, please start recommending that people DISABLE active probing. We lived without it for many decades, we can live a few more while Microsoft works out this problem.

I will absolutely not recommend this.

But if you're interested in having an offline conversation with me to discuss your experience with NCSI in much more detail I'd love to talk to you.   In fact I think I could learn a thing or two that could indirectly benefit the improvements NCSI needs (everything needs improvements).  We can take a much deeper introspective look at your past analysis and figure out what's going on.

I am very amicable and open and genuinely interested in improving the product. 

If you're interested please fire off an email to the following address and we'll start a conversation there.  

(EDIT: I have to be sneaky about the email address because the privacy bots keep removing it.   :)

forncsihelp at outlook dot com