If after you upgrade or update your Windows 11/10 and you notice that the Network Connectivity Status Indicator (NCSI) on the notification area/system tray on the right end of the Taskbar indicates no internet connection, then this post is intended to help you. In this post, we will provide the solution you can try to resolve this anomaly.
Based on user reports on support forums, Windows 11/10 is displaying false internet connection warnings for some PCs.
Users have been reporting that a dreaded yellow triangle would appear on the system tray annoyingly reporting that they have No Internet Access. The error will appear when your device is connected to your internet device correctly but it would seem like Windows 11/10 cannot connect to the internet.
This issue is different from the internet connectivity issues that caused problems for VPN users. Despite Windows 10 informing users that their internet connection is down, it does in fact exactly as it should. As Windows problems go, this is a minor one.
Network icon says No internet access
If you’re faced with the issue, you can try the fix prescribed below to resolve the issue.
Since this is a registry operation, it is recommended that you back up the registry or create a system restore point as necessary precautionary measures. Once done, you can proceed as follows:
- Press Windows key + R to invoke the Run dialog.
- In the Run dialog box, type regedit and hit Enter to open Registry Editor.
- Navigate or jump to the registry key path below:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet
- On the right pane, double-click the EnableActiveProbing entry to edit its properties.
- In the properties window, set the Value data to 1.
- Click OK to apply changes.
- Exit Registry Editor and restart your computer.
That’s it! The network icon should now correctly report the internet connection status.
If this does not help, run one of these Network Troubleshooters or use the Network Reset feature and see if that works for you.
Microsoft has acknowledged this issue and will likely roll out a fix in a future cumulative update.
Related:
