Microsoft Confirms Windows Update Failures in Restricted Network Environments

Microsoft has confirmed that some customers using restricted Windows network environments may experience Windows Update failures after installing the January 2026 optional non-security preview updates.

The issue affects systems operating in tightly controlled environments, including air-gapped networks, fully isolated networks, or networks with strict firewall restrictions. Affected devices may encounter error code 0x80010002 when attempting to download updates through the Windows Update page in Settings.

According to Microsoft, impacted devices may still be able to download the February monthly Windows security update. However, after that, they may no longer be able to use Windows Update in Settings to download updates released in March, April, or later.

Microsoft stated that the issue is caused by recent changes to download timeout requirements when initiating download operations. The company clarified that this is not related to device health, system integrity, or the ability to install updates. Instead, the problem is limited to the device’s ability to download updates from the internet through Windows Update.

Microsoft is currently working on a permanent fix. In the meantime, IT administrators can mitigate the issue by deploying the appropriate Known Issue Rollback (KIR) Group Policy for their Windows version:

• Windows 11 26H1: KB5083806 Known Issue Rollback
• Windows 11 24H2, Windows 11 25H2, and Windows Server 2025: KB5083631 Known Issue Rollback

After installing and configuring the correct Group Policy, affected devices must be restarted for the rollback policy to take effect.

Microsoft also recommends that administrators review its official guidance for deploying and configuring KIR Group Policies in managed environments.

This is not the first time enterprise administrators have run into update deployment issues. Microsoft previously resolved a Windows Server Update Services issue in April 2025 that blocked some enterprise customers from installing that month’s security updates. A similar issue was also fixed in August 2025, when Windows 11 24H2 cumulative updates failed with 0x80240069 errors when deployed through WSUS.

More recently, Microsoft released another KIR-based workaround for a separate issue affecting the May 2026 Windows 11 security update, KB5089549, which could fail to install on some systems and trigger 0x800f0922 errors.