Reverting Changes After Patch Failure

Scenario

If a patch deployment is reported as successful in Patch Manager Plus, but after the system reboots the patch is still listed as Missing, it indicates that the update was rolled back by Windows during the reboot process. This behavior is typically caused by an environmental issue on the endpoint rather than a deployment issue with Patch Manager Plus.

Cause

Patch Manager Plus is responsible for downloading and initiating the patch installation. Once the installation reaches the reboot stage, the remaining commit operations are performed entirely by the Windows Update servicing mechanism.

If Windows encounters an issue while processing these reboot operations, it automatically rolls back the update to restore the previous system state. Since this rollback occurs within the Microsoft Windows servicing process after Patch Manager Plus has already completed deployment, it is considered an operating system environmental issue rather than an Patch Manager Plus deployment failure.

Common environmental factors include:

• Corrupted Windows components.
• Windows servicing issues.
• Incompatible drivers.
• Pending operations.
• Insufficient system resources.
• File access or permission issues.
• Other Windows Update-related problems.