Datto RMM: How to address Patch Status of "No Data"

Follow

Topic

This article describes how to address a Patch Status of "No Data."

Environment

  • Datto RMM

Description

A Patch Status of "No Data" can happen on Windows 10 devices that have been recently updated, as all former patch history is removed, and there may be no updates applicable for installation from Microsoft until the following month. But more commonly, the "No Data" status is the result of a patch audit failure

Patch audit errors happen when patch management passes off the patch inquiry task to Windows Update on the endpoint, and Windows Update errors on the local device, returning a hexadecimal HRESULT code like 0x8024001E or 0x8024002E

You can see the exact error in the activity log for the device, indicated by a "patch audit failure" with a red progress bar. If you click on StdOut, you can see the exact error code and message.

fig1.PNGFigure1: Patch Audit Failure (click to enlarge)


This error code comes directly from Windows itself, and troubleshooting should focus on the local device and not Datto RMM. We can, however, offer the following suggestions:

1. Try rerunning an audit from Actions → Request Device Audit. Often, audit errors are temporary and related to booting, which may be resolved when audited again. If a new audit succeeds, it won't post a successful audit to the activity log (we only post failures). Still, you can tell it was successful if the patch status changes, and the manage tab for the device shows patches that are approved/installed/denied instead of 0 for each. 

fig1.PNGFigure 2: Request device audit(s) (click to enlarge)

2. Check any applied Windows Update policies to see if there is a WSUS configured. If the policy has changed the device settings to look for patches on a WSUS instead of the Windows API, but the WSUS settings are invalid, which will prevent the audit from finding patches correctly. In some cases, the WSUS may also be misconfigured and will not present and patch data to the device without an error.

3. Other than the suggestions above, troubleshooting should be done locally, as the problem most likely isn't with RMM. We offer a component called Windows Update Diagnostic Tool that can help collect additional info, and Windows also provides a Windows Update Troubleshooter tool that you can run on the affected device.


Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Want to talk about it? Have a feature request?

Head on over to our Datto Community Forum or the Datto Community Online.

For more Business Management resources, see the Datto RMM Online Help and the Autotask PSA Online Help .

Still have questions? Get live help.

Datto Homepage