|
| 1 | +--- |
| 2 | +title: Windows Unexpectedly Installs Updates When Automatic Updates Are Disabled by Group Policy |
| 3 | +description: Discusses a problem that Windows unexpectedly installs updates when automatic updates are disabled by Group Policy. |
| 4 | +audience: itpro |
| 5 | +manager: dcscontentpm |
| 6 | +ms.date: 04/03/2025 |
| 7 | +ms.reviewer: 5x5dnd, shan |
| 8 | +ms.topic: troubleshooting |
| 9 | +ms.custom: |
| 10 | +- sap:windows servicing,updates and features on demand\windows update configuration,settings and management |
| 11 | +- pcy:WinComm Devices Deploy |
| 12 | +--- |
| 13 | +# Windows unexpectedly installs updates when automatic updates are disabled by Group Policy |
| 14 | + |
| 15 | +Windows unexpectedly installs updates on Windows Server 2016 and Windows Server 2019 automatically even though the **Configure Automatic Updates** Group Policy is set to one of the following options: |
| 16 | + |
| 17 | +- Option 2 - **Notify before downloading and installing any updates** |
| 18 | +- Option 3 - **Download the updates automatically and notify when they are ready to be installed** |
| 19 | +- Option 5 - **Allow local administrators to select the configuration mode that Automatic Updates should notify and install updates** (this option hasn't been carried over to any Windows 10 versions) |
| 20 | +- Option 7 - **Notify for install and notify for restart** (Windows Server only) |
| 21 | + |
| 22 | +## Cause |
| 23 | + |
| 24 | +This issue occurs when an administrator runs the command `GPUPDATE / FORCE`. This command resets all policy settings and reapplies them. During this interval, the automatic update settings are reverted to defaults, and updates might be installed. This issue occurs only on Windows Server 2016 and Windows Server 2019. |
| 25 | + |
| 26 | +## Resolution |
| 27 | + |
| 28 | +To avoid this issue, don't run `GPUPDATE /FORCE` on Windows Server 2016 and 2019 unless you're prepared for any queued updates to be installed. This issue is rare, but it can occur. |
| 29 | + |
| 30 | +## Workarounds for Windows Server 2016 and Windows Server 2019 |
| 31 | + |
| 32 | +For users on Windows Server 2016 and Windows Server 2019, implementing one of the following workarounds can help reduce the frequency of the issue: |
| 33 | + |
| 34 | +### Enable the "Configure registry policy processing" policy |
| 35 | + |
| 36 | +1. Navigate to **Computer Configuration** > **Administrative Templates** > **System** > **Group Policy** > **Configure registry policy processing** and set it to **Enabled**. |
| 37 | +2. Clear **Do not apply during periodic background processing**. |
| 38 | +3. Select **Process even if the Group policy objects have not changed**. |
| 39 | + |
| 40 | +### Enable the "Configure registry policy processing" policy by using the registry |
| 41 | + |
| 42 | +Set the following registry keys: |
| 43 | + |
| 44 | +`HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}` |
| 45 | +`NoBackgroundPolicy`=dword:00000000 |
| 46 | +`NoGPOListChanges`=dword:00000001 |
| 47 | + |
| 48 | +You can also run the following commands to modify the registry: |
| 49 | + |
| 50 | +```console |
| 51 | +reg add "HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}" /v NoBackgroundPolicy /t REG\_DWORD /d 00000000 /f |
| 52 | +reg add "HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}" /v NoGPOListChanges /t REG\_DWORD /d 00000001 /f |
| 53 | +``` |
| 54 | + |
| 55 | +For more information, see [Configure registry policy processing (admx.help)](https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.GroupPolicy::CSE_Registry). |
| 56 | + |
| 57 | +> [!NOTE] |
| 58 | +> These workarounds reduce the frequency of the problem but don't always prevent it from occurring. |
| 59 | +
|
| 60 | +## Reference |
| 61 | + |
| 62 | +For more information, open [Windows security baseline](/azure/governance/policy/samples/guest-configuration-baseline-windows) and see the "Ensure 'Configure registry policy processing: Process even if the Group Policy objects have not changed' is set to 'Enabled: TRUE'" row. |
0 commit comments