Microsoft has successfully resolved a significant issue that impacted the installation of Windows updates released since May 2025. This problem primarily affected users employing the Windows Update Standalone Installer (WUSA) from a network share, particularly within enterprise environments.
WUSA, a command-line tool integrated into Windows, facilitates the installation and uninstallation of Microsoft Standalone Update (.msu) files through the Windows Update Agent API. This tool is essential for administrators looking to deploy or remove patches, updates, and hotfixes efficiently.
The issue at hand was notably relevant for devices running Windows 11 24H2/25H2 and Windows Server 2025, as WUSA is less commonly utilized for updates on personal devices. Microsoft clarified that the problem did not arise when handling a single .msu file or when the files were stored locally.
In August 2025, Microsoft acknowledged the issue, stating, “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.” The company indicated that this issue could occur on devices that had installed updates released on May 28, 2025 (KB5058499) and later.
To mitigate the impact of this known issue, Microsoft implemented a Known Issue Rollback Group Policy in September 2025, automatically addressing the problem on home and non-managed business devices.
Fixed in June 206 cumulative updates
With the arrival of the June 2026 Patch Tuesday, Microsoft rolled out cumulative updates that effectively resolved the issue for all affected systems. The updates were released for Windows 11 (KB5079391) and Windows Server 2025 (KB5094125).
For users experiencing difficulties with updates released prior to this fix, Microsoft provided a workaround: “You have the option to work around it by saving the .msu files locally on the device and install the update from this location,” the company noted in an update to its Windows release health dashboard.
Additionally, Microsoft advised users who had restarted their systems after installing an .msu file via WUSA to wait at least 15 minutes before checking the Update History page in Settings. This brief pause allows the Settings app to accurately reflect whether the update was installed successfully.
Earlier in April 2025, Microsoft had addressed another issue that hindered enterprise customers from installing the April 2025 security updates via Windows Server Update Services (WSUS). An identical bug also caused failures in the August 2025 Windows 11 updates, resulting in 0x80240069 errors.
Recently, Microsoft cautioned customers about potential issues with installing the latest monthly updates on some devices upgraded to Windows 11 24H2 or 25H2, indicating ongoing vigilance in addressing update-related challenges.
