**Microsoft** has acknowledged that customers operating in restricted network environments may encounter **Windows Update** failures after applying the January 2026 optional non-security preview updates. ### Impact on Restricted Networks In network-restricted environments, including fully isolated, air-gapped systems and strictly firewalled networks, affected systems will display the error code 0x80010002 when attempting to update via **Windows Update**. According to a [service alert](https://admin.cloud.microsoft/Adminportal/Home?source=applauncher#/windowsreleasehealth/:/issue/WI1311742) spotted by **Microsoft** MVP **Susan Bradley**, "Affected devices might be able to download the February monthly Windows security update, but then become unable to use the Windows Update settings to download Windows updates released in March, April, or later months." **Microsoft** clarified that "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." ### Known Issue Rollback (KIR) as a Workaround While **Microsoft** is actively working on a permanent solution, IT administrators can mitigate the issue by implementing one of the following group policies using Known Issue Rollback (KIR), a **Windows** feature designed to revert problematic updates delivered through **Windows Update**: * [Windows 11 26H1 KB5083806 Known Issue Rollback](https://download.microsoft.com/download/2b881d89-8630-4d6f-a316-b100094b07aa/Windows%2011%2026H1%20KB5083806%20260513_22071%20Known%20Issue%20Rollback.msi) * [Windows 11 24H2, Windows 11 25H2 and Windows Server 2025 KB5083631 Known Issue Rollback](https://download.microsoft.com/download/4c6b9e6e-5760-435f-b5ef-0ceaafc14520/Windows%2011%2024H2,%20Windows%2011%2025H2%20and%20Windows%20Server%202025%20KB5083631%20260513_22072%20Known%20Issue%20Rollback.msi) "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** stated. Further guidance on deploying and configuring KIR group policies is available on **Microsoft's** [support website](https://docs.microsoft.com/en-us/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). ### Recurring Update Issues This isn't the first time administrators have faced challenges with **Windows** updates. In April 2025, **Microsoft** addressed a bug preventing enterprise customers from installing the April 2025 security updates via **Windows Server Update Services (WSUS)**. A similar issue arose in August 2025, causing the **Windows 11 24H2** cumulative update to fail with 0x80240069 errors when delivered through **WSUS**. More recently, **Microsoft** released a KIR fix for installation issues related to the May 2026 **Windows 11** security update (**KB5089549**), which triggered 0x800f0922 errors on some systems.  ## [The Validation Gap: Automated Pentesting Answers One Question. You Need Six.](https://hubs.li/Q048zztN0) Automated pentesting tools deliver real value, but they were built to answer one question: can an attacker move through the network? They were not built to test whether your controls block threats, your detection rules fire, or your cloud configs hold. This guide covers the 6 surfaces you actually need to validate. [Download Now](https://hubs.li/Q048zztN0)