Docs
Datto RMM Patching Not Working? Fix No Data, Approval, and Install Errors
Troubleshoot Datto RMM patching when patch status shows no data, approvals fail, or Windows updates do not install.
Troubleshooting for MSPs and IT admins troubleshooting Datto RMM patching
Free Audit
Run a Free Datto RMM Windows Update Audit
If you want to validate Datto RMM patch risk across devices instead of relying on stale patch status alone, run the free audit against your Datto RMM environment.
Short Answer
Direct answer: Datto RMM patch issues usually come down to missing patch scan data, policy approval gaps, or endpoint-level Windows Update failures that Datto is surfacing rather than causing.
The first split to make is no visibility versus failed installation. Those are different fix paths.
Datto RMM patch issues usually come down to missing patch scan data, policy approval gaps, or endpoint-level Windows Update failures that Datto is only surfacing rather than causing.
When patching is not working, first determine whether the problem is no visibility or failed installation. Those are different fix paths in Datto RMM.
Caution: do not widen approvals or rewrite policy before you know whether the device is actually returning current patch data. Visibility problems and install problems are not the same branch.
Use this guide to troubleshoot Datto RMM patching when patch visibility, approval flow, install status, or reporting does not match endpoint reality.
Fast Triage in Datto RMM
- Check whether the device returns patch data at all.
- Review the site or device patch policy and approval logic.
- Compare the reported patch error with local Windows Update behavior.
- Confirm the endpoint has completed the needed reboot or servicing prerequisites.
Common Failure Patterns
| Symptom | Likely cause | What to check first |
|---|---|---|
| No patch data on the device | Scan did not complete or the patch subsystem is unhealthy | Use Datto's no-data troubleshooting steps before changing approvals. |
| Patches remain pending | Policy does not approve the patch class or product the way you expect | Review the assigned patch policy and device/site inheritance. |
| Patches fail with install errors | Local Windows Update or servicing stack failure | Test Windows Update directly on the endpoint and compare error details. |
| Install requires repeated attempts | Reboot or prerequisite chain is incomplete | Check reboot state and whether additional servicing updates are outstanding. |
What the Official Docs Point To
Datto's own troubleshooting guidance separates visibility failures from installation failures. That is the right operational split for UK MSPs and other teams searching this topic: do not rework approval policy until you know the device is actually returning usable patch data.
If the endpoint is the real problem, continue to Windows Update fails to install common fixes, update requires restart, or where are Windows Update logs. If the issue is mostly visibility and stale data, use patch dashboard. If the bigger business problem is inaccurate RMM reporting, continue to RMM patch report wrong or patch report not accurate.
More Datto Troubleshooting Paths
Use the more specific Datto RMM pages when the broad workflow is not enough: Datto RMM missing patches, Datto RMM updates not installing, and Datto RMM not detecting patches.
Common Mistakes
- Changing approval policy before proving the device is returning current patch data.
- Ignoring reboot debt when patches remain pending.
- Assuming Datto caused every Windows Update failure it reports.
- Treating no-data and install-error states like the same issue.