Docs
ConnectWise Automate Not Detecting Patches? What It Means
Troubleshoot ConnectWise Automate not detecting patches by checking inventory freshness, WUA and BITS health, update-source policy, and local Windows evidence.
Troubleshooting for MSPs and IT admins troubleshooting ConnectWise Automate patch detection gaps
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 a ConnectWise Automate patch scan is not detecting expected updates, the usual causes are stale patch inventory, WUA or BITS health problems, changed applicability, update-source policy issues, or local Windows Update failure.
ConnectWise Automate not detecting patches is the page to use when the patch never shows up in Automate inventory or scan results even though you expect it to be there.
This is mainly a detection and inventory problem. The important distinction is whether Patch Manager inventory is stale, WUA or BITS could not return clean scan data, update-source policy is wrong, or the patch is no longer the real applicable target.
What You'll Get
- Separate failed detection from changed applicability
- Check freshness and endpoint evidence before changing Automate workflow
Why the Inventory Is Not Surfacing the Patch
Detection gaps in Automate usually come from stale patch-state data, a misunderstanding about the current applicable update, or endpoint Windows Update behavior that never returned clean inventory. In Automate, an empty or stale patch view often points to WUA or BITS failure before it points to an approval problem.
Empty or Stale Patch Inventory
- Check patch-state freshness.
- Check whether inventory is empty or simply old.
- Check whether the expected update is still currently applicable.
- Check reboot state.
- Check local Windows Update behavior.
Use verification, event IDs, and logs.
WUA, BITS, and Update Source Issues
If Automate is not surfacing patches at all, treat WUA, BITS, WSUS, proxy, and firewall path as first-line suspects. Empty patch windows and missing inventory often point to Windows Update not returning usable data rather than Automate simply hiding a patch.
Applicability and Supersedence Problems
Not every non-detected patch is a broken scan. The expected update may have been superseded, replaced by a newer rollup, or no longer be the current applicable target for that machine.
How to Confirm Whether Detection Really Failed
- Refresh patch state.
- Validate current applicability.
- Check WUA and BITS health locally.
- Check whether the endpoint is pointed at the correct update source.
- If detection still fails locally, move into Windows troubleshooting.
Where to Go Next
If the patch is actually failing to install after detection, go to ConnectWise Automate updates not installing. If the patch is detected or installed but the dashboard still says missing, go to ConnectWise Automate missing patches. If the expected update changed or the inventory is simply stale, continue to how to check for Windows updates or back to ConnectWise Automate patching not working.