Windows 11 does not reboot at scheduled installation time

Bischof Andreas IT 5 Reputation points

Dear all,

i have a strange issue that showed up recently on a couple of our Windows 11 v22H2 clients in our Domain. Our Clients are configured to fetch their updates from our internal WSUS server and some of them are supposed to download and install updates on sundays at lunchtime and automatically reboot afterwards.

We´ve configured these GPOs to achieve that behavior:

  • Configure Automatic updates = 4 -Auto download and schedule the install install during automatic maintenance = disabled Schedule install day = sunday Scheduled install time = 12:00 Every week = enabled Install updates for other Microsoft products = disabled
  • Always automatically restart at the scheduled time = enabled restart timer = 15 minutes
  • Specify intranet Microsoft Update service location = pointing to our WSUS server
  • Do not include drivers with Windows updates

Weird thing is that this GPO has done exactly what we wanted when we started introducing Windows 11 in late 2023.

But now, such clients only search and install any pending updates at Sundays around 12:00 so obviously, "Configure Automatic updates" does what it´s intended to.

But afterwards, then they ignore the GPO to automatically reboot afterwards. The reboot is pending and is then done automatically around midnight but not after the updates have applied (just as if "Always automatically restart at the scheduled time" hasn´t been enabled).

Has anyone else been facing that behavior and found a solution for it? Or are we missing something?

Appreciate any help since we´re slowly running out of ideas why that happens and how to fix this.

Many thanks,


Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,061 questions
Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
955 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. glebgreenspan 1,125 Reputation points

    Hello Bischof

    It sounds like you have configured your Group Policy settings correctly, but there may be an issue with the way Windows 11 is handling the automatic reboot after updates are installed. Here are a few things you can try to troubleshoot and potentially resolve the issue:

    1.     Check for conflicting Group Policies: Make sure there are no conflicting Group Policies that may be overriding the setting to automatically restart after updates are installed. You can run a Group Policy Results report on one of the affected Windows 11 computers to see if any other policies are applying that could be causing this issue.

    2.     Check for Windows Update settings: Verify the Windows Update settings on the affected Windows 11 computers to ensure that there are no conflicting configurations that may prevent the automatic restart after updates. Double-check the "Active Hours" settings to make sure they are not conflicting with the scheduled restart time.

    3.     Check for pending restart notifications: Sometimes, Windows may display a notification that a restart is pending but does not automatically reboot. Users may need to manually initiate the restart after updates are installed. Make sure to check for any pending notifications on the affected computers.

    4.     Use Windows Update troubleshooter: Run the built-in Windows Update troubleshooter on the affected Windows 11 computers to see if it can identify and fix any issues related to update installation and automatic restart.

    5.     Check Event Viewer logs: Review the Event Viewer logs on the affected Windows 11 computers to see if there are any errors or warnings related to Windows Update or automatic restarts. This may provide more insights into what could be causing the issue.