Microsoft fixes Windows update failures linked to WUSA installer
Microsoft fixed a WUSA bug that broke some Windows updates from network shares. The issue affected Windows 11 24H2/25H2 and Windows Server 2025.
Intelligence analysis by GPT-5.4 Mini
Microsoft has patched a known Windows Update Standalone Installer problem that caused .msu updates to fail when launched from a network share containing multiple update files. The fix arrived in June 2026 cumulative updates after months of workarounds and partial mitigation.
Microsoft fixed a bug that could stop some Windows updates from installing when they were opened from a shared folder. It was like trying to use one key in a big keyring and the wrong door got picked, so copying the update file onto the computer first helped.
Analysis
What happened
Microsoft says it fixed a known issue that caused Windows updates released since May 28, 2025 to fail when installed through the Windows Update Standalone Installer, or WUSA. The bug showed up when admins tried to install or open a .msu file from a network share that contained multiple .msu files, and the failure could surface as ERROR_BAD_PATHNAME.
The problem mainly affected Windows 11 24H2/25H2 and Windows Server 2025 devices in enterprise environments. Microsoft noted that it did not affect the common home-user path, and it also did not occur when a single .msu file was used or when the file was copied locally first.
How Microsoft handled it
Microsoft first acknowledged the issue in August 2025. For home and non-managed business devices, it rolled out an automatic Known Issue Rollback Group Policy starting in September 2025. The broader fix arrived in June 2026 Patch Tuesday cumulative updates: KB5079391 for Windows 11 and KB5094125 for Windows Server 2025.
Microsoft also published a workaround for systems running older updates: save the .msu files locally before installing them. It added one more operational warning too: after restarting Windows following a WUSA install, wait 15 minutes or more before checking Update History in Settings, because the status may take a short time to appear correctly.
Broader context
This is one of several recent Windows update problems Microsoft has had to clean up, including prior failures tied to WSUS and other update-install errors. For security teams, the practical takeaway is simple: patching pipelines that rely on shared folders need validation, and local-file installs remain the safer fallback when update behavior looks unreliable.
Key points
- Microsoft fixed a WUSA issue that broke some Windows updates installed from network shares.
- The bug affected Windows 11 24H2/25H2 and Windows Server 2025, mainly in enterprise environments.
- Microsoft first acknowledged the issue in August 2025 and partially mitigated it for some devices starting in September 2025.
- The full fix arrived in June 2026 cumulative updates KB5079391 and KB5094125.
- Microsoft says admins can avoid the issue by saving `.msu` files locally before installing them.
The June 2026 cumulative updates should let affected organizations install patches normally again through WUSA. That can reduce manual workarounds and help IT teams keep Windows systems updated on schedule.
Older systems that have not taken the June 2026 updates can still hit the same failure and may keep relying on local-file workarounds. If admins miss the 15-minute delay guidance or keep using shared folders with multiple `.msu` files, update status checks may still look broken.
