Impact: This issue primarily impacts script callers using Windows Update Agent API to manage Windows Updates. Originating KB URL: https://support.microsoft.com/en-us/topic/5039302 Originating KB Release Date: 2024-06-25T14:00:00-07:00 Originating Build: 22621.3810 Resolved KB URL: https://support.microsoft.com/en-us/topic/5040527 Date Resolved: 2024-07-25T10:00:00-07:00 All Updates: ------------------------------------------------------ July 25, 2024 17:00 PM After installing the June 2024 Windows preview update, released June 25, 2024 (KB5039302 (https://support.microsoft.com/help/5039302)) and later updates, you might face issues using Windows Update Agent API (https://learn.microsoft.com/windows/win32/api/_wua/) (WUA) from your script (PowerShell, VBScript, etc.) while searching for Windows updates. Due to this issue, you might get an empty result when querying the properties of IUpdate (https://learn.microsoft.com/windows/win32/api/wuapi/nn-wuapi-iupdate) objects present in the IUpdateCollection (https://learn.microsoft.com/windows/win32/wua_sdk/iupdatecollection-properties) and error code 0x8002802B (TYPE_E_ELEMENTNOTFOUND) when calling methods on the object from your script. Organizations using Windows Automatic Updates are not impacted by this issue. Home users of Windows using Home or Pro editions are unlikely to face this issue as their devices are managed using Windows Automatic Updates that doesn't run into this issue. Resolution: This issue was resolved by Windows updates released July 25, 2024 (KB5040527 (https://support.microsoft.com/help/5040527)), and later. We recommend you install the latest update for your device. It contains important improvements and issue resolutions, including this one. If you install an update released July 25, 2024 (KB5040527 (https://support.microsoft.com/help/5040527)) or later, you do not need to use a Known Issue Rollback (KIR) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831) or a special Group Policy to resolve this issue. If you are using an update released before July 25, 2024, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>. Group Policy downloads with Group Policy name: - Download for Windows 11, versions 23H2 and 22H2 (https://download.microsoft.com/download/3944f364-6483-49ab-af0d-3e2bd80dedaf/Windows%2011%2022H2%20KB5039302%20240711_20301%20Known%20Issue%20Rollback.msi) - Windows 11 22H2 KB5039302 240711_20301 Known Issue Rollback Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting. Note that the Group Policy will temporarily disable the change causing the script issue. Affected platforms: - Client: Windows 11 version 23H2, Windows 11 version 22H2 - Server: None Click here (https://admin.microsoft.com/Adminportal/Home?#/windowsreleasehealth/:/wrhpreferences) to manage email notifications for Windows known issues ------------------------------------------------------ July 12, 2024 17:17 PM After installing the June 2024 Windows preview update, released June 25, 2024 (KB5039302 (https://support.microsoft.com/help/5039302)) and later updates, you might face issues using Windows Update Agent API (https://learn.microsoft.com/windows/win32/api/_wua/) (WUA) from your script (PowerShell, VBScript, etc.) while searching for Windows updates. Due to this issue, you might get an empty result when querying the properties of IUpdate (https://learn.microsoft.com/windows/win32/api/wuapi/nn-wuapi-iupdate) objects present in the IUpdateCollection (https://learn.microsoft.com/windows/win32/wua_sdk/iupdatecollection-properties) and error code 0x8002802B (TYPE_E_ELEMENTNOTFOUND) when calling methods on the object from your script. Organizations using Windows Automatic Updates are not impacted by this issue. Home users of Windows using Home or Pro editions are unlikely to face this issue as their devices are managed using Windows Automatic Updates that doesn't run into this issue. Resolution: This issue is resolved using Known Issue Rollback (KIR) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831). IT administrators can resolve this issue by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback (https://learn.microsoft.com/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). Group Policy downloads with Group Policy name: - Download for Windows 11, versions 23H2 and 22H2 (https://download.microsoft.com/download/3944f364-6483-49ab-af0d-3e2bd80dedaf/Windows%2011%2022H2%20KB5039302%20240711_20301%20Known%20Issue%20Rollback.msi) - Windows 11 22H2 KB5039302 240711_20301 Known Issue Rollback Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting. Note that the Group Policy will temporarily disable the change causing the script issue. Next Steps: We are working to include the resolution in a future Windows update. Once the update with the resolution is released, organizations will not need to install and configure this Group Policy to address this issue. Affected platforms: - Client: Windows 11 version 23H2, Windows 11 version 22H2 - Server: None Click here (https://admin.microsoft.com/Adminportal/Home?#/windowsreleasehealth/:/wrhpreferences) to manage email notifications for Windows known issues