Network and Sharing Center - The service to detect this status is disabled.

Rich Bell 0 Reputation points
2026-08-20T22:39:00.1566667+00:00

I am running the latest version of Windows 11 Pro Canary. This has been a problem for at least the last 3 builds. I have tried everything that I could find online about fixing this problem. The links in the Sharing Center also do not work. All network related services are set to Automatic and are running. Troubleshooting doesn't find anything. I have reset the network. I have deleted and reinstalled all network drivers. The network is function correctly. I have posted on the Feedback Hub and have received no response.

What else can be done to fix this issue?

Windows Insider program | Apps on Insider preview

2 answers

Sort by: Most helpful
  1. Alex-L 12,555 Reputation points Microsoft External Staff Moderator
    2026-08-21T09:49:09.2866667+00:00

    Hi Rich Bell

    Thanks for confirming you've already worked through the NCSI, service, registry, logging, and network reset steps without improvement.

    Given the environment, this starts to look less like a configuration problem and more like a potential Canary build regression affecting the legacy Network and Sharing Center or its status-detection components.

    At this point, I'd be interested to know:

    1. Does Settings > Network & Internet correctly show the connection status and network details?
    2. Do the links in Network and Sharing Center fail only there, or do the equivalent settings pages open correctly from the modern Settings app?
    3. Have you tested whether the issue occurs in a newly created local user account?

    If the problem is limited to Canary builds and you've already submitted Feedback Hub reports, there may not be an end-user fix available until Microsoft investigates and addresses the underlying issue. It may also help if other Canary users can confirm whether they see the same behavior.

    Was this answer helpful?


  2. AI answer

    2026-08-20T22:39:16.95+00:00

    Since the network works and the issue is the status-detection layer, focus on NCSI and network profile detection rather than the adapter itself.

    1. Verify what Windows currently thinks the connection state is. Run PowerShell:
         Get-NetConnectionProfile
      
      Expected result for normal internet detection is IPv4Connectivity : Internet or IPv6Connectivity : Internet. If the profile is wrong here, the problem is in Windows network status detection, not basic connectivity.
    2. Check whether NCSI active probing is enabled. Open Registry Editor and review:
         HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet
      
      Confirm:
      • EnableActiveProbing = 1
      On Windows 10 version 1607 and later, the default probe values are:
      • ActiveWebProbeHost = www.msftconnecttest.com
      • ActiveWebProbePath = connecttest.txt
      • ActiveWebProbeContent = Microsoft Connect Test
      • ActiveDnsProbeHost = dns.msftncsi.com
      • ActiveDnsProbeContent = 131.107.255.255
      Risk: editing the registry incorrectly can cause system issues. Only correct values that are different from the defaults.
    3. Do not disable active probing. NCSI uses active probes to determine internet connectivity. If probing is disabled, Windows can report no internet even when browsing still works.
    4. Check the NCSI operational log. Open Event Viewer and go to:
         Applications and Services Logs\Microsoft\Windows\NCSI\Operational
      
      This is the primary log location for NCSI probe and status events.
    5. Confirm the probe endpoint behavior. NCSI uses an HTTP query to: http://www.msftconnecttest.com/connecttest.txt The expected result is HTTP 200 OK with content Microsoft Connect Test.
    6. If the machine is domain-joined, also verify the applied network profile. Get-NetConnectionProfile should show the expected category, such as DomainAuthenticated on a correctly detected domain network. On Windows 11, domain profile detection is handled by the Network List Manager rather than NLA.
    7. If this started across multiple Canary builds and all services, drivers, and network reset steps were already tried, compare against known Windows issues before making more changes. Review Windows release health for the installed build.

    The key point is that this symptom usually means Windows cannot validate connectivity status through NCSI, even though the network stack itself is working.


    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.