Microsoft's service alert and the environments hit
Microsoft confirmed that customers operating in restricted Windows network environments — ranging from fully isolated, air-gapped systems to strictly firewalled networks — may see Windows Update failures after installing the January 2026 optional non-security preview updates. The company published a service alert describing the problem and the environments where it appears to surface, calling attention to constrained networks where direct access to Windows Update servers may be limited or controlled.
Symptoms and the underlying cause
Affected systems attempting to use the Windows Update page under Settings will show error code 0x80010002 when downloading updates. Microsoft warned that, while some devices can still download the February monthly security update, they may subsequently be unable to use Settings to fetch updates released in March, April, or later months.
Microsoft attributed the failure to a specific change: "This issue results from recent changes in download timeout requirements when starting download operations. It is not related to device integrity or the device's ability to install Windows updates, only to its ability to download updates from the internet via the Windows Update page under Settings." In short, Microsoft says the problem prevents download initiation in constrained networks rather than blocking update installation once an update package is available.
Workarounds: Known Issue Rollback KB5083806 and KB5083631
While a permanent fix is still under development, Microsoft published workarounds based on Known Issue Rollback (KIR) group policy settings. Administrators can install one of the following KIR policies depending on their Windows version:
- Windows 11 26H1 KB5083806 Known Issue Rollback
- Windows 11 24H2, Windows 11 25H2 and Windows Server 2025 KB5083631 Known Issue Rollback
Microsoft's guidance is explicit about implementation: "You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting," Microsoft added. The company also points administrators to its support website for further guidance on deploying and configuring KIR group policies.
How administrators should act now
For IT administrators responsible for systems in restricted networks, the immediate, source-approved actions are limited and specific: install the KIR group policy that matches the Windows build in use, configure it per Microsoft's instructions, and restart affected devices so the policy takes effect. Microsoft frames this as a workaround rather than a remediation of device integrity or install capability; the company continues to work toward a full resolution that will remove the need for these special group policy settings.
Where this sits in a pattern of update-delivery problems
This incident is the latest in a string of update-delivery problems Microsoft has documented and fixed in recent years. The company resolved a separate bug in April 2025 that prevented enterprise customers from installing April 2025 security updates via Windows Server Update Services (WSUS). In August 2025 Microsoft fixed an almost identical issue that caused the Windows 11 24H2 cumulative update to fail with 0x80240069 errors when delivered via WSUS. More recently, Microsoft issued another KIR fix for a known issue that caused the May 2026 Windows 11 security update (KB5089549) to fail to install on some systems and to trigger 0x800f0922 errors.
Microsoft's current advisory leaves a narrow, practical path for administrators: apply the version-appropriate KIR group policy, restart devices, and consult Microsoft's support documentation while the company works on a permanent correction. For organizations operating in air-gapped or tightly firewalled environments, those steps will determine whether Windows Update via Settings continues to function for forthcoming monthly releases.
