Microsoft fixes Windows Server 2016 June update failures
Key Takeaways
- Microsoft fixed the 0x80070002 error that blocked KB5094122 security update installation on Windows Server 2016
- The failure occurred when administrators skipped the May 2026 KB5087537 prerequisite update
- This is one of several Windows update issues Microsoft has addressed in recent weeks across Server 2016, 2025, and Windows 11
Microsoft has resolved a bug that caused June 2026 security updates to fail on Windows Server 2016 systems. The issue threw a 0x80070002 (FILE_NOT_FOUND) error when administrators tried to install the KB5094122 update without first applying the May 2026 KB5087537 patch.
The company acknowledged the problem through an admin portal service alert after IT administrators reported widespread installation failures. Systems that were current on updates were unaffected. The fix is now live, and Microsoft says affected devices should no longer encounter the error.
“Microsoft received reports that the June 2026 security update might fail to install on some devices running Windows Server 2016. Affected devices might have received error code 0x80070002 (ERROR_FILE_NOT_FOUND) during installation of the update.”
— Microsoft service alert
Why did the Windows Server 2016 update fail?
The root cause is straightforward: cumulative updates on older Windows Server versions often have strict dependency chains. KB5094122 required files or registry entries that KB5087537 created. Skip the May update, and the June update can't find what it needs.
This pattern is common with legacy infrastructure. Windows Server 2016 turns ten years old this year, and maintaining it in production means navigating increasingly complex update dependencies. Each month's patch builds on the last, and out-of-order installations trigger exactly these FILE_NOT_FOUND errors.
On Reddit's r/sysadmin community, system administrators shared frustrations about the recurring nature of these failures. Several posted workarounds involving DISM commands or clearing specific registry keys tied to Event Log providers. The consensus: keeping a month-by-month update schedule is no longer optional on Server 2016.
A string of Windows update problems in 2026
This fix is part of a pattern. Microsoft has spent the past several weeks cleaning up update-related bugs across its server and desktop operating systems.
In May 2026, the company fixed an issue where the KB5089549 Windows 11 security update failed with error 0x800f0922. That one came down to insufficient free space on the EFI System Partition, which caused automatic rollbacks.
Early June brought warnings about 0x80073712 and 0x800f0993 errors on Windows 11 24H2 and 25H2 systems. Last week, Microsoft patched a bug that forced Windows Server 2025 devices into BitLocker recovery mode after the April 2026 security update. A separate fix addressed failures in the Windows Update Standalone Installer (WUSA) that had persisted since May 2025.
And as of Wednesday, Microsoft confirmed it's investigating yet another problem: the June 2026 updates are blocking third-party applications from launching Office apps or opening documents. That one remains unresolved.
What administrators should do now
If your Windows Server 2016 systems are still showing the 0x80070002 error, Microsoft's fix should propagate automatically. For stubborn cases, the manual path is to install KB5087537 first, reboot, then apply KB5094122.
More broadly, this incident reinforces the need for sequential update discipline on legacy servers. Test environments should mirror production patching schedules. Skipping months or applying updates out of order invites exactly these failures.
Organizations still running Server 2016 in production should also consider their long-term roadmap. Extended Security Updates are available, but the maintenance overhead grows each year. At some point, the cost of keeping legacy infrastructure running exceeds migration costs.
The bigger picture on legacy infrastructure
Ten-year-old server operating systems don't age gracefully. Each cumulative update adds complexity. Each missed patch creates potential dependency gaps. And Microsoft's engineering resources naturally prioritize current platforms over legacy ones.
That's not a criticism. It's economics. But it means administrators managing older infrastructure need tighter processes, better testing, and realistic conversations with leadership about technical debt.
The June 2026 update failure wasn't a security breach or a critical outage. It was an inconvenience with a clear fix. But it's also a reminder that legacy systems require more care, not less, as they age.
Logicity's Take
Microsoft's quick turnaround on this fix is good. What's less good: the frequency of these update-related bugs across the Windows ecosystem in 2026. Four major patching issues in six weeks suggests either increased complexity in the update pipeline or reduced QA bandwidth. For enterprises, the practical response is the same either way: maintain staging environments, test before deploying to production, and budget time for rollback procedures every patch Tuesday.
Another recent security-relevant incident affecting enterprise operations
Frequently Asked Questions
What caused the Windows Server 2016 June 2026 update to fail?
The KB5094122 security update failed with error 0x80070002 (FILE_NOT_FOUND) on systems that hadn't installed the May 2026 KB5087537 prerequisite update. The June patch required files or registry entries created by the May update.
How do I fix the 0x80070002 error on Windows Server 2016?
Microsoft has deployed a fix that should resolve the issue automatically. If the error persists, manually install KB5087537 first, reboot, then install KB5094122.
Is Windows Server 2016 still supported?
Windows Server 2016 is in Extended Security Updates (ESU) mode. Microsoft continues to release security patches, but the operating system is now ten years old and requires careful update management.
What other Windows update issues has Microsoft fixed recently?
In recent weeks, Microsoft fixed the KB5089549 Windows 11 update failure, addressed errors on Windows 11 24H2/25H2, patched a BitLocker recovery bug on Server 2025, and resolved WUSA installer failures dating to May 2025.
Need Help Implementing This?
If your organization needs assistance with Windows Server update management, patch testing infrastructure, or migration planning from legacy systems, contact Logicity's enterprise consulting partners for tailored guidance.
Source: BleepingComputer
Manaal Khan
Tech & Innovation Writer
Related Articles
Browse all
Kraken Crypto Exchange Extortion: Hackers Threaten to Leak Internal Videos After Insider Breach
Cryptocurrency exchange Kraken is being extorted by hackers who obtained videos of internal systems through bribed support employees. The company says no funds were compromised and refuses to pay, with only about 2,000 accounts affected. Kraken is working with federal law enforcement to prosecute everyone involved.
Windows 11 KB5083769 and KB5082052: April 2026 Patch Tuesday Brings Smart App Control Changes and Security Fixes
Microsoft's April 2026 Patch Tuesday updates are now live for Windows 11, bringing critical security patches alongside a welcome change to Smart App Control. You can finally toggle SAC on or off without wiping your entire system. The updates cover versions 23H2, 24H2, and 25H2.
Zero Trust Identity Security: 5 Ways This Framework Actually Stops Credential Theft
Stolen credentials caused 22% of breaches in 2025, making them the top attack vector. Zero Trust promises to fix this, but only when it's built around identity as the core principle. Here's how organizations can implement it properly.
Open Source PR Backlogs: Why Your GitHub Contribution Sits Unreviewed for a Year
A developer's Jellyfin pull request has been waiting over a year for merge despite two approvals, exposing a systemic crisis in open source maintenance. Queuing theory explains why backlogs grow exponentially, and 60% of maintainers have quit or considered quitting due to burnout.
