Microsoft Fixes Windows Server 2016 June 2026 Update Installation Failures

Microsoft has resolved a known issue that prevented some Windows Server 2016 systems from installing the June 2026 security update.

The problem affected servers that were not fully updated before attempting to install the June 2026 Patch Tuesday release. Affected devices could fail to install KB5094122 and display error code 0x80070002 or ERROR_FILE_NOT_FOUND during the installation process.

Cause of the Windows Server 2016 Update Failure

Microsoft said the issue primarily impacted systems that tried to deploy KB5094122 without first installing the May 2026 security update, KB5087537. As a result, some administrators were unable to successfully apply the latest security fixes to their Windows Server 2016 environments.

The company acknowledged the problem after reports from IT administrators and later confirmed the issue through service alert WI1395301 in the admin center.

According to Microsoft, the bug has now been fixed, and affected Windows Server 2016 devices should no longer experience installation failures when deploying KB5094122.

June Update Issue Now Resolved

Microsoft says administrators can now install the June 2026 security update normally, even on systems that previously encountered the installation error.

The issue highlighted the importance of maintaining updated prerequisites, as the missing May 2026 security update appeared to be a key factor behind the deployment failures.

For users running client versions of Windows, Microsoft also recently released the June 2026 Patch Tuesday update for Windows 11.

Additional Windows Server Fixes Released

The Windows Server 2016 update installation issue was not the only server-related problem Microsoft addressed recently.

The company also released fixes for a Windows Server 2025 issue that could unexpectedly trigger BitLocker Recovery after installing security updates. In addition, Microsoft resolved update deployment failures caused by a bug in the Windows Update Standalone Installer (WUSA), which affected some enterprise environments.

These fixes are part of Microsoft’s ongoing effort to address post-update issues reported by administrators and enterprise customers.

Via BleepingComputer