Patch Continues to try to Install despite successful install

Last Modified

Fri Jan 05 14:30 GMT 2023

Description

  • Patch isn't installing, but investigation of logs shows successful installation message.
  • Since there are generally no services running in Windows (including the N-able N-central agent as well as the Windows Event Log Service) during a reboot when the patches are being finalized there will not be any logging of what happens (without other methods). We can infer from the logs below followed by the sudden missing status of the patch that the installation succeeded but was rolled back during the reboot.
  • If multiple patches were installed at the same time or without reboting, Windows will generally roll all of the patches back if even one of them has an issue.

Environment

  • N-able N-central
  • Patch Management

Solution

  1. Identify which patch is causing the issue.
  2. Look for successful installation message for the agent logs via PatchInstall.log:

    [175] 2018-12-18 00:59:57,567 <<*>> (25) Install 2018-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4103725) OperationResultCode: Succeeded

    [175] 2018-12-18 00:59:57,567 <<*>> 2018-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4103725) is Installed. Reboot:Required to complete the install.

  3. Check that Windows also sees the successful installation. WindowsUpdate.log:

    2018-12-18 04:07:14:787 956 cc0 Report REPORT EVENT: {9B3F230C-555E-41DE-B06A-AAF80160A833} 2018-12-18 04:06:35:746-0500 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 {F2EA9A36-A6DF-472C-BED2-D7F0A155AFF2} 200 0 <<PROCESS>>: agent.exe Success Content Install Installation Successful: Windows successfully installed the following update: 2018-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4103725)

  4. If the patch is once again detected as Missing, even after a reboot is applied as above:
    1. Optionally:Isolate the problem patch by installing patches one at a time, such as using Patch on Demand. The problem patch would show as missing after the POD and reboot, since patch detection occurs within minutes of reboot.

  5. Manually install the problem patch, superseding patch and reboot.
  6. If the problem persists after manually installing the patch then assistance from Microsoft Support will be required. Another option to troubleshoot further is using this Public KB (ARTICLE NUMBER: 000042302) as a guide: https://documentation.n-able.com/N-central/troubleshooting/Content/kb/Troubleshooting-Microsoft-Windows-Update-issues-and-N-able-N-central-Patch-Management.htm