PatchReporter

Docs

N-able N-central Not Detecting Patches: Check Scans and Update Scope

By

Troubleshoot N-able N-central not detecting patches. Check collection freshness, update scope and endpoint availability.

Category: Troubleshooting | Published | Updated

Quick Answer

Run Patch Detection on Demand for the affected device and check the returned inventory. It creates a temporary detection window; editing that window does not refresh the scan or change your installation schedule.

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: N-central detection on demand

What You'll Get

  • Find where scanning, approval or installation stopped
  • Check the result and collect useful details for support

How Patching Works

N-central uses separate windows for detection, download, installation and restart. On-demand detection refreshes patch inventory without changing the regular installation schedule.

N-central detection on demand.

Checks to Run in Order

  1. Use Add Task > Patch Management > Patch Detection on Demand on the selected device.
  2. Capture task outcome and returned inventory time.
  3. Do not edit generated temporary-window times as an inventory repair.

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

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 N-able N-central not detecting patches?

Run Patch Detection on Demand for the affected device and check the returned inventory. It creates a temporary detection window; editing that window does not refresh the scan or change your installation schedule.

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 N-able N-central. Sign up for free and connect your Windows devices.

Sign up for free

Related Docs

Browse all docs or see product features.