Let’s discuss how to Configure Engaged Restart Snooze options for End Users during Monthly Patch Cycle using Intune. This Windows Update for Business setting controls how long a user can postpone the Engaged restart reminder after a quality update is installed, and a reboot is required.
The purpose of this policy configuration in Intune is to strike a balance between user productivity and update compliance. A shorter snooze period for example, 1 day ensures users see reminders more often, which accelerates restarts and helps finalize patch installation quickly.
On the other hand, allowing 2–3 days provides more flexibility for frontline staff who cannot afford frequent interruptions. Intune gives IT admins the ability to define this behavior consistently across all managed Windows devices, without requiring manual configuration on endpoints.
This policy applies at the device and user scope and is supported across multiple Windows editions, including Pro, Enterprise, Education, IoT Enterprise, and IoT Enterprise LTSC. It is available starting from Windows 10, version 1703 (build 10.0.15063) and later.
Table of Contents
How to Configure Engaged Restart Snooze options for End Users during Monthly Patch Cycle using Intune
Intune helps administrators to monitor which devices remain in a “restart pending” state. Configuring this policy helps you to correctly ensure updates are finalized within the expected timeframe while still respecting user experience.
- First Log in to the Microsoft Intune Admin Center with administrator credentials.
- Go to Devices > Windows > Manage Devices> Configuration.
- Click +Create and then select +New Policy to begin configuring the required settings.
| Steps | Details |
|---|---|
| Platform | Windows 10 and later |
| Profile Type | Settings Catalog |
- Easy way to Block Pause Updates Ability in Windows Update for Business via Intune
- Best way Intune to Stop Sending New Policy Updates to Windows Devices Pause Config Refresh Feature
- Simplifying Windows Update Management Integration of Intune and Autopatch
In the Basics settings, you provide a Name and Description for the policy. You can set the name as Engaged Restart Snooze Schedule and add a description that How to configure the snooze period for restart reminders after Windows Quality Updates in Intune. This helps clearly identify the purpose of the policy when managing it in the Intune portal.
When you enable this policy in Intune, you can control how long Windows waits before moving from automatic restarts (which can happen outside active hours) to the Engaged restart stage, where the user is asked to pick a restart time.
- You can set this period anywhere between 0 and 30 days from the moment the restart becomes pending.
- This setting is managed in Intune as part of the Engaged Restart Snooze Schedule.
- Here in the configuration window, select the +Add settings hyperlink
In the settings picker window of Intune, you can search for the keyword Windows Update for Business, which shows 77 available settings. From these, you can select the Engaged Restart Snooze Schedule policy. This policy is useful for IT admins because it gives them control over how long users can delay restart reminders after Quality Updates.
- By setting this period, admins can make sure devices stay secure and updated, while still giving users some flexibility to restart at a convenient time.
With this policy, IT admins can decide how many days a user is allowed to snooze the Engaged restart reminder after a Quality Update. The snooze period can be set between 1 and 3 days. This helps admins ensure that users do not keep delaying restarts for too long, which means updates get installed and devices stay secure.
- At the same time, it still gives users a little flexibility to choose a convenient time for the restart, reducing disruption to their work.
- The default value is 3 days
Here I set the value to 2, which means users can snooze the Engaged restart reminder for up to 2 days. After this period, the reminder will appear again until the device is restarted. This setting strikes a balance by giving users some flexibility while still ensuring that updates are completed within a reasonable time.
The property for this policy is set in an integer (int) format and supports actions like Add, Delete, Get, and Replace. The allowed values are in the range of 1 to 3, with the default value set to 3. This means if no custom value is chosen, Windows will automatically use 3 as the default.
The advantage of using assignments is that it gives IT admins targeting and flexibility. Instead of applying a policy to everyone, you can choose specific Azure AD groups, such as only frontline workers, specific departments, or test devices.
The advantage of Review + create is that it helps catch mistakes, such as assigning to the wrong group or missing a setting. Once you confirm everything looks correct, clicking Create will publish the policy to Intune and apply it to the selected users or devices.
If the engaged restart snooze schedule policy has no deadline set or is set to 0, the computer will not restart automatically. In this case, the user must manually choose a time to restart. However, if the policy is disabled or left unconfigured, the computer will restart automatically based on the default schedule.
- A notification appears confirming the policy.
- The message shows that the Engaged Restart Snooze Schedule policy is created.
- Status indicates successful creation.
Windows CSP Details – Engaged Restart Snooze
The Engaged Restart Snooze Schedule policy applies at the device level and is not available for users. This policy applies to Windows 10, version 1703 (build 10.0.15063) and later. The configuration path for this policy is:
./Device/Vendor/MSFT/Policy/Config/Update/EngagedRestartSnoozeSchedule.
Check-in Status for Devices and Users
The Engaged Restart Snooze Schedule device configuration profile shows the check-in status for devices and users. It was successful on 2 devices, with zero errors reported. There are no conflicts, no devices marked as not applicable, and none currently in progress.
MDM Policy Update – Engaged Restart Snooze Schedule
The MDM PolicyManager has set the policy EngagedRestartSnoozeSchedule under the Update area. The request came from the enrollment ID EB427D85-802F-46D9-A3E2-D5B414587F63 for the current user (Device). The integer value applied is 0x2, with an enrollment type of 0x6 and scope 0x0.
MDM PolicyManager: Set policy int, Policy: (EngagedRestartSnoozeSchedule), Area: (Update),
EnrollmentID requesting merqe: (EB427D85-802F-46D9-A3E2-D5B414587F63), Current User:
(Device), Int: (0x2), Enrollment Type: (0x6), Scope: (0x0).
- Event Viewer > Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin
- Search for Event ID 813 or 814 for configuration profile status updates.
How to Remove the Engaged Restart Snooze Schedue using Intune
Let’s discuss how to remove the engaged restart snooze schedule using Intune. Click the Remove button from the assignment window. Read more – How to Remove Assigned Group from Energy Saver Battery Threshold Policy in Intune Settings Catalog.
How to Delete the Engaged Restart Snooze Schedule Policy
You can easily delete the Engaged Restart Snooze Schedule policy from the Intune portal. Simply go to the list of device configuration profiles, select the policy, and choose the Delete option. Once deleted, the policy will no longer apply to devices in your environment.
Read more – How to Delete Allow Clipboard History Policy in Intune Step by Step Guide.
Need Further Assistance or Have Technical Questions?
Join the LinkedIn Page and Telegram group to get the latest step-by-step guides and news updates. Join our Meetup Page to participate in User group meetings. Also, join the WhatsApp Community to get the latest news on Microsoft Technologies. We are there on Reddit as well.
Author
Anoop C Nair has been Microsoft MVP for 10 consecutive years from 2015 onwards. He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.