# APD Shows Missing Patches When None Missing

Last Updated On: 31 Oct 2026

An Automate Patch Deployment (APD) task can show patches as missing, or show a high missing count, when those patches are not waiting to be deployed on the target computers.

## Cause

- The latest version of the application is already installed on the computer.
- The computer posted **This version already exists** and has not been rebooted, so a later update still shows as missing.
- Not every target has finished a patch scan, so the missing report is incomplete.
- The APD task has not started, or agents were offline when it last ran.

## Resolution

If the operating-system build or version displayed in the console does not change after patching, record the page and exact column name. Compare it with the operating-system value on the endpoint and the last successful scan. **Agent Version** identifies the management agent. Follow the [version-reporting checks](https://www.manageengine.com/products/desktop-central/kb/patch-management/patch-issues.html). An APD missing count does not establish when an Inventory build field will refresh.

If the task records a failed deployment rather than a count-only discrepancy, open its computer-level execution details. Follow [Patch Deployment Troubleshooting](https://www.manageengine.com/products/desktop-central/help/patch-management/patch-deployment-troubleshooting.html) for the full remark. If your account cannot export the details, ask an authorized administrator to provide them.

If an approved patch is missing on a computer but absent from the APD task, see [Patch eligibility in Automated Patch Deployment](https://www.manageengine.com/products/desktop-central/kb/patch-management/patch-issues.html#apd-patch-eligibility). Approval alone does not establish that the task includes that update.

An installation result and the latest patch scan describe different stages. A Not Applicable result does not by itself confirm that the update is installed. Check the same patch ID on the target computer after a fresh scan completes. If the mismatch remains, collect the deployment result and scan times for support instead of repeatedly redeploying the update.

1. Open the APD task **System View**. If the latest application version is already installed, that application is not listed for that computer.
2. If the remark is **This version already exists**, verify the patch type and installation/reboot outcome, then complete a fresh scan. For definition and other update types, see [patch detection results](https://www.manageengine.com/products/desktop-central/help/patch-management/manual-deployment.html#understanding-patch-detection-results). If the mismatch remains, collect the results for Support.
3. Wait until all target computers have completed a patch scan before you generate or trust the missing-patches report.

## Related

- [Automate Patch Deployment](https://www.manageengine.com/products/desktop-central/help/patch-management/apd.html)
- [Assessing Automate Patch Deployment Tasks](https://www.manageengine.com/products/desktop-central/help/patch-management/assessing-automate-patch-deployment.html)