Microsoft fixes Windows update failures linked to WUSA installer
Microsoft fixed a known issue causing Windows updates released since May 2025 to fail when installed via the Windows Update Standalone Installer (WUSA) from a network share. This issue affected Windows 11 24H2/25H2 and Windows Server 2025 on enterprise networks. The failure occurred with multiple .msu files on network shares, producing ERROR_BAD_PATHNAME. Microsoft mitigated the issue for home and non-managed devices in September 2025 and fully fixed it in June 2026 cumulative updates. Workarounds include installing .msu files locally and waiting 15 minutes after installation before checking update status.
AI Analysis
Technical Summary
A known issue caused Windows updates released since May 28, 2025 (starting with KB5058499) to fail when installed using the Windows Update Standalone Installer (WUSA) from a network share containing multiple .msu files. This affected Windows 11 versions 24H2 and 25H2, as well as Windows Server 2025, primarily in enterprise environments. The error encountered was ERROR_BAD_PATHNAME. Microsoft initially mitigated the problem on home and non-managed business devices via a Known Issue Rollback Group Policy in September 2025. The issue was fully resolved in the June 2026 Patch Tuesday cumulative updates KB5079391 for Windows 11 and KB5094125 for Windows Server 2025. Until the fix, Microsoft recommended saving .msu files locally before installation and waiting 15 minutes after installation before verifying update status.
Potential Impact
The issue caused Windows updates to fail installation via WUSA when run from network shares with multiple .msu files, potentially disrupting patch deployment in enterprise environments using this method. It did not affect installations from single .msu files or local storage. The failure generated ERROR_BAD_PATHNAME, which could delay or prevent timely update application on affected systems.
Mitigation Recommendations
Microsoft has officially fixed this issue in the June 2026 cumulative updates KB5079391 (Windows 11) and KB5094125 (Windows Server 2025). For systems not yet updated, a workaround is to save .msu files locally before installation. Additionally, after installing an update via WUSA, wait at least 15 minutes before checking the Update History to allow proper status reporting. No further action is required for home and non-managed business devices, as Microsoft mitigated the issue automatically via Known Issue Rollback starting September 2025.
Microsoft fixes Windows update failures linked to WUSA installer
Description
Microsoft fixed a known issue causing Windows updates released since May 2025 to fail when installed via the Windows Update Standalone Installer (WUSA) from a network share. This issue affected Windows 11 24H2/25H2 and Windows Server 2025 on enterprise networks. The failure occurred with multiple .msu files on network shares, producing ERROR_BAD_PATHNAME. Microsoft mitigated the issue for home and non-managed devices in September 2025 and fully fixed it in June 2026 cumulative updates. Workarounds include installing .msu files locally and waiting 15 minutes after installation before checking update status.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
A known issue caused Windows updates released since May 28, 2025 (starting with KB5058499) to fail when installed using the Windows Update Standalone Installer (WUSA) from a network share containing multiple .msu files. This affected Windows 11 versions 24H2 and 25H2, as well as Windows Server 2025, primarily in enterprise environments. The error encountered was ERROR_BAD_PATHNAME. Microsoft initially mitigated the problem on home and non-managed business devices via a Known Issue Rollback Group Policy in September 2025. The issue was fully resolved in the June 2026 Patch Tuesday cumulative updates KB5079391 for Windows 11 and KB5094125 for Windows Server 2025. Until the fix, Microsoft recommended saving .msu files locally before installation and waiting 15 minutes after installation before verifying update status.
Potential Impact
The issue caused Windows updates to fail installation via WUSA when run from network shares with multiple .msu files, potentially disrupting patch deployment in enterprise environments using this method. It did not affect installations from single .msu files or local storage. The failure generated ERROR_BAD_PATHNAME, which could delay or prevent timely update application on affected systems.
Mitigation Recommendations
Microsoft has officially fixed this issue in the June 2026 cumulative updates KB5079391 (Windows 11) and KB5094125 (Windows Server 2025). For systems not yet updated, a workaround is to save .msu files locally before installation. Additionally, after installing an update via WUSA, wait at least 15 minutes before checking the Update History to allow proper status reporting. No further action is required for home and non-managed business devices, as Microsoft mitigated the issue automatically via Known Issue Rollback starting September 2025.
Technical Details
- Article Source
- {"url":"https://www.bleepingcomputer.com/news/microsoft/microsoft-fixes-windows-update-failures-linked-to-wusa-installer/","fetched":true,"fetchedAt":"2026-06-12T11:55:09.930Z","wordCount":700}
Threat ID: 6a2bf39de617e2d834633fa0
Added to database: 6/12/2026, 11:55:09 AM
Last enriched: 6/12/2026, 11:55:17 AM
Last updated: 6/12/2026, 11:55:24 AM
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.