Microsoft Snafu: Network Share Update Fiasco Gets a Patch!
Microsoft has tackled a Windows update glitch using the Windows Update Standalone Installer (WUSA) from a network share. This issue, affecting enterprise systems, has been mitigated through Known Issue Rollback. For those feeling nostalgic for error messages, simply try updates from a network share—otherwise, save those .msu files locally for a smoother ride.
Hot Take:
Oh Microsoft, you’ve done it again! Just when we thought Windows updates couldn’t get any more unpredictable, you go ahead and throw a curveball at IT admins with your WUSA mishap. It’s like a soap opera, but with less drama and more error codes. Let the adventures of troubleshooting continue!
Key Points:
- Microsoft resolved an issue affecting Windows updates via the Windows Update Standalone Installer (WUSA) from network shares.
- The problem mostly impacted Windows 11 24H2 and Windows Server 2025 systems in enterprise networks.
- Updates could fail with an “ERROR_BAD_PATHNAME” error when multiple .msu files were on the same network share.
- Microsoft is rolling out a Known Issue Rollback (KIR) to mitigate the issue automatically for home and non-managed business devices.
- Admins can manually resolve the issue on managed devices via Group Policy settings or by storing .msu files locally.
Already a member? Log in here