TrueSight Server Automation (TSSA) : Warning from Windows Patch Analysis Job - Reboot is pending on this machine, analysis results may be incorrect

Version 9
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BladeLogic Server Automation Suite


    BladeLogic Application Server


    version neutral



    The following warning message is encountered when running a BMC Truesight Server Automation (TSSA) Patch Analysis Job against a Windows target server:

    serverX,Warning,03/10/2020 04:39:40,"Reboot is pending on this machine, analysis results may be in-correct."

    When this warning is received for a target server, the Patch Analysis results are likely to be incorrect.  
    Patches which are installed may be listed as Missing until the server is rebooted.  
    This, in turn, can lead to errors such as the following during the remediation phase when an attempt is made to install a patch which is already installed. 

    03/09/20 20:45:21.635 DEBUG    bldeploy - [2][windows10.0-2016-kb4537764-x64-1607.msu-MS20-02-W10-4537764-en-WINDOWS SERVER 2016 STANDARD-1607] Found ReturnCode token with value '2359302'

    See KA 000087137 for details on the Remediation side of this issue.



    Target Server is in the "Reboot Required" state




    For reliable results, reboot the impacted server/s and rerun the Windows Patch Analysis Job before proceeding with patch remediation.

    Additional Details:

    To confirm the Server is in the Reboot Required state, check the following registry keys on the Target Server:

    - Go to "run" and "regedit"
    - Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired
    - Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations


    If the value data is present in the Value name "PendingFileRenameOperations", it means that the server requires a reboot.


    User-added image

    The server state can also be validated by executing below reg queries in cmd

    Server that doesn't need a reboot for pending files:
    No output will be generated for the command

    C:\>reg query "\\<hostname>\hklm\System\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations ERROR: The system was unable to find the specified registry key or value.

    User-added image

    Server that does need a reboot for pending files:
    Some output will be shown for the command execution

    C:\>reg query "\\<hostname>\hklm\System\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager     PendingFileRenameOperations    REG_MULTI_SZ    \??\C:\WINDOWS\system32\SET2B5.tmp\0!\??\C:\WINDOWS\system32\schannel.dll\0\??\C:\WINDOWS\system32\SET2BA.tmp\0!\??\C:\WINDOWS\system32\shdocvw.dll\0\??\C:\WINDOWS\system32\SET2CA.tmp\0!\??\C:\WINDOWS\system32\kernel32.dll

    User-added image

    The Patch Readiness Zipkit contains a Component Template which can check for Pending Reboots in advance of running the Patch Analysis job.
    "Component Templates > Windows > Patch Analysis > Patch Ready (Windows)"
    Patch Ready




    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles