The issue of automatic restart after installing the KB5077181 update for Windows 11

Automatic restarts after installing cumulative updates like KB5077181 are controlled by Windows Update restart policies and registry settings. To troubleshoot why production devices auto‑restarted once and why this behavior is not reproduced in test, check and compare the following between both environments:

1. Verify Windows Update restart policies (Group Policy)

On affected clients and on test machines, review these policies under:

Computer Configuration > Administrative Templates > Windows Components > Windows Update

Key policies to compare:

• Turn off auto-restart for updates during active hours
• No auto-restart with logged on users for scheduled automatic updates installations
• Always automatically restart at the scheduled time (legacy, not applicable for Windows 11 but still worth confirming it isn’t misconfigured)
• Specify deadline before auto-restart for update installation (legacy, not applicable for Windows 11)

Differences here can explain why production devices restarted during use while test devices did not.

2. Check registry-based restart configuration

On clients, inspect the Windows Update AU policy keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

Compare these values between production and test:

• AUOptions
• NoAutoRebootWithLoggedOnUsers
• AlwaysAutoRebootAtScheduledTime
• AlwaysAutoRebootAtScheduledTimeMinutes
• ScheduledInstallTime

From the documented behavior:

• NoAutoRebootWithLoggedOnUsers = 0 allows automatic restart even when users are signed in.
• NoAutoRebootWithLoggedOnUsers = 1 prevents restart while a user is signed in.
• AUOptions = 4 is required to configure scheduled install/restart behavior.

If production devices had NoAutoRebootWithLoggedOnUsers set to 0 (or not set at all) and test devices had it set to 1, that would directly explain the difference.

3. Confirm WSUS/approval timing and install schedule

Because KB5077181 is a cumulative update, once it is approved and downloaded, restart behavior is governed by the client’s configured schedule and policies, not by WSUS itself. Check:

• Whether production clients had a scheduled install time that coincided with active usage.
• Whether test clients had different install windows or were restarted manually before reaching any forced restart deadline.

4. Align restart behavior going forward

If the goal is to prevent unexpected restarts during usage:

• Configure Configure Automatic Updates to option 4 – Auto download and schedule the install and set an appropriate install time.
• Ensure NoAutoRebootWithLoggedOnUsers is set to 1 (via Group Policy rather than direct registry editing) so devices do not restart while users are signed in.
• Optionally configure active hours so that restarts are avoided during typical working time.

5. Note on direct registry editing

Directly editing the registry is not recommended; use Group Policy or MDM to enforce consistent restart behavior across all Windows 11 devices.

References:

• Manage device restarts after updates
• Group policy settings for restart
• Registry keys used to manage restart
• WSUS client computers restart automatically without any notification when updates are installed on the client computers