Applies to: Windows 10
-->
- Windows Is In Notification Period 1
- Windows In Notification Mode
- Windows Is In Notification Period 1
- Windows Is In Notification Periodic Table
- Event 4105 Windows Is In Notification Period
Deploying feature or quality updates for many organizations is only part of the equation for managing their device ecosystem. The ability to enforce update compliance is the next important part. Windows Update for Business provides controls to manage deadlines for when devices should migrate to newer versions.
Whether the notification should be discarded if it cannot be displayed immediately. A timeout for the notification. This setting is ignored in Windows Vista and later systems in favor of a system-wide accessibility timeout setting. Whether the notification should respect quiet time, set through the NIIFRESPECTQUIETTIME flag. Mar 16, 2016 Windows 10 improves on Windows’ notification system by adding the Action Center, a slide out sidebar that shows recent notifications and handy system actions you can perform. It’s a convenient feature and one you can customize pretty well. For most people, the few seconds a pop-up notification stays on screen is fine. ^^ Now your problem has been solved or not? Which Windows version are you currently using in that machine? Neine on May 22, 2016 at 1:16 pm. I already have a windows 7 genuine but i have a problem i want to fix it, this is the reasons make me to reload this version of windows, Devesh on June 1, 2016 at 7:07 am. First of all,open Start. Jan 11, 2019 Windows 7 Professional and Windows 7 Enterprise editions were affected by the issue (and probably any other edition using Key Management Service activation). Microsoft notes that the issue was not caused by the release of security updates for Windows 7 in January 2019. And in those cases we were used to seeing a 5-10% voluntary user participation rate in the availability period leading up to the deadline. That availability period is about 7 days on average. Now, with our first Windows 10 build update we blew past 20% in the first two business days that the update was available.
The compliance options have changed for devices on Windows 10, version 1709 and above:
For Windows 10, version 1709 and above
With a current version of Windows 10, it's best to use the new policy introduced in June 2019 to Windows 10, version 1709 and above: Specify deadlines for automatic updates and restarts. In MDM, this policy is available as four separate settings:
- Update/ConfigureDeadlineForFeatureUpdates
- Update/ConfigureDeadlineForQualityUpdates
- Update/ConfigureDeadlineGracePeriod
- Update/ConfigureDeadlineNoAutoReboot
This policy starts the countdown for the update installation deadline from when the update is published, instead of starting with the 'restart pending' state as the older policies did.
The policy also includes a configurable grace period to allow, for example, users who have been away to have extra time before being forced to restart their devices.
Further, the policy includes the option to opt out of automatic restarts until the deadline is reached by presenting the 'engaged restart experience' until the deadline has actually expired. At this point the device will automatically schedule a restart regardless of active hours.
Policy setting overview
Policy | Description |
---|---|
(Windows 10, version 1709 and above) Specify deadlines for automatic updates and restarts | Similar to the older 'Specify deadline before auto-restart for update installation,' but starts the deadline countdown from when the update was published. Also introduces a configurable grace period and the option to opt out of automatic restarts until the deadline is reached. |
Suggested configurations
Policy | Location | Quality update deadline in days | Feature update deadline in days | Grace period in days |
---|---|---|---|---|
(Windows 10, version 1709 and above) Specify deadlines for automatic updates and restarts | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadlines for automatic updates and restarts | 7 | 7 | 2 |
When Specify deadlines for automatic updates and restarts is set (Windows 10, version 1709 and above):
-
While restart is pending, before the deadline occurs:
-
For the first few days, the user receives a toast notification
-
After this period, the user receives this dialog:
-
If the user scheduled a restart, or if an auto restart is scheduled, 15 minutes before the scheduled time the user is receives this notification that the restart is about to occur:
-
-
If the restart is still pending after the deadline passes:
-
Within 12 hours before the deadline passes, the user receives this notification that the deadline is approaching:
-
Once the deadline has passed, the user is forced to restart to keep their devices in compliance and receives this notification:
-
Prior to Windows 10, version 1709
Two compliance flows are available:
Deadline only
This flow only enforces the deadline where the device will attempt to silently restart outside of active hours before the deadline is reached. Once the deadline is reached the user is prompted with either a confirmation button or a restart now option.
End-user experience
Once the device is in the pending restart state, it will attempt to restart the device during non-active hours. This is known as the auto-restart period, and by default it does not require user interaction to restart the device.
Note
Deadlines are enforced from pending restart state (for example, when the device has completed the installation and download from Windows Update).
Policy overview
Policy | Description |
---|---|
Specify deadline before auto-restart for update installation | Governs the update experience once the device has entered pending restart state. It specifies a deadline, in days, to enforce compliance (such as imminent installation). |
Configure Auto-restart warning notification schedule for updates | Configures the reminder notification and the warning notification for a scheduled installation. The user can dismiss a reminder, but not the warning. |
Suggested configuration
Policy | Location | 3-day compliance | 5-day compliance | 7-day compliance |
---|---|---|---|---|
Specify deadline before auto-restart for update installation | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadline before auto-restart for update installation | State: Enabled Specify the number of days before pending restart will automatically be executed outside of active hours: 2 |
State: Enabled Specify the number of days before pending restart will automatically be executed outside of active hours: 3 |
State: Enabled Specify the number of days before pending restart will automatically be executed outside of active hours: 4 |
Controlling notification experience for deadline
Policy | Location | Suggested Configuration |
---|---|---|
Configure Auto-restart warning notification schedule for updates | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure auto-restart warning notifications schedule for updates | State: Enabled Reminder (hours): 2 Warning (minutes): 60 |
Notification experience for deadline
Notification users get for a quality update deadline:
Notification users get for a feature update deadline:
Deadline with user engagement
This flow provides the end user with prompts to select a time to restart the device before the deadline is reached. If the device is unable to restart at the time specified by the user or the time selected is outside the deadline, the device will restart the next time it is active.
End-user experience
Before the deadline the device will be in two states: auto-restart period and engaged-restart period. During the auto-restart period the device will silently try to restart outside of active hours. If the device can't find an idle moment to restart, then the device will go into engaged-restart. The end user, at this point, can select a time that they would like the device to try to restart. Both phases happen before the deadline; once that deadline has passed then the device will restart at the next available time.
Policy overview
Policy | Description |
---|---|
Specify engaged restart transition and notification schedule for updates | Governs how the user will be impacted by the pending restart. Transition days, first starts out in Auto-Restart where the device will find an idle moment to restart the device. After 2 days engaged restart will commence and the user will be able to choose a time |
Configure Auto-restart required notification for updates | Governs the notifications during the Auto-Restart period. During Active hours, the user will be notified that the device is trying to restart. They will have the option to confirm or dismiss the notification |
Suggested configuration
Policy | Location | 3-day compliance | 5-day compliance | 7-day compliance |
---|---|---|---|---|
Specify engaged restart transition and notification schedule for updates | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify Engaged restart transition and notification schedule for updates | State: Enabled Transition (Days): 2 Snooze (Days): 2 Deadline (Days): 3 |
State: Enabled Transition (Days): 2 Snooze (Days): 2 Deadline (Days): 4 |
State: Enabled Transition (Days): 2 Snooze (Days): 2 Deadline (Days): 5 |
Controlling notification experience for engaged deadline
Policy | Location | Suggested Configuration |
---|---|---|
Configure Auto-restart required notification for updates | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Auto-restart required notification for updates | State: Enabled Method: 2- User |
Notification experience for engaged deadlines
Notification users get for quality update engaged deadline:
Notification users get for a quality update deadline:
Notification users get for a feature update engaged deadline:
Notification users get for a feature update deadline:
-->
The notification area is a portion of the taskbar that provides a temporary source for notifications and status. It can also be used to display icons for system and program features that have no presence on the desktop, such as battery level, volume control, and network status. The notification area has been known historically as the system tray or status area.
This topic contains the following sections:
- Creating and Displaying a Notification
Windows Is In Notification Period 1
Notification and Notification Area Guidelines
See the Notifications and Notification Area sections of the Windows User Experience Interaction Guidelines for best practices in the use of notifications and the notification area. The goal is to provide user benefit through appropriate use of notifications, without being annoying or distracting.
The notification area is not for critical information that must be acted on immediately. It is also not intended for quick program or command access. As of Windows 7, much of that functionality is best accomplished through an application's taskbar button.
Windows 7 allows a user to suppress all notifications from an application if they choose, so thoughtful notification design and use will incline the user to allow your application to continue to display them. Notifications are an interruption; ensure that they are worth it.
Windows 7 introduces the concept of 'quiet time'. Quiet time is defined as the first hour after a new user logs into his or her account either for the first time or for the first time after an operating system upgrade or clean installation. This time is set aside to allow the user to explore and familiarize themselves with the new environment without the distraction of notifications. During this time, most notifications should not be sent or shown. Exceptions include feedback that the user would expect to see in response to a user action, such as when he or she plugs in a USB device or prints a document. API specifics of regarding quiet time are discussed later in this topic.
Creating and Displaying a Notification
Windows In Notification Mode
The remaining sections in this topic outline the basic procedure to follow to display a notification from your application to the user.
Add a Notification Icon
To display a notification, you must have an icon in the notification area. In certain cases, such as Microsoft Communicator or battery level, that icon will already be present. In many other cases, however, you will add an icon to the notification area only as long as is needed to show the notification. In either case, this is accomplished using the Shell_NotifyIcon function. Shell_NotifyIcon allows you to add, modify, or delete an icon in the notification area.
When an icon is added to the notification area on Windows 7, it is added to the overflow section of the notification area by default. This area contains notification area icons that are active, but not visible in the notification area. Only the user can promote an icon from the overflow to the notification area, although in certain circumstances the system can temporarily promote an icon into the notification area as a short preview (under one minute).
Note
The user should have the final say on which icons they want to see in their notification area. Before installing a non-transient icon in the notification area, the user should be asked for permission. They should also be given the option (normally though its shortcut menu) to remove the icon from the notification area.
The NOTIFYICONDATA structure sent in the call to Shell_NotifyIcon contains information that specifies both the notification area icon and the notification itself. The following are those items specific to the notification area icon itself that can be set through NOTIFYICONDATA.
- The resource from which the icon is taken.
- A unique identifier for the icon.
- The style of the icon's tooltip.
- The icon's state (hidden, shared, or both) in the notification area.
- The handle of an application window associated with the icon.
- A callback message identifier that allows the icon to communicate events that occur within the icon's bounding rectangle and balloon notification with the associated application window. The icon's bounding rectangle can be retrieved through Shell_NotifyIconGetRect.
Each icon in the notification area can be identified in two ways:
- The GUID with which the icon is declared in the registry. This is the preferred method on Windows 7 and later.
- The handle of a window associated with the notification area icon, plus an application-defined icon identifier. This method is used on Windows Vista and earlier.
Icons in the notification area can have a tooltip. The tooltip can be either a standard tooltip (preferred) or an application-drawn, pop-up UI. While a tooltip is not required, it is recommended.
Notification area icons should be high-DPI aware. An application should provide both a 16x16 pixel icon and a 32x32 icon in its resource file, and then use LoadIconMetric to ensure that the correct icon is loaded and scaled appropriately.
The application responsible for the notification area icon should handle a mouse click for that icon. When a user right-clicks the icon, it should bring up a normal shortcut menu. However, the result of a single click with the left mouse button will vary with the function of the icon. It should display what the user would expect to see in the form best suited to that content—a popup window, a dialog box or the program window itself. For instance, it could show status text for a status icon, or a slider for the volume control.
The placement of a popup window or dialog box that results from the click should be placed near the coordinate of the click in the notification area. Use the CalculatePopupWindowPosition to determine its location.
The icon can be added to the notification area without displaying a notification by defining only the icon-specific members of NOTIFYICONDATA (discussed above) and calling Shell_NotifyIcon as shown here:
You can also add the icon to the notification area and display a notification all in one call to Shell_NotifyIcon. To do so, continue with the instructions in this topic.
Define the NOTIFYICONDATA Version
As Windows has progressed, the NOTIFYICONDATA structure has expanded to include more members to define more functionality. Constants are used to declare which version of NOTIFYICONDATA to use with your notification area icon, to allow for backward compatibility. Unless there is a compelling reason to do otherwise, it is strongly recommended that you use the NOTIFYICON_VERSION_4 version, introduced in Windows Vista. This version provides the full available functionality, including the preferred ability to identify the notification area icon though a registered GUID, a superior callback mechanism, and better accessibility.
Set the version through the following calls:
Note that this call to Shell_NotifyIcon does not display a notification.
Define the Notification Look and Contents
A notification is a special type of balloon tooltip control. It contains a title, body text, and an icon. Like a window, it has a Close button in its upper right corner. It also contains a Options button that opens the Notification Area Icons item in the Control Panel, which allows the user to show or hide the icon or show only notifications without an icon.
The NOTIFYICONDATA structure sent in the call to Shell_NotifyIcon contains information that specifies both the notification area icon and the notification balloon itself. The following are those items specific to the notification that can be set through NOTIFYICONDATA.
- An icon to display in the notification balloon, which is specified by the notification type. The size of the icon can be specified, as well as custom icons.
- A notification title. This title should be a maximum of 48 characters long in English (to accommodate localization). The title is the first line of the notification, and set apart through the use of font size, color, and weight.
- Text for use in the body of the notification. This text should be a maximum of 200 characters in English (to accommodate localization).
- Whether the notification should be discarded if it cannot be displayed immediately.
- A timeout for the notification. This setting is ignored in Windows Vista and later systems in favor of a system-wide accessibility timeout setting.
- Whether the notification should respect quiet time, set through the NIIF_RESPECT_QUIET_TIME flag.
Note
The IUserNotification and IUserNotification2 interfaces are Component Object Model (COM) wrappers for Shell_NotifyIcon. However, at this time, they do not provide the full NOTIFYICON_VERSION_4 functionality available through Shell_NotifyIcon directly, including the use of a GUID to identify the notification area icon.
Check the User Status
![Notification area windows 10 Notification area windows 10](https://i.ytimg.com/vi/HKKcYrudaDY/maxresdefault.jpg)
The system uses the SHQueryUserNotificationState function is used to check whether the user is in quiet time, away from the computer, or in an uninterruptable state such as Presentation mode. Whether the system displays your notification depends on this state.
Note
If your application is using a custom notification method that does not use Shell_NotifyIcon, IUserNotification, or IUserNotification2, it should always explicitly call SHQueryUserNotificationState to determine whether it should display notification UI at that time.
Notifications sent when the user is away are queued for display, but because you cannot know when the user will return or whether the notification will still be valid at that time, you might consider resending the notification later.
Notifications sent during quiet time are discarded unshown. Design guidelines ask that all notifications be ignorable. They should not require immediate user action. Therefore, no notification is so important that it should override quiet time.
Display the Notification
Once you have set the NOTIFYICONDATA version and defined the notification in a NOTIFYICONDATA structure, call Shell_NotifyIcon to display the icon.
-
If the notification area icon is not present, call Shell_NotifyIcon to add the icon. Do this for both transient and non-transient icons.
-
If the notification area icon is already present, call Shell_NotifyIcon to modify the icon.
The following code shows an example of setting NOTIFYICONDATA data and sending it through Shell_NotifyIcon. Note that this example identifies the notification icon through a GUID (preferred in Windows 7).
Removing an Icon
To remove an icon—for instance, when you have only added the icon temporarily to broadcast a notification—call Shell_NotifyIconas shown here. Only a minimal NOTIFYICONDATA structure that identifies the icon is needed in this call.
Windows Is In Notification Period 1
Note
When an application is uninstalled, its notification area icon can still appear to the user as an option in the Notification Area Icons page in the Control Panel for up to seven days. However, any changes made there will have no effect.
Windows Is In Notification Periodic Table
SDK Sample
See the NotificationIcon Sample sample in the Windows Software Development Kit (SDK) for a full example of the use of Shell_NotifyIcon.