×
×
×
×

Patch Issues

1. Confirm the Exact Identifier

For a Linux vulnerability, select the affected Linux platform and compare the distribution vendor's package and remediation guidance. A Windows application patch with a similar name is not a Linux remediation. Distribution packages can contain backported fixes. Compare the vendor's affected and fixed package information rather than the upstream version number alone. See Linux Patch Management and Vulnerability Remediation.

An advisory or detection identifier does not necessarily identify a deployable patch package. For Secure Boot certificate readiness and updates, follow the Secure Boot certificate procedure and its prerequisites. Do not use an assumed Patch ID or an unspecified MSU package for this workflow.

7. Check the Vulnerabilities View

A detected vulnerability does not always have a deployable patch. Follow Vulnerability Remediation to check the available remediation and guidance for an application that remains vulnerable at its latest version.

Navigate to:

Threats -> Vulnerabilities

For This version already exists while the patch remains missing, compare the exact update, target version and reboot outcome. Follow Understanding patch detection results.

For the remark This version is not applicable for this target, compare the exact update with the target's installed product edition and version and its latest completed scan. The remark alone does not prove that the application is absent. See target-version applicability checks. For macOS, verify the installed application and update on the affected Mac; Windows-specific diagnostic branches do not establish the cause.

For the reverse mismatch, where an application patch appears as missing but the application cannot be found, verify the installation directly on the endpoint, including its edition, instance and any relevant hardware. Compare Inventory and patch-scan times, then complete a fresh patch scan. If the mismatch remains, collect the detection and installed-instance evidence, screenshots and agent logs. Declining the patch is optional; do not remove registry data or residual files unless the vendor identifies them as part of a supported removal procedure. For an intentional exception, see group-scoped decline.

If an application is independently verified on the endpoint but absent from Software & Components or the expected Missing Patches view, confirm the exact product edition, version and installation instance. Complete a fresh patch scan and compare the same endpoint and Patch ID using the relevant view and patch settings. If the mismatch remains, collect the application’s own installed-instance details, scan times, screenshots and agent logs for Support. Continue this evidence collection even when the deployment Troubleshoot view is unavailable.

If a declined patch appears to have been installed again, verify the exact Patch ID, application or family and the group to which the decline applies. Use Installed Patches audit details to identify the actual installation source and task. Compare the effective decline with the task targets and the agent metadata and scan times. If an APD task still deploys the patch in the declined scope, provide the decline and target screenshots, task report and agent logs to Support.

To decline patches from the Missing Patches view, navigate to Patch Mgmt (Threats and Patches) → Patches → Missing patches, then search for the KB in the patch description column. Select the patches, click Decline patches, and select the group. Repeat for each additional KB. SeeDecline Patch.

Declining a patch removes it from Missing Patches only for the selected group. Use All Computers when the patch must be declined throughout the managed scope. A declined, non-superseded patch remains visible in the Decline Patch view.

Declining a patch in Endpoint Central does not prevent the endpoint's native Windows Update service from installing it. If Windows Update is also active, use the supported controls described in Disable Windows Automatic Updates.

For Deployment Failed, open the affected task and computer execution details. Export the task summary and record the Patch ID, full remark and attempt time. Follow Patch Deployment Troubleshooting for that result and Manual Deployment for status interpretation. A generic failed status does not identify UAC, antivirus or component corruption.

For an unexpected deployment of a declined update, include the affected task or computer summary and the decline rule. Record the selected group, the rule type (patches, applications or families), and the exact selected items. Compare them with the deployed Patch ID and application before concluding that the decline rule did not apply. See Decline Patch and the APD task Summary.

For Problem while generating patch scan data., recent agent contact does not confirm a successful patch scan. Record the failed scan time and follow scan-data generation troubleshooting.