Microsoft has taken steps to address a known issue that has been affecting the installation of Windows updates from network shares using the Windows Update Standalone Installer (WUSA). This built-in command-line tool is essential for IT administrators, enabling them to install and uninstall Microsoft Standalone Update (.msu) files through the Windows Update Agent API, facilitating the deployment and removal of patches, hotfixes, and updates.
The issue primarily impacts Windows 11 24H2 and Windows Server 2025 systems operating within enterprise networks, as WUSA is not typically utilized for updating home devices. According to Microsoft, “Windows updates installed using the Windows Update Standalone Installer (WUSA) might fail with error ERRORBADPATHNAME when the update is installed using WUSA or double-clicking a .msu file from a network share that contains multiple .msu files.” This problem has been noted to occur on devices that installed updates released on May 28, 2025 (KB5058499) and later.
Importantly, Microsoft clarified that this issue does not arise when dealing with a single .msu file or when the files are stored locally. Additionally, users may experience a temporary glitch where the Update History page indicates that a restart is necessary after installing an .msu file and rebooting Windows.
Fix available via Known Issue Rollback
While a definitive fix for this bug is still in the works, Microsoft is proactively mitigating the issue on home and non-managed business devices through a Known Issue Rollback (KIR). For IT administrators managing devices, the resolution can be implemented by installing and configuring the Known Issue Rollback Group Policy on affected Windows 11 24H2 and Windows Server 2022 systems.
As an alternative, users who prefer to wait for a future Windows update can circumvent the issue by saving the .msu files locally and performing the installation from that location.
In recent months, IT administrators have encountered various challenges when attempting to install Windows updates. For example, in April, Microsoft addressed a separate issue that hindered enterprise customers from installing the April 2025 security updates on Windows 11 22H2/23H2 systems via Windows Server Update Services (WSUS). Furthermore, the company resolved a similar bug that caused the August 2025 Windows 11 24H2 cumulative update to fail with 0x80240069 errors when delivered through WSUS.
As the landscape of Windows updates continues to evolve, Microsoft remains committed to addressing these challenges and ensuring a smoother experience for IT professionals and end-users alike.
