Microsoft has resolved a known problem that caused Windows updates from May 2025 onward to fail when installed through the Windows Update Standalone Installer (WUSA) from a network share.
WUSA is a native Windows command-line utility that enables administrators to install and uninstall Microsoft Standalone Update (.msu) files via the Windows Update Agent API, allowing for the deployment or removal of patches, updates, and hotfixes.
This known issue impacts Windows 11 24H2/25H2 and Windows Server 2025 systems on enterprise networks, as WUSA is not a typical method for installing updates on consumer devices. Microsoft also highlighted that the bug does not occur with a single .msu file or when the files are saved locally.
"Windows updates installed using the Windows Update Standalone Installer (WUSA) might fail with error ERROR_BAD_PATHNAME, when the update is installed using WUSA or double-clicking a .msu file from a network share that contains multiple .msu files," Microsoft stated when it first acknowledged the problem in August 2025.
"These issues might occur on devices that installed updates released May 28, 2025 (KB5058499) and later."
Microsoft initially mitigated this known issue automatically on home and non-managed business devices using a Known Issue Rollback Group Policy starting in September 2025.
Fixed in June 2026 cumulative updates
As part of the June 2026 Patch Tuesday, Microsoft ultimately resolved this known issue for all affected systems in cumulative updates released for Windows 11 (KB5079391) and Windows Server 2025 (KB5094125).
"If you are using an update released before this date, and are experiencing this issue, you have the option to work around it by saving the .msu files locally on the device and install the update from this location," Microsoft said in a Windows release health dashboard update.
"Also, if you've restarted Windows after installing an .msu file via WUSA, please wait 15 minutes or more before checking the Update History page in Settings. After this short delay, the Settings app should properly indicate if the update installed successfully."
Microsoft fixed another issue in April 2025 that prevented enterprise customers from installing the April 2025 security updates via Windows Server Update Services (WSUS), as well as a similar bug that caused the August 2025 Windows 11 updates to fail with 0x80240069 errors.
Earlier this week, Microsoft also warned customers that they may encounter difficulties installing the latest monthly updates on some Windows devices upgraded to Windows 11 24H2 or 25H2.
Test every layer before attackers do
Security teams log 54% of successful attacks and alert on just 14%. The rest move through your environment unseen.
The Picus whitepaper shows how breach and attack simulation tests your SIEM and EDR rules so threats stop slipping by detection.
Related Articles:
Microsoft: Recent Windows updates may fail to install via WUSA
Microsoft fixes BitLocker recovery bug on Windows Server 2025
Microsoft: Some Windows PCs fail to install latest monthly updates
Microsoft fixes KB5089549 Windows security update install issues
Microsoft confirms April Windows updates cause backup failures