Windows 11 26H2: Incorrect “No Internet” status despite verified IPv4 connectivity #140

Windows 11 26H2: Network status incorrectly reports "No Internet" despite verified connectivity

Environment

• Device: ASUS TUF Gaming laptop
• Network adapter: Intel Wi-Fi 6 AX201
• OS: Windows 11 26H2
• Build: 26300.9711
• Cumulative update: KB5127648, installed October 13, 2026
• Network: Campus Wi-Fi, DHCP-assigned configuration
• Observation period: October 15–16, 2026

Issue Description

Windows 11 continues to display "No Internet" in the taskbar and Settings homepage, although actual network connectivity is functional and "Get-NetConnectionProfile" reports "IPv4Connectivity = Internet"

The discrepancy persists after restoring NCSI active probing, repairing relevant Windows services, correcting DNS configuration, and completing network stack and system integrity repairs

This suggests a possible inconsistency between the connectivity state exposed through Windows networking APIs and the state presented by the Windows Shell and Settings UI

Verified Observations

1. Four independent connectivity checks returned successful HTTP 200 responses after remediation

2. "Get-NetConnectionProfile" reports "IPv4Connectivity = Internet", while the taskbar and Settings continue to indicate an offline state

3. Manual HTTP requests to "http://www.msftconnecttest.com/connecttest.txt" succeeded through two tested request paths

4. The NCSI registry value "EnableActiveProbing" was restored to "1"

5. EventLog, NlaSvc, and netprofm experienced service disruptions during the incident, and service recovery was part of the remediation

6. Initial DNS resolution delays were identified and addressed, but the incorrect UI status remained

7. The IPv4 routing table was inspected, with no unexpected competing default route identified

Troubleshooting Performed

The following corrective actions were completed during October 15:

• Restored NCSI active probing
• Restored Windows Event Log service configuration
• Recovered network awareness services
• Corrected DNS configuration
• Reset Winsock and the TCP/IP stack
• Executed SFC and DISM repair operations
• Re-established campus network authentication
• Rechecked network connectivity and system-reported connectivity state

Initial configuration and service problems were identified and corrected during troubleshooting

The remaining discrepancy is therefore reported separately from those earlier failures

Expected Behavior

When Windows networking components report Internet connectivity and the relevant connectivity checks succeed, the taskbar and Settings should consistently reflect the current connection state

Actual Behavior

"Get-NetConnectionProfile" reports Internet connectivity, but Windows continues to render the connection as offline

Possible Regression

The symptoms were observed around October 12–13, close to the installation of KB5127648 on October 13

This is a temporal correlation only, not confirmation that the cumulative update caused the issue

A stale connectivity state, a missed notification, or a failure to refresh the UI after NCSI/NLA recovery may explain the discrepancy

Successful manual requests to the NCSI endpoint confirm endpoint reachability, but do not independently prove that Windows' internal active probing completed successfully

Requests to Microsoft

1. Please investigate whether connectivity state changes are consistently propagated from NCSI/NLA and the relevant network profile components to the Windows Shell and Settings UI, particularly after network service recovery

2. Please confirm whether KB5127648 introduced any relevant changes to NCSI, network awareness, or connectivity status notification and refresh behavior

Current Workaround

Normal network operations remain functional after remediation

The incorrect status indicator can currently be disregarded for the verified working applications, while actual connectivity is checked independently

No confirmed permanent fix for the remaining status discrepancy has been identified

Additional diagnostic outputs, relevant Event Viewer records, and screenshots can be provided if required