For the Windows Update reboot notifications scenario, keep the message short and action-oriented. Users should immediately understand whether they can postpone, whether a restart deadline exists, and which business application might be affected if they ignore the prompt.
Also check the policy assignment after deployment. If the same device receives multiple update rings or conflicting restart settings, the notification can look correct while the underlying restart behavior is still confusing for users and support teams.
This guide is about Windows Update reboot notifications in Intune and how to make restart behavior predictable for users. The important part is not only enabling a toast, but also choosing timing, wording, and assignment groups that match your patching process.
Before rolling this out broadly, test the notification on a small pilot group and compare the user experience with your existing update rings. That gives you a clean baseline for support tickets, restart deadlines, and expected device behavior after monthly patch deployment.
Windows Update reboots are one of those topics where the default behaviour annoys exactly the people you want least to annoy: knowledge workers in the middle of a presentation, factory operators on a kiosk, and your CEO on a Friday afternoon. Out of the box, Windows shows generic reboot prompts that users either dismiss without reading or only see seconds before the machine restarts.
The good news is that Microsoft Intune exposes a complete set of CSP-backed settings to tame these notifications: when they appear, how often they nag, when they auto-restart, and how aggressively they enforce. This post collects the small handful of policies I deploy in every tenant for predictable reboot behaviour, with the gotchas that don’t make it into the docs.
In one of my blog posts (Delay Windows Update pending reboot with toast notification) I have already described how to give users more flexibility in deciding when to reboot their device while still reminding them regularly. In this blog I want to explain how to configure the system notification of Windows Update for business. The reason for this blog is a question in the Microsoft Tech Community.
Table of contents
Why Windows Update reboot notifications matter
A restart at the wrong moment is more than a minor annoyance. It can cost unsaved work, interrupt a live meeting, or take a shared production device offline. Well-configured Windows Update reboot notifications turn an abrupt, surprising restart into a predictable event that users can plan around. When the prompt is clear and the timing is reasonable, people are far more likely to install updates voluntarily, which keeps your patch compliance high without forcing aggressive deadlines.
From a support perspective, predictable behavior also reduces noise. Most “my computer rebooted by itself” tickets disappear once the notification clearly states when the restart will happen and how long it can be postponed. That is why I treat the notification settings as a core part of every Windows Update for Business rollout rather than an afterthought.
Creation of the configuration profile
- Open the Intune admin center
- Navigate to Devices -> Windows -> Configuration profiles
- Click + Create profile
- Select Windows 10 and later platform as Platform
- Select Settings catalog (preview) as Profile type
- Click Create
- Enter a Name and click Next
- Click + Add settings
- Enter Windows Update in the search box and click Search
- Select Windows Update for Business
- Select the following settings:
- Auto Restart Notification Schedule
- Auto Restart Required Notification Dismissal
- Set Auto Restart Notification Disable
Note: The documentation for the CSP you can find the Microsoft documentation.
- Configure the settings as needed
- Click Next
- Assign the policy to a group
- Click Next
- Click Next
- Click Create
Key settings that control Windows Update reboot notifications
The three settings above do most of the work, so it helps to know exactly what each one changes. Auto Restart Notification Schedule defines how many minutes before an automatic restart the user is warned, which is the single most important knob for avoiding surprise reboots. Auto Restart Required Notification Dismissal controls whether the reminder dismisses automatically after a set time or stays on screen until the user acts on it. Set Auto Restart Notification Disable is the override you reach for when a device class, such as a kiosk or a meeting-room PC, should never display the prompt at all.
My recommended starting point is a 60-minute warning schedule with a non-auto-dismissing reminder for standard knowledge workers. That combination gives people a clear, persistent heads-up without being so aggressive that they tune it out. For details on the underlying CSP values and accepted ranges, the Microsoft Learn Update policy reference is the authoritative source.
Common mistakes to avoid
- Stacking conflicting update rings on the same device, so the notification timing no longer matches the actual restart deadline.
- Disabling notifications globally instead of scoping the disable to the specific kiosk or shared-device group that truly needs it.
- Setting an extremely short warning window, which recreates the exact surprise-restart problem you were trying to solve.
- Skipping a pilot ring, so the first time you learn the wording is confusing is from a flood of support tickets.
Avoid these and the rest is straightforward. Configure Windows Update reboot notifications once per ring, validate them on a pilot group, and the behavior stays consistent as your fleet grows.
Conclusion
There are many different settings to configure Windows Update for Business. In this blog I have shown you how to configure the Windows Update reboot notifications for restarts so the experience is predictable for your users. Combine these policies with sensible update rings and a short pilot, and reboots stop being a source of surprise and support tickets.
Stay healthy, Cheers
Jannik