Reverting Changes After Patch Failure
Scenario
A windows10.0- filename prefix alone does not mean that a package is unsuitable for Windows Server 2016. Windows 10 version 1607 and Windows Server 2016 share the RS1 servicing family, as shown in Microsoft's Windows version and update table. Verify the KB's supported products, architecture and target OS build before deployment. If installation rolls back, follow Windows servicing troubleshooting and review the installation logs.
Compare the package with the vendor KB or applicability information for the target OS build, edition and architecture. The package filename alone is not a supported-platform check. If the update rolls back after reboot, retain the agent installation result and Windows servicing logs for the same attempt.
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. The same condition can appear in the execution remarks as Patch installed successfully, but rolled back on reboot. 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 a 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
Resolution
If the update continues to roll back, record the Windows build, KB or Patch ID, full error and reboot result. Follow Windows Update error troubleshooting to select the relevant servicing checks. A rollback remark alone does not confirm component-store corruption or guarantee that a repair patch will resolve the issue.
- Deploy the Component Store Cleanup patch (Patch ID: 105979) from the Supported Patches view.
- After the cleanup patch is installed successfully, reboot the system and redeploy the failed patch.
- Exclude the agent folder from antivirus:
C:\Program Files (x86)\ManageEngine\UEMS_Agent. - If Windows servicing or component-store corruption persists, follow the Windows component repair procedure.
- Restart the endpoint when required by that procedure and retry the failed update.
If the rollback continues after performing these steps, upload the Patch Manager Plus agent logs for further analysis, along with the Setup Event Viewer logs located at:
Event Viewer → Windows Logs → Setup