Force install update with deadline without reboot

Question

Hi,

I want to force install update and configure deadline without auto reboot ,is this configuration functional ?

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

SetComplianceDeadline = 1

ConfigureDeadlineForQualityUpdates = 1

ConfigureDeadlineForFeatureUpdates = 1

ConfigureDeadlineGracePeriod = 0

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

NoAutoRebootWithLoggedOnUsers = 1

AlwaysAutoRebootAtScheduledTime = 0

Best regards

Answer 1

Hi Aymen Hanini,

Thank you for reaching out.

This configuration is not expected to reliably provide “force install by deadline, but never auto-reboot” on Windows 11 because it combines modern deadline policies with legacy restart settings that do not fully align in current Windows update behavior.

For Windows 11, the supported approach is to use the deadline policies themselves for update enforcement, such as:

• ConfigureDeadlineForQualityUpdates
• ConfigureDeadlineForFeatureUpdates
• ConfigureDeadlineGracePeriod
• ConfigureDeadlineNoAutoRebootForQualityUpdates / FeatureUpdates

A key limitation is that ConfigureDeadlineNoAutoReboot can help delay automatic restart before the effective deadline, but once the deadline is reached, Windows can still enforce the restart to complete the update.

If your goal is to reduce unexpected restarts before the deadline, use only the supported deadline-based policies and avoid mixing them with older AU restart settings.

You can consider trying this approach:

1. Configure the required quality/feature update deadline.
2. Set an appropriate grace period to give users time after installation completes.
3. Enable the related no-auto-reboot-before-deadline option if you want to minimize non-user-aware restarts until the deadline is reached.
4. Do not rely on AlwaysAutoRebootAtScheduledTime for Windows 11, as Microsoft documents it as a legacy policy not applicable to Windows 11.

If the requirement is “install by deadline but never auto-reboot afterward”, that is not a supported outcome under the current compliance deadline model.

I hope this helps clarify the behavior. Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

The configuration as written mixes legacy restart behavior with the newer compliance‑deadline model and won’t reliably give “forced install with deadline but never auto‑reboot” on current Windows versions, especially Windows 11.

Key points from the documented behavior:

1. Compliance deadline policies drive install and restart
   For Windows 10/11 with deadlines, the recommended path is the newer deadline policies (GPO or CSP), not the legacy AU/NoAutoRebootWithLoggedOnUsers/AlwaysAutoRebootAtScheduledTime combination. When using Specify deadlines for automatic updates and restarts (or the equivalent CSPs like ConfigureDeadlineForQualityUpdates, ConfigureDeadlineForFeatureUpdates, and ConfigureDeadlineGracePeriod):
   • Once the deadline + grace period are passed, updates are applied automatically and a restart occurs regardless of active hours.
   • To let Windows choose the least disruptive restart time, ConfigureDeadlineNoAutoReboot must be Disabled; this still allows automatic restart after the effective deadline.
2. Legacy restart policies can be overridden
   The legacy “Engaged restart” policy explicitly notes that enabling any of the following overrides it:
   • No auto‑restart with logged‑on users for scheduled automatic updates installations (NoAutoRebootWithLoggedOnUsers)
   • Always automatically restart at scheduled time (AlwaysAutoRebootAtScheduledTime)
   • Specify deadline before auto‑restart for update installation (the legacy deadline GPO)
   Additionally, the documentation states that AlwaysAutoRebootAtScheduledTime and related settings are legacy and not applicable for Windows 11; they may be removed in a future release.
3. Registry combination for “delay restart if user is signed in”
   The documented combination for delaying restart when a user is signed in is:
   • AUOptions = 4 (auto download and schedule install)
   • NoAutoRebootWithLoggedOnUsers = 1
   However, this is for the legacy Configure Automatic Updates model. When the newer deadline policy is used, the documentation for Windows 10/11 compliance deadlines states that once the deadline and grace period are passed, a restart occurs regardless of active hours. That means the deadline mechanism is designed to eventually force a reboot to complete installation.
4. Effect on your exact configuration
   Your intent is:
   • Force installation by deadline
   • Do not auto‑reboot
   But the documented behavior of compliance deadlines is:
   • After deadline + grace period, automatic restart happens regardless of active hours.
   The registry values you listed (SetComplianceDeadline, ConfigureDeadlineForQualityUpdates, ConfigureDeadlineForFeatureUpdates, ConfigureDeadlineGracePeriod) are not the documented names for the supported CSP or GPO settings in the references, and the supported deadline model is explicitly tied to forced restart after the deadline. The legacy NoAutoRebootWithLoggedOnUsers = 1 and AlwaysAutoRebootAtScheduledTime = 0 cannot reliably override the compliance‑deadline restart behavior on Windows 11.

Conclusion:
The documented compliance‑deadline mechanism is not designed to support “force install by deadline but never auto‑reboot.” After the deadline and grace period, Windows will enforce a restart to complete the update. The registry combination shown is therefore not a supported or reliable way to achieve the desired behavior on Windows 11.

---

References:

• Enforcing compliance deadlines for updates
• Policies for update compliance, activity, and user experience
• Manage device restarts after updates
• Registry keys used to manage restart
• Policy CSP - Update
• Walkthrough: Use CSPs and MDMs to configure Windows Update client policies
• Configure Windows Update for business rings, delivery optimization, and compliance