How to Configure Windows 10 Update Notifications with Group Policy
Use the Configure Automatic Updates policy in supported Windows 10 editions to notify before downloading updates instead of silently downloading them.
- Applies to Windows 10
- 4 min read
View article illustration

Use this guide to request a notification before applicable Windows updates download on an eligible Windows 10 PC. It is not a method for permanently stopping security updates or controlling every application's updater. First record the existing policy so you can restore it.
Before you begin
This local-editor workflow is for editions with Local Group Policy, such as Pro, Enterprise and Education. Home does not normally include gpedit.msc; do not install an unofficial “Group Policy enabler” to reproduce these steps. Use the supported Windows Update controls for your edition instead.
| Situation | What to do |
|---|---|
| Personal PC with the policy editor | Record the edition, build, current policy state and selected option before making one change. |
| Work or school device, or an existing organisation policy | Ask the administrator which policy controls update behaviour. Do not try to override it locally. |
| Updates already downloading or awaiting restart | Record their current state. This procedure is not a rollback of an update already in progress. |
| Goal is to avoid an inconvenient restart | Review restart scheduling and active hours separately. Download notification and restart timing are different decisions. |
Configure update notifications
- Press Win + R, enter gpedit.msc, and open the editor with the appropriate administrator rights.
- Go to Computer Configuration > Administrative Templates > Windows Components > Windows Update. Depending on the administrative templates, the policy can be inside Manage end user experience.
- Open Configure Automatic Updates. Record its original state and option.
- Choose Enabled, then 2 - Notify for download and auto install. Select Apply > OK.
Microsoft describes option 2 as notifying users when applicable updates are ready for download, after which they can use Windows Update to download and install them. Selecting Disabled is a different policy state; it is not the option used in this procedure.
Verify the change without assuming it controls everything
- Reopen that policy and check the selected state and option against your notes.
- Let normal policy processing occur, then review Settings > Update & Security > Windows Update. Record the status and any management message.
- When an applicable update is offered, observe the actual download notification and installation workflow. Record the update identifier and time if behaviour differs from your expectation.
No offered update means there is nothing yet to observe. A management banner does not identify which policy won, and a saved local setting does not prove it is the effective setting on a managed device.
For Group Policy investigation, an administrator can view the applied computer-policy summary in an elevated Command Prompt:
gpresult /scope computer /rThis displays resultant Group Policy summary information. It is not a complete report of mobile-device-management settings, nor proof of the selected download option. Keep computer, domain and user details private when sharing output. If access is denied or policy ownership is unclear, stop and ask the administrator.
Undo your local change
Return to Configure Automatic Updates and restore the exact previous state and option. If your record shows it was originally Not Configured, restore that state; do not assume that is correct for every PC. Apply the change and recheck after policy processing. On a managed device, the organisation's policy can still apply.
Do not disable Windows Update services, delete policy keys or stack additional tweaks because one observation was unexpected. Restore your single change first, then investigate the update state and effective management configuration.
Important security context
A notification-based workflow still needs someone to act on the notifications. Decide when you will review and install applicable updates, and check update history afterward. If this arrangement repeatedly leaves the PC unpatched, restore the previous automatic behaviour rather than relying on reminders you cannot maintain.
Documentation review: 6 October 2026. Checked against the linked Microsoft documentation. This is an editorial configuration and verification workflow, not a claim of a Windows 10 device test. No update policy or virtual-switch configuration was changed on the author’s computer for this review.


