Docs
Datto RMM Updates Not Installing? What to Check First
Troubleshoot Datto RMM updates that are not installing by checking policy inheritance, reboot blockers, patch data freshness, and underlying Windows Update failure.
Troubleshooting for MSPs and IT admins troubleshooting Datto install failures
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.
Quick Answer
Direct answer: when Datto RMM updates are not installing, the failure usually sits in policy inheritance, reboot blockers, device timing, or Windows Update itself.
Datto RMM updates not installing usually means the endpoint never reached a clean install phase because of policy inheritance, reboot debt, device timing, or Windows Update failure.
The key is to separate Datto workflow blockers from Windows install failure before rerunning the same deployment.
What You'll Get
- Separate Datto workflow blockers from Windows install failure
- Check policy inheritance and endpoint proof before rerunning deployments
Why Datto RMM Says Updates Are Not Installing
Datto can approve and target an update correctly while the endpoint still fails to install it. The usual blockers are bad inheritance, missed windows, reboot debt, or Windows Update failure on the device.
How to Check Whether Windows or Datto RMM Is the Real Failure Layer
- Check policy inheritance.
- Check device availability.
- Check reboot state.
- Check local Windows Update errors.
- Check whether the same update keeps failing.
Use verification, event IDs, and logs.
Why a Stalled Install View in Datto RMM Can Be Misleading
- Approved but not installed: the device never had a real install opportunity.
- Installed but still unhealthy: reboot completion is missing.
- Repeated retries: the endpoint issue is local.
How to Confirm Install State Outside Datto RMM
Use endpoint evidence directly. This is also why patch compliance vs patch status matters.
What Usually Restarts the Update Flow
- Validate policy inheritance.
- Confirm the device was available.
- Clear reboot debt.
- Check Windows logs and event IDs.
- If Windows itself is failing, move to the Windows install-failure path.
When Updates Look Stuck but Patching Is Still Progressing
If the device simply missed timing or the view is stale, the workflow may not be broken. Continue to Windows Update fails to install or Datto RMM patching not working.