PatchReporterDocs
Kaseya VSA Not Detecting Patches: Check Scans and Update Scope
Troubleshoot Kaseya VSA not detecting patches. Check collection freshness, update scope and endpoint availability.
Quick Answer
VSA 9 Patch Management detects installed and missing updates through Patch Scan; Software Management has its own scan profile. VSA 10 evaluates updates through Patch Review. Identify which engine supplied the empty or stale result.
Free patch reporting
See which endpoints need attention.
Review Windows patch status and update failures in one workspace, then use this guide to plan your follow-up.
Prefer an RMM assessment? Request an integration
Read the vendor guide: VSA 9 Software Management
What You'll Get
- Find where scanning, approval or installation stopped
- Check the result and collect useful details for support
How Patching Works
VSA 9 Patch Management uses Patch Scan and policy membership; Software Management has separate scan and deployment profiles. VSA 10 uses global, policy and individual patch rules. Start with the module managing the affected device.
Checks to Run in Order
- Confirm the scan belongs to the active engine and current endpoint.
- Review the correct scan profile or Patch Scan result.
- Keep version/module identity with the expected applicable update in an escalation.
Interpret the Result
| Evidence | Next action |
|---|---|
| No completed inventory returned | Investigate collection and communication; patch state is still unknown. |
| Current inventory has no applicable candidate | Check update type and OS applicability before diagnosing scan failure. |
| Windows offers the update but fresh managed inventory omits it | Escalate with matching device/update identities and both scan results. |
Validate the Outcome
Check one affected device and an update it should receive. Save the scan time and returned update list. If the scan fails, repair collection before deciding whether the device is up to date.
Prepare a Useful Escalation
Send the device ID, Windows edition and build, update KB or title, patch policy, scan time, installation time and exact error. Include the time zone, relevant logs and what changed after your test.
Use the Windows Update logs guide to find the logs for the failed scan, download, installation or restart.
Continue With the Right Guide
Official References
- VSA 9 Patch / Update Management — Patch Scan, policy membership and deployment paths.
- VSA 10 Automating patch review — Global, policy and individual patch rules and precedence.
- VSA 9 Software Management — Separate scan/deployment profiles and update strategies.