Windows Update Agent API

Winsage
June 12, 2026
Microsoft resolved an issue affecting the installation of Windows updates released since May 2025, which primarily impacted users using the Windows Update Standalone Installer (WUSA) from a network share, especially in enterprise environments. The problem was significant for devices running Windows 11 24H2/25H2 and Windows Server 2025, but did not occur when handling a single .msu file or when files were stored locally. In August 2025, Microsoft acknowledged that updates installed using WUSA might fail with error ERRORBADPATHNAME when multiple .msu files were involved. A Known Issue Rollback Group Policy was implemented in September 2025 to mitigate the impact on home and non-managed business devices. The issue was ultimately resolved with cumulative updates released in June 2026 for Windows 11 (KB5079391) and Windows Server 2025 (KB5094125). Microsoft provided a workaround for users experiencing difficulties with prior updates by suggesting they save .msu files locally for installation. Users were also advised to wait at least 15 minutes after installing an .msu file via WUSA before checking the Update History page. Additionally, Microsoft had previously addressed another issue in April 2025 that affected enterprise customers installing security updates via WSUS, which recurred in the August 2025 updates. Microsoft warned customers about potential issues with installing the latest monthly updates on devices upgraded to Windows 11 24H2 or 25H2.
Winsage
August 18, 2025
Microsoft is addressing an issue with the Windows Update Standalone Installer (WUSA) that affects the installation of Windows updates from network shares, primarily impacting Windows 11 24H2 and Windows Server 2025 systems in enterprise networks. The problem leads to updates failing with the error ERRORBADPATHNAME when multiple .msu files are present on a network share. This issue does not occur with single .msu files or local installations. A Known Issue Rollback (KIR) is available to mitigate the problem for home and non-managed business devices, while IT administrators can implement a Group Policy fix for affected systems. Users can also avoid the issue by saving .msu files locally for installation.
Winsage
July 14, 2024
Microsoft has noted a bug in the KB5039302 update for Windows 11 and is working to limit its effects. They are using the Known Issue Rollback feature to fix the problem without requiring users to take extra steps. However, in some cases, IT teams may need to use special group rules to fully solve the issue.
Winsage
July 13, 2024
Microsoft has resolved an issue caused by the June 2024 KB5039302 preview update, impacting only client platforms in enterprise environments. To resolve the bug, admins must install and set up a KIR Group Policy targeting the affected Windows versions.
Winsage
July 12, 2024
Microsoft has confirmed a new issue with the Windows Update Agent API in the latest Windows 11 update, KB5039302. This bug disrupts PowerShell or VBScript scripts using the API, resulting in empty query results for certain objects and error code 0x8002802B "TYPEEELEMENTNOTFOUND." The issue can be resolved using the Known Issue Rollback feature, and IT administrators may need to implement special Group Policies to address specific issues like the error code.
Search