PatchReporterDocs
Kaseya VSA Missing Patches: Verify Inventory and Applicability
Investigate Kaseya VSA missing patches. Compare current inventory, update applicability and installed evidence before changing policy.
Quick Answer
For VSA 9 Patch Management, compare Patch Scan with policy membership. For VSA 10, trace global, policy and individual rules. The policy evidence required depends on the product generation and active module.
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 10 Automating patch review
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
- Capture the latest scan from the module actually managing the device.
- For VSA 9 Patch Management, record expected policy membership.
- For VSA 10, trace global, policy and individual rule evaluation.
Interpret the Result
| Evidence | Next action |
|---|---|
| Current scan offers the update | Inspect approval and the last eligible installation; the backlog may be real. |
| Installed evidence and a later scan agree | Keep update/build identity with the explanation for the older report. |
| Expected KB is no longer applicable | Verify the replacement target against Microsoft release information before closing the gap. |
Validate the Outcome
After a fresh scan, check whether the update is still needed, installed or replaced by a newer update. Save the update and device details, and keep any outstanding security updates on your follow-up list.
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.