Microsoft has mitigated a identified challenge that brought about Home windows replace failures when putting in them from a community share utilizing the Home windows Replace Standalone Installer (WUSA).
WUSA is a built-in command-line device that helps IT admins set up and uninstall Microsoft Standalone Replace (.msu) information via the Home windows Replace Agent API to deploy and take away patches, hotfixes, and updates.
This identified challenge impacts Home windows 11 24H2 and Home windows Server 2025 programs on enterprise networks, as WUSA is not a typical technique for putting in Home windows updates on dwelling units.
“Home windows updates put in utilizing the Home windows Replace Standalone Installer (WUSA) may fail with error ERROR_BAD_PATHNAME, when the replace is put in utilizing WUSA or double-clicking a .msu file from a community share that incorporates a number of .msu information,” Redmond stated on the Home windows launch well being dashboard.
“These points may happen on units that put in updates launched Might 28, 2025 (KB5058499) and later.”
The corporate famous that this challenge does not happen with a single .msu file or when information are saved domestically. Moreover, one other challenge that ought to resolve by itself is that the Replace Historical past web page might quickly present {that a} restart is required after putting in an .msu file and restarting Home windows.
Repair obtainable through Identified Problem Rollback
Whereas a repair for this bug will not be but obtainable, Microsoft is mitigating it routinely on dwelling and non-managed enterprise units by rolling out a repair via Identified Problem Rollback (KIR).
IT admins can even resolve the difficulty on managed units by putting in and configuring this Identified Problem Rollback Group Coverage on impacted Home windows 11 24H2 and Home windows Server 2022 units.
As a workaround, those that choose to get the repair through a future Home windows replace can even save the .msu information domestically and set up the Home windows replace from that location.
In current months, admins have skilled a number of different points when making an attempt to put in Home windows updates. As an illustration, in April, Microsoft resolved one other challenge stopping enterprise prospects from putting in the April 2025 safety updates on Home windows 11 22H2/23H2 programs through Home windows Server Replace Providers (WSUS).
The corporate mounted an similar bug that brought about the August 2025 Home windows 11 24H2 cumulative replace to fail with 0x80240069 errors when delivered through WSUS.
46% of environments had passwords cracked, almost doubling from 25% final 12 months.
Get the Picus Blue Report 2025 now for a complete take a look at extra findings on prevention, detection, and knowledge exfiltration tendencies.
