Server rebooted unknowingly

Apurva Pathak 735 Reputation points
2023-09-20T15:45:15.37+00:00

Hi folks,

One of my Windows Server 2019 got automatically rebooted with below pasted message in Event ID 1074. On same date a KB was installed on my server, so it seems that this reboot is triggered by that update installation.

However, we have configured GPOs to stop servers from being rebooted automatically (pasting a snip below).

Could you please help me understand, how this reboot could have been triggered, and where can I get relevant information on this.

Event details:

The process C:\Windows\servicing\TrustedInstaller.exe has initiated the restart of computer on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Upgrade (Planned)
Reason Code: 0x80020003
Shutdown Type: restart
Comment:

GPO applied:

User's image

Any help would be appreciated, thanks in advance!

Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} vote

2 answers

Sort by: Most helpful
  1. Anonymous
    2023-09-21T13:33:13.88+00:00

    Some updates deemed critical may not always honor those settings.

    --please don't forget to close up the thread here by marking answer if the reply is helpful--

    0 comments No comments

  2. Limitless Technology 44,751 Reputation points
    2023-09-21T13:50:43.0633333+00:00

    Hello Apurva Pathak,

    You are right, the code "0x80020003" refers to a reboot triggered by an installation, most likely a KB update. Bear in mind that the GPO setting you mentioned applies only when a User Account is logged in the system. System or Service accounts will not apply and updates will carry on.

    You can verify this by checking the update history of the server or running Get-HotFix cmdlet to view the installed updates and which one could have caused the reboot.

    Additionally, I would recommend:

    • Check Event Logs (Application and System) related to time of the reboot, as this can provide you more information about conditions met in the system.
    • Check if the GPO is applied correctly in the system. You can use GPRESULT /H to generate a HTML output of the policies and their status.
    • Verify if the update was pushed though a Deployment tool, such as SCCM, in which the administrator can request a forceful reboot.

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.