Microsoft patches WUSA network-share update failures in June 2026 Patch Tuesday

Microsoft's June 2026 Patch Tuesday delivers a permanent fix for a persistent deployment failure affecting enterprise patching workflows, closing a gap that had persisted since May 2025.

What broke and when

The problem traces back to updates released on 28 May 2025 (KB5058499) and those that followed. When administrators used the Windows Update Standalone Installer (WUSA) to deploy .msu packages directly from a network share containing more than one such file, the operation failed with an ERROR_BAD_PATHNAME error. Single-file installs and locally stored packages were unaffected — making the failure specific to a common enterprise mass-deployment pattern.

Microsoft publicly acknowledged the issue in August 2025. The scope is confined to managed environments: Windows 11 versions 24H2 and 25H2, and Windows Server 2025. Consumer devices rarely use WUSA against network shares, so home users were largely unaffected.

Interim mitigations

Before a code fix was available, Microsoft applied a Known Issue Rollback (KIR) Group Policy in September 2025, which addressed the symptom automatically on home and unmanaged business endpoints — though not on domain-joined machines subject to stricter policy controls.

For managed environments still waiting on a permanent patch, Microsoft advised saving .msu files locally on the target device before running WUSA. The company also flagged a secondary nuance: administrators who restarted a device after a WUSA install should wait at least 15 minutes before consulting the Update History page in Settings, as the interface could otherwise misreport installation status.

The June 2026 fix

The definitive resolution arrives in two cumulative updates shipped as part of June 2026 Patch Tuesday: KB5079391 for Windows 11 and KB5094125 for Windows Server 2025. Both updates supersede the workaround guidance for all affected configurations.

Broader pattern of WUSA and WSUS failures

This is not an isolated incident. In April 2025, Microsoft resolved a separate bug that had blocked enterprise customers from delivering that month's security updates through Windows Server Update Services (WSUS). An analogous failure resurfaced with August 2025's Windows 11 updates, which errored out with 0x80240069 codes. Earlier this week, Microsoft separately cautioned that some devices upgraded to Windows 11 24H2 or 25H2 may encounter difficulty installing the most recent monthly updates — a distinct issue still under investigation.

The accumulation of enterprise patching failures over the past 14 months points to ongoing fragility in update-delivery paths that many organizations rely on for compliance and vulnerability management.