Hello allaturu reddy
This behavior is tied to how Windows 11 handles NCSI (Network Connectivity Status Indicator) probing in 802.1X environments. When internet reachability drops, NCSI marks the connection as “limited” and triggers a disconnect/re-authentication cycle, which is why you see repeated 802.1X attempts. Other OS platforms don’t couple WLAN connectivity to internet reachability in the same way, which explains the difference.
Microsoft does not recommend disabling NCSI entirely, as you already noted, because it affects endpoint health reporting and application behavior. A supported alternative is to redirect NCSI probes to an internal endpoint you control, such as a local web server that responds to the probe URL. This can be configured via Group Policy or registry under HKLM\System\CurrentControlSet\Services\NlaSvc\Parameters\Internet. That way, clients always receive a valid response even during WAN flaps, preventing unnecessary disconnects while retaining NCSI functionality.
This behavior is a design change in Windows 11 compared to Windows 10, where probing was less aggressive. Microsoft has acknowledged that NCSI can cause unintended disconnects in transient outage scenarios, and guidance is to either redirect probes internally or ensure WAN stability. At present, there is no official fix to decouple Wi-Fi connectivity from NCSI probing, but monitoring Microsoft advisories and cumulative updates is recommended, as improvements may be introduced in future builds.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
Harry.