This article addresses the issue with a recent Windows patch upgrade/scan and how it's affecting patch scans run by the SuperOps agent. Currently, because of the faulty Windows patch, devices that have installed the recent patches will not be able to perform scans, and the patch status will report "No Data".
What is the issue?
Microsoft confirmed that there is an issue with the Windows patch KB5039302, an optional non-security update that was released on June 25th. The bug is affecting client versions 22H2 and 23H2 of Windows 11. According to Microsoft’s official documentation, the patch might impact applications using Windows Update Agent API (WUA). Due to this issue, your scans may fail.
How can I resolve the issue?
As a workaround, Microsoft has mitigated the issue using Known Issue Rollback (KIR). IT administrators can resolve this issue by installing and configuring the special Group Policy. See below for details.
Via SuperOps Script
We have come up with a workaround that will help you resolve this issue in the short term. Please see instructions below, and keep in mind that the script will reboot the system.
Note: While this solution has worked in our limited testing, it may not be effective in all cases. Use with caution. Please be aware that if the script brings about any issues, SuperOps cannot be held responsible.
Go to Scripts > Community.
Search for "Roll back KB5039302 - Patch Scan Issue" to locate the script and hit Import.
Run the script using Bat language as a system user.
If you have multiple affected assets, you can bulk select them and run the script in one shot.
You can also set up a one-time policy to run the script in bulk.
Go to the policy that applies to your affected assets.
Go to Scheduled Actions.
Enter a name for the action and select When to Run as Once.
Select "Roll back KB5039302 - Patch Scan Issue" from the script dropdown and hit Save.
Running this script will restart the system. Please wait for the system to restart successfully, it will take about 2 mins. Once restarted, attempt a patch scan to see if the issue has been fixed.
Via GPO
Please refer to the documentation here for step-by-step instructions.
Via Microsoft Intune
Please refer to the documentation here for step-by-step instructions.