"Microsoft received reports that the June 2026 security update (the Originating KBs listed above) might fail to install on some devices running Windows Server 2016," the company said in its admin portal alert, describing repeated installation failures that produced 0x80070002 (ERROR_FILE_NOT_FOUND) on affected servers.
Microsoft's acknowledgement and the remedial action
Microsoft confirmed the issue in an administrative service alert after IT administrators reported failed installations of the June 2026 security update for Windows Server 2016. The failures manifested as error code 0x80070002 or FILE_NOT_FOUND during installation of KB5094122. According to the notice, the company has now resolved the problem and says affected devices should no longer experience installation failures when deploying the June 2026 KB5094122 security update.
Why some Windows Server 2016 systems failed to update
The bug primarily affected customers attempting to install KB5094122 without first installing the prior month's security update, KB5087537. Microsoft’s advisory framed the problem as a dependency issue: systems that were not up to date with the prior patch could encounter the 0x80070002 error when attempting the June update. The vendor’s guidance is explicit — the installation failures were tied to systems that “weren't up to date” with the earlier KB.
Context: a string of recent Windows update installation incidents
This June fix arrived in the shadow of several other, closely timed update problems Microsoft has acknowledged and addressed. Last month, Microsoft resolved a similar installation failure and 0x800f0922 errors when deploying the May 2026 Windows 11 security update (KB5089549); those failures were triggered by insufficient free space on the EFI System Partition (ESP), causing the update to roll back automatically. In early June, Microsoft warned customers they may encounter 0x80073712 or 0x800f0993 errors on some Windows devices upgraded to Windows 11 24H2 or 25H2. In the preceding week, the company fixed a known issue that caused Windows Server 2025 devices to boot into BitLocker recovery after installing the April 2026 security update and fixed a separate bug that triggered installation failures for Windows updates released since May 2025 when installed using the Windows Update Standalone Installer (WUSA). More recently, Microsoft also confirmed it is investigating an issue that blocks third‑party applications from launching Word, Excel, PowerPoint, Access, and other Office applications (or from opening documents) on Windows systems after installing the June 2026 updates.
How technologists, enterprise IT administrators, and end users should react
- Technologists and security teams: Verify that Windows Server 2016 systems have the prior KB5087537 installed before deploying KB5094122; confirm successful installation and monitor for the 0x80070002 (ERROR_FILE_NOT_FOUND) condition until Microsoft’s mitigation is fully reflected in your environment.
- Enterprise IT and procurement leaders: Review patch sequencing procedures and change control to ensure prerequisite updates are applied in the correct order; track the recently fixed and ongoing Microsoft advisories so rollout plans account for known dependency and partition‑space issues.
- End users and administrators managing smaller environments: If you experienced failed installs, retry the June KB5094122 deployment after confirming KB5087537 is present; if third‑party apps can’t open Office files following recent updates, watch for Microsoft’s ongoing investigation and apply vendor guidance as it arrives.
A practical closing
Microsoft’s resolution removes one concrete roadblock for Windows Server 2016 administrators: KB5094122 should now install without the previously reported 0x80070002 failures on systems that have been brought up to date. The broader pattern is instructive — a cluster of recent update issues highlights how prerequisites, partition capacity, and installer paths can derail rollouts across different Windows versions and deployment tools. For IT teams that wrestle with patch cadence and change management, the lesson is straightforward and unglamorous: confirm preconditions before applying cumulative updates, and watch vendor advisories closely during patch windows.
Source: BleepingComputer — Microsoft fixes Windows Server 2016 security update failures
