Technical Support

Need help?

 

Issues in Systems Management Patch audits on Windows devices after installing certain Microsoft KB patches

Information applies to:

Products
Panda Systems Management

Issue Status
Tracking ID: SPE-32
Status: Resolved
Type of solution: Workaround


Symptoms
Unable to do Systems Management Patch audits on Windows devices after the installation of certain June/July Microsoft KB patches.

  • Patch status shows No data under Summary


  • Error 0x8002802B is shown under Activities

IMPORTANT!

This issue is caused by an unannounced change made by Microsoft to the backend API powering Windows Update patch scans related to KB5037771 and other KB patches. However, not all users who have installed KB5037771 will experience this issue.

We DO NOT recommend attempting to remove these update patches. What's more, blocking these patches may prevent your device from receiving crucial security updates.
However, for customers and partners looking to adjust their Patch Management Policies, this is the list of related Microsoft KBs:
  • KB5037959 (SSU)
  • KB5039212
  • KB5039302 (Preview)
  • KB5039338 (SSU)
  • KB5040442
How to check if my device is affected
Follow these steps to verify if your device is affected:
  1. Open Powershell.
  2. Paste this line of code:

    $varUpdateSearcher=$(New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher()
  3. Press Enter.
  4. Paste this line of code:

    ($varUpdateSearcher.Search('IsInstalled=1').Updates | select -first 1).title
  5. Press Enter.

    Non affected devices will show a random KB installation. Affected devices will not return any message:

Workaround
Follow these instructions to apply a workaround until Microsoft releases a fix.
  1. Go to the Components tab in Systems Management.
  2. Import the Systems Management WUA JSON Adjustment Tool for Windows component and run it on affected devices.

    IMPORTANT! When you run the component, select the following options:

    usrAction: Make Adjustment
    usrReboot: True
  3. The device will restart twice. The first reboot will take place 60 seconds after the component has been run, and the second one, after the next login is detected.
  4. If you leave usrReboot as False, you will have to manually restart the device twice after the component has been run.



Help nº- 20240712 300187 EN
ALWAYS ONLINE TO HELP YOU TWITTER FORUM
ALWAYS ONLINE TO HELP YOU TWITTER FORUM