Microsoft has mounted a identified difficulty the place Home windows Updates launched after Might 2025 fail to put in from a community share through the Home windows Replace Standalone Installer (WUSA).
WUSA is a Home windows built-in command-line instrument that helps directors set up and uninstall Microsoft Standalone Replace (.msu) recordsdata and deploy or take away patches, updates, and hotfixes by means of the Home windows Replace Agent API.
This identified difficulty impacts Home windows 11 24H2/25H2 and Home windows Server 2025 units on company networks as a result of WUSA shouldn’t be a standard technique for putting in updates on residence units. Microsoft additionally said that this bug doesn’t happen in single .msu recordsdata or when recordsdata are saved domestically.
When Microsoft acknowledged the problem in August 2025, it mentioned, “Home windows updates put in utilizing the Home windows Replace Standalone Installer (WUSA) might fail with the error ERROR_BAD_PATHNAME while you set up utilizing WUSA or double-click an .msu file from a community share that incorporates a number of .msu recordsdata.”
“These points might happen on units which have put in the replace launched on Might 28, 2025 (KB5058499) or later.”
Microsoft first mechanically mitigated this identified difficulty on residence units and unmanaged enterprise units beginning in September 2025 by means of Recognized Challenge Rollback Group Coverage.
206 cumulative updates mounted in June
As a part of Patch Tuesday June 2026, Microsoft has lastly addressed this identified difficulty for all affected methods in a cumulative replace launched for Home windows 11 (KB5079391) and Home windows Server 2025 (KB5094125).
“In case you are utilizing an replace launched earlier than this date and are experiencing this difficulty, you have got the choice to work across the difficulty by saving the .msu file domestically in your machine and putting in the replace from this location,” Microsoft mentioned in an replace to the Home windows Launch Well being Dashboard.
“Additionally, in case you restart Home windows after putting in the .msu file through WUSA, please wait not less than quarter-hour earlier than checking the Replace Historical past web page in Settings. After this brief delay, the Settings app ought to correctly point out whether or not the replace was put in efficiently.”
In April 2025, Microsoft resolved a separate difficulty that prevented enterprise prospects from putting in the April 2025 safety replace through Home windows Server Replace Companies (WSUS) and an an identical bug that prompted the August 2025 Home windows 11 replace to fail with the 0x80240069 error.
Microsoft additionally warned prospects earlier this week that some Home windows units upgraded to Home windows 11 24H2 or 25H2 might expertise points putting in the newest month-to-month updates.
Safety groups doc 54% of profitable assaults and difficulty a warning on solely 14%. The remaining strikes invisibly by means of the atmosphere.
Picus’ whitepaper reveals easy methods to take a look at your SIEM and EDR guidelines in breach and assault simulations to make sure threats go undetected.
Get the white paper
