From bdcc1e9e299b787b93f66b7403ddd2b05dcaf2c6 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Sun, 29 Sep 2024 14:27:38 -0700 Subject: [PATCH] edits --- .../includes/wufb-restart-notifications-compliance-deadlines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/includes/wufb-restart-notifications-compliance-deadlines.md b/windows/deployment/update/includes/wufb-restart-notifications-compliance-deadlines.md index b0757fa36a..96a9307792 100644 --- a/windows/deployment/update/includes/wufb-restart-notifications-compliance-deadlines.md +++ b/windows/deployment/update/includes/wufb-restart-notifications-compliance-deadlines.md @@ -10,7 +10,7 @@ ms.localizationpriority: medium --- -These deadline policies also offer an option to opt out of automatic restarts until a deadline is reached by presenting an "engaged restart experience" until the deadline has expired. At that point, the device automatically schedules a restart regardless of active hours. +These deadline policies also offer an option to opt out of automatic restarts until a deadline is reached by presenting an "engaged restart experience" until the deadline passes. At that point, the device automatically schedules a restart regardless of active hours. These notifications are what the user sees depending on the settings you choose, and what operating system version their device is running. Generally, the user notifications become more noticeable as the deadline approaches. The experience described is the default and assumes there's ample time for notifications before the [effective deadline](../wufb-compliancedeadlines.md) occurs. The description doesn't account for settings such as [Update/NoUpdateNotificationsDuringActiveHours](/windows/client-management/mdm/policy-csp-update#NoUpdateNotificationsDuringActiveHours) that would significantly change the experience.