Docs
ConnectWise Automate Updates Not Installing? What to Check First
Troubleshoot ConnectWise Automate updates that are not installing by checking WUA health, reboot blockers, retry exhaustion, policy side effects, and underlying Windows Update failures.
Troubleshooting for MSPs and IT admins troubleshooting Automate install failures
Free Audit
Run a Free ConnectWise Automate Windows Update Audit
If you want to validate ConnectWise Automate patch risk across devices instead of relying on one patch status view, run the free audit against your Automate environment.
Quick Answer
Direct answer: when ConnectWise Automate updates are not installing, the failure usually sits in WUA or BITS health, reboot blockers, retry exhaustion, policy side effects, or Windows Update itself.
ConnectWise Automate updates not installing is the page to use when patches are approved, targeted, and still fail to complete on the endpoint.
This is mainly an install-failure problem. The key is to identify whether Windows Update Agent is broken, reboot state is blocking completion, Automate stopped retrying the patch, or policy and update-source controls are preventing a clean install path.
What You'll Get
- Separate Automate workflow blockers from Windows install failure
- Check approval scope and endpoint proof before rerunning deployments
Why Approved Updates Still Fail to Install
Automate can approve and target an update correctly while the endpoint still fails to install it. The usual blockers are broken Windows Update prerequisites, stale reboot flags, failed retry state that prevents more attempts, or update-source and policy controls that keep Windows from completing the install path.
Common Install Failure Patterns
- Check WUA and BITS first. Empty inventory, repeated failures, or long-running scans often mean Windows Update itself is unhealthy.
- Check reboot blockers. A stuck pending reboot can leave the device in a half-complete state for multiple cycles.
- Check retry exhaustion. Automate can stop reattempting patches after repeated failures unless you reset the right state.
- Check update source and policy. WSUS remnants, UI-disabled modes, or policy tattooing can keep installs from progressing cleanly.
Use verification, event IDs, and logs.
Reboot Blockers and Pending State
Automate patching can look stuck when the endpoint never clears pending reboot state. That leaves installs half-finished, scans stale, and later patch cycles blocked even though the policy itself is not the main issue.
Retry Exhaustion and Stuck Failure State
One Automate-specific trap is failure state that stops more attempts. If the same patch failed repeatedly and then no longer retries, you may be dealing with stale Patch Manager state rather than a new approval problem.
How to Confirm the Install Really Failed
- Check WUA, BITS, and Windows Update-related services.
- Check Windows Update logs and event IDs.
- Confirm whether the same KB keeps failing or has stopped retrying.
- Confirm the device is not only waiting on reboot or stale post-install inventory.
Where to Go Next
If the patch is showing as missing rather than failed, go to ConnectWise Automate missing patches. If the patch never appeared in inventory or scan results, go to ConnectWise Automate not detecting patches. If Windows itself is failing, continue to Windows Update fails to install or back to ConnectWise Automate patching not working.