PatchReporter

Docs

Kaseya VSA Updates Not Installing: Check Eligibility and Errors

By

Troubleshoot Kaseya VSA updates not installing. Separate a queued or ineligible request from a failed Windows installation.

Category: Troubleshooting | Published | Updated

Quick Answer

Identify the deployment mechanism first. VSA 9 Patch Management scheduled updates and Software Management deployment profiles are distinct. Keep the module identity with the attempted update and error so troubleshooting follows the correct execution path.

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.

Sign up for free

Prefer an RMM assessment? Request an integration

Read the vendor guide: VSA 9 Patch / Update 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.

VSA 9 Patch / Update Management.

Checks to Run in Order

  1. Identify Patch Management, Software Management or VSA 10 as the executor.
  2. Record the selected device, update and deployment outcome.
  3. Match the Windows error to that attempt before changing a policy/profile.

Interpret the Result

Evidence Next action
No start recorded Investigate eligibility, device availability and scheduling.
An attempt returned an error Preserve the error and follow the matching Windows/vendor resolution.
Installation ended but restart remains Complete the agreed restart and check a new scan before reporting success.

Validate the Outcome

Test the fix on one affected device. Check the installation result, complete any required restart and run a fresh scan. Use those results to decide whether the fix is ready for the remaining devices.

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

Put the guide into practice

Use this guide with PatchReporter.

See failed updates, successful installs and available Windows updates in one free workspace.

Sign up for free

FAQ

Where should I start with Kaseya VSA updates not installing?

Identify the deployment mechanism first. VSA 9 Patch Management scheduled updates and Software Management deployment profiles are distinct. Keep the module identity with the attempted update and error so troubleshooting follows the correct execution path.

What should I send to support?

Include the device ID, Windows build, update KB or title, patch policy, scan and installation times, and the exact error. Add relevant logs and a short description of what you expected to happen.

See which devices still need patching

Review failed updates, successful installations and available Windows updates in PatchReporter alongside Kaseya VSA. Sign up for free and connect your Windows devices.

Sign up for free

Related Docs

Browse all docs or see product features.