Windows 10 lets you 'schedule' a reboot for later. I want to disable it.
Evidently Windows scheduled itself for a reboot last night when I wasn't looking and just closed everything I had been working on the night before.
I reboot on the regular; I don't need Windows to do that for me.
Can I disable it completely? I don't mind if it downloads everything, and then says "hey, you should reboot," but it should never reboot itself, ever.
I'm using the "Pro" edition of Windows 10.
Note: Unfortunately this appears to not work on Windows 10 Home, and I'm not sure of a workable solution for users of this edition.
I posted this as an answer on another question, but as that appears to be a duplicate of this question I'll provide it here too:
You can edit your local group policy settings to force Windows update to only download updates, but wait for your input to install (and therefore reboot.)
Open your start menu and type Group, then click Edit group policy
Expand either (depending on Windows 10 or 11 version):
Double click Configure Automatic Updates and enable the policy, and configure it as needed.
Head back to Windows Update and click Check for updates. Once it is done, click on the Advanced options
You should see your new settings being 'enforced.'
After applying this setting on a test VM, I left Windows Update open and noticed it started downloading.
When it finishes downloading, you get a toast notification that there are updates and you need to install them.
Note that you must click install now. Restarting or shutting down from the start menu does not appear to trigger the install process.
More info:
I'm not sure if editing Local Group Policy is an option in the Home edition of Windows 10, but the same result should be possible through the registry (I haven't tested this as I used the policy method myself). Including this in case non-pro users come looking for an answer too.
Press Win + R and type regedit then hit Enter
Navigate to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU
(you may need to create the keys manually if they don't exist)
Create a new DWORD value called AUOptions and enter a value of either 2 or 3.
2 = Notify before download
3 = Automatically download and notify of installation
Restart PC
Check for updates
Inspect Advanced Settings
Update following Anniversary Update (1607):
I've seen a lot a few comments lately from people saying this no longer works after the Anniversary Update.
I've been running some tests, detailed in the two blog posts here:
These tests have been running for nearly three weeks and I have yet to see any forced reboots.
In light of these results, it appears that this does still work.
Things to keep in mind:
You can try Windows 10 Reboot Blocker:
A simple Windows-Service that will update this "active hours" timeslot in the background.
It is free and works with the Anniversary update.
I have answered this as part of my attempt to fix another garbage setting in Windows 10 (the way it will wake your device up, and you in the process, to install updates you haven't approved.)
Please consult Step 2 of my guide here. It explains how to modify the "Reboot" task in the "UpdateOrchestrator" section of the Windows Scheduled Tasks list to disable it and stop Windows from interfering with it. With this task disabled, your machine will never reboot unless you instruct it to.
Cheers - Seagull
The best solution to this annoying problem is with Task Scheduler.
Click Start and type Task Scheduler
Navigate to Task Scheduler Library >> Microsoft >> Windows >> UpdateOchestrator
To disable automatic reboots right-click on Reboot and select disable.
Then be sure change the permissions. Should be set to Read & Execute
I also disabled automatic updates by disabling all the tasks in this folder.
You can control the time which you allow Windows to automatically reboot per Windows Update operations without disabling anything or forcefully stopping the Windows Update service.
This method will not prevent any Windows Updates from being downloaded or installed ever so OS security patches will still be applied to the system―you just have it reboot when you're ready.
Please note that rebooting may be required before any newly patched vulnerability becomes effective so you need to understand this and still routinely reboot when patches are applied in a somewhat timely manner to ensure your system stays secure.
I will explain with more detail below but essentially this uses a batch script to dynamically set and change the correlated registry values of the the Active hours settings for Start time and End time based on the run time it's executed while ensuring to increment the values to always be hours ahead.
Unlike the Windows 10 Reboot Blocker solution that is not Windows native, this is a 100% Windows native solution that does not require any third party software to complete the task which uses registry keys to manage restart behavior as outlined by Microsoft.
Simply schedule a single Batch Script (provided below) with Task Scheduler to run twice a day:
Each execution sets the ActiveHoursStart and ActiveHoursEnd times to values making Windows think you're always active and ensures no reboot occurs from Windows Update operations.
The batch logic and the scheduling of this process is simple to scale and adjust should you run into any issue (e.g. you run into issues with Power Saving modes such as Sleep or Hibernate.)
NOTES: The registry values are set in hexidecimal format. Also note that the logic example below expects the script to be executed at a frame of 6:00:00 AM - 6:59:59 AM or 6:00:00 PM - 6:59:59 PM only. This can be adjusted easily with the IF %HH%==XX portion of the logic though; you can also use this same logic to test this functionality to confirm it works as expected changing the value.
@ECHO ON
SET HH=%TIME: =0%
SET HH=%HH:~0,2%
IF %HH%==06 SET StartHour=06 & SET EndHour=13
IF %HH%==18 SET StartHour=12 & SET EndHour=07
CALL :ChangeActiveHours
REG IMPORT "%DynamicReg%"
EXIT
:ChangeActiveHours
SET DynamicReg=%temp%\ChangeActiveHours.reg
IF EXIST "%DynamicReg%" DEL /Q /F "%DynamicReg%"
ECHO Windows Registry Editor Version 5.00 >>"%DynamicReg%"
ECHO. >>"%DynamicReg%"
ECHO [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings] >>"%DynamicReg%"
ECHO "ActiveHoursEnd"=dword:000000%EndHour% >>"%DynamicReg%"
ECHO "ActiveHoursStart"=dword:000000%StartHour% >>"%DynamicReg%"
ECHO "IsActiveHoursEnabled"=dword:00000001 >>"%DynamicReg%"
GOTO :EOF
For some detail on the correlated registry settings this will change, below I'll reference the portions of A closer look at Active Hours in Windows 10 for what this method will affect.
Active Hours
Active Hours don't change that behavior, but they add a mechanic to the Windows 10 operating system that makes sure users are not disturbed by reboots during active hours.
Active Hours and the the Registry
Tap on the Windows-key, type regedit.exe, and hit enter.
Confirm the UAC prompt.
Navigate to the following key using the tree hierarchy on the left:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\SettingsThe following options are provided here:
- ActiveHoursEnd: defines the end time of the feature.
- ActiveHoursStart: defines the start time of the feature.
- IsActiveHoursEnabled: if set to 1, the feature is enabled. If set to 0, it is disabled.
If you want to change the starting or end hour of the feature, double-click on one of the entries. Switch to a decimal base on the prompt that opens, and enter the starting hour using the 24 hour clock system.
Please note that you cannot add minutes in the Registry only full hours.
To confirm this works as excepted you will
key one time, and then start typing in Windows Updates until you see the Windows Update Settings options and then click on it
Cancel and then close entirely out from the Settings screens.
run the batch script now ensuring the values are set in the variables accordingly for the time you run the script to ensure it sets the values for the Start time and End time accordingly and ensure it runs without error (run as admin if needed).
Now do steps 1 - 3 again and confirm the Start time and End time values changed correctly.
When you are ready to allow Windows Updates to reboot the machine per it's update operations, you can do so manually since this method does not stop Windows Updates from being downloaded and installed. If you need to disable this job though, that can be done by disabling the scheduled task that executes it with Task Scheduler.
You can use Windows' own tools against it to disable automatic reboots.
As some of the other answers have mentioned, Windows runs its reboots using the Scheduled Task called \Microsoft\Windows\UpdateOrchestrator\Reboot. However, if you open Task Scheduler and disable this one, Windows will happily reenable it the following day -- even if you change its permissions to make it read-only.
Rather than have to go into the Task Scheduler UI to disable the task every day, we can set this up automatically, using the schtasks command-line utility to modify tasks.
If a reboot is scheduled, the following command, run with administrative privileges, will disable the task:
schtasks /change /tn \Microsoft\Windows\UpdateOrchestrator\Reboot /DISABLE
Knowing this, you can create your own Scheduled Task to periodically run the above command and disable Windows' insidious little scheme. If you're familiar with how to use Task Scheduler, set up your own task.
Otherwise,
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.4" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Author>http://superuser.com/users/1909/kpozin</Author>
<URI>\SuperUser\Cancel Windows automatic reboot</URI>
</RegistrationInfo>
<Triggers>
<CalendarTrigger>
<Repetition>
<Interval>PT10M</Interval>
<Duration>P1D</Duration>
<StopAtDurationEnd>false</StopAtDurationEnd>
</Repetition>
<StartBoundary>2016-11-16T18:30:00</StartBoundary>
<Enabled>true</Enabled>
<ScheduleByDay>
<DaysInterval>1</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<!-- That's the SYSTEM user -->
<UserId>S-1-5-18</UserId>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>true</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>
<UseUnifiedSchedulingEngine>false</UseUnifiedSchedulingEngine>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT1H</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>schtasks</Command>
<Arguments>/change /tn \Microsoft\Windows\UpdateOrchestrator\Reboot /DISABLE</Arguments>
</Exec>
</Actions>
</Task>
Other answers require 3rd-party software or a running task/service, and many have to be repeated after Windows updates. This solution has several advantages:
Run this command in Command Prompt as administrator:
cd C:\Windows\System32\Tasks\Microsoft\Windows\UpdateOrchestrator && rename Reboot Reboot.backup & rename Reboot_Battery Reboot_Battery.backup & rename Reboot_AC Reboot_AC.backup & rename USO_UxBroker USO_UxBroker.backup & mkdir Reboot & mkdir Reboot_Battery & mkdir Reboot_AC & mkdir USO_UxBroker & copy NUL Reboot\empty_file & copy NUL Reboot_Battery\empty_file & copy NUL Reboot_AC\empty_file & copy NUL USO_UxBroker\empty_file
cd C:\Windows\System32\Tasks\Microsoft\Windows && takeown /F UpdateOrchestrator /A /R /D y && icacls UpdateOrchestrator /reset /T /C && icacls UpdateOrchestrator /T /C /grant *S-1-5-32-544:F && cd UpdateOrchestrator && rename Reboot Reboot.backup & rename Reboot_Battery Reboot_Battery.backup & rename Reboot_AC Reboot_AC.backup & rename USO_UxBroker USO_UxBroker.backup & mkdir Reboot & mkdir Reboot_Battery & mkdir Reboot_AC & mkdir USO_UxBroker & copy NUL Reboot\empty_file & copy NUL Reboot_Battery\empty_file & copy NUL Reboot_AC\empty_file & copy NUL USO_UxBroker\empty_file
This last command does the same thing, but first gives Administrators ownership of and full permissions to the UpdateOrchestrator folder & contents.
2022 update:
It seems some of the old tasks are being phased out, resulting in "not found" error messages when running the command. These are safe to ignore, as the commands will still prevent reboots.
Windows 11 update:
Unfortunately, this solution does not work for Windows 11, at least for me. Even though Windows uses the same tasks for restart, it seems like Windows 11 will execute the tasks successfully as they are still saved in the registry.
If anyone are able to make this method work on Windows 11, please update this answer or add a comment.
Automatic reboots after updates are performed by Windows Tasks, specifically one of Reboot, Reboot_AC, Reboot_Battery or USO_UxBroker. These tasks are defined in files in the C:\Windows\System32\Tasks\Microsoft\Windows\UpdateOrchestrator folder.
This solution renames these files and creates folders with the same names in their place. It then puts an empty file in each of the created folders.
This effectively deletes the tasks responsible for the auto-reboots, and prevents Windows from re-creating them.
Windows can no longer run the Reboot, Reboot_AC, Reboot_Battery or USO_UxBroker tasks after an update because they no longer exist (except as backups with different names).
When this happens, Windows will attempt to fix the problem by re-creating (or fixing) the expected tasks (files), and then run them. However, Windows will fail to create the needed files because there's a folder with the same name in the target folder and two items in the same folder can't have the same name.
Moreover, since folders and files are different things, Windows will not be able to modify the folders into files containing the correct Task definitions.
Finally, because the command puts an empty file in each of the created folders, it's very unlikely that they will be automatically deleted (which is necessary to re-create the tasks). This is because deleting folders with contents requires a recursive delete command, which would never be used for deleting an object that Windows expects to be a file.
For these reasons, this solution is much more robust than those relying on changing file ownership/access and/or modifying the relevant tasks, something that can be (and frequently is) "fixed" by Windows during updates.
I learned about the technique used in my solution from this article. I have been using this technique for several years and have not experienced a single auto-reboot in all this time except this January (2020) when Microsoft added the new Reboot_AC and Reboot_Battery tasks, which are now also used by Windows Update to initiate automatic restarts.
I have updated the solution myself to account for the new tasks, and it has successfully prevented reboots after the changes I've made.
Late 2020, the task USO_UxBroker was added to Windows. The task description (This task triggers a system reboot following update installation) confirms its purpose, so the solution now also neutralizes this task. Thanks to @Simon East for pointing out this task in the comments.
The entire answer, including the cmd commands, is my own original work.
I've made a PowerShell script that dynamically sets the Active Hours to prevent the unwanted restarts from Windows Updates based on this answer (https://superuser.com/a/1208866/351521). It sets these registry keys:
HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings\ActiveHoursStart
HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings\ActiveHoursEnd
HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings\IsActiveHoursEnabled
You can get it here: https://github.com/marcosbozzani/Win10ActiveHours
Suggestions and Pull Requests are welcomed!
Changes
Converted from Batch to PowerShell (easier to understand and maintain, in my opinion)
The script checks a range of hours instead of a single a hour (as suggested in the comments from that answer)
The script can install and uninstall the Scheduled task and set the appropriated settings and triggers
The script can execute the Scheduled task manually, if needed
Created a Github repository (easier to update and to accept changes)
General information
The task will be created at \Win10ActiveHours\Update
There are two Active Hours windows of 18 hours:
18:00 to 12:0006:00 to 00:00There are four triggers that will active the tasks and switch between the two windows:
06:0018:00These are the settings for the task:
For more information see the README.md from the repository
Windows 10 rebuild his Windows Update Policies adding some diferences between previous versions.
Windows Update will force updates even if windows update service is off, that apply to Home users, since some update requires a mandatory restart, restart scheduler can't be turned off.
That don't mean you can not block the updates, maybe you could do a workarround as block updates servers, but that could be very annoying asuming you have hundred of methods to do that in whole internet.
A Newspaper with Reference Here
Updates. The software periodically checks for system and app updates, and downloads and installs them for you. You may obtain updates only from Microsoft or authorized sources, and Microsoft may need to update your system to provide you with those updates. By accepting this agreement, you agree to receive these types of automatic updates without any additional notice.
Source Windows 10 EULA
Some information about Windows Update for Business explaining the diferences between home users and advantages of enterprise update Here
It seems like "No auto-restart with logged on users for scheduled automatic updates installations" doesn't work currently with Windows 10, but according to this article on Lifehacker.com (http://lifehacker.com/enable-metered-connection-to-delay-windows-10-updates-1723316525), enabling metered connections in Windows 10 might stop or at least further delay Windows Updates.
Windows 10 comes with a feature that allows you to specify that your internet connection is capped, throttled, or handicapped in some way. You may be tethering to your phone, on a public Wi-Fi network, or just have a crappy data cap on your home network. By enabling “Metered connection,” Microsoft will respect that by waiting to force a download. To turn it on, follow these steps:
- Search in the start menu for “Change Wi-Fi settings”
- Click Advanced Options.
- Enable the toggle under “Metered connection.”
The one major downside to this method is that it only works if your computer is connected via Wi-Fi. For some reason, Windows 10 doesn’t allow you to specify that your connection is metered when connected via ethernet (despite the fact that many home internet connections have data caps). However, this should help many typical users.
According to this answer, two actions are both required to disable forced reboot while the user is logged-on. The answer is based on an article (in Italian).
The two required settings are :
NoAutoRebootWithLoggedOnUsersConfigure Automatic Updates policyI do not have the capability to test it in all Windows versions, nor can I guarantee that it will still work tomorrow. But here is how to set these two settings.
This registry modification will disable forced restarts as long as some user(s) are logged-in.
- Click Win+R, type
regedit, and hit Enter- Navigate to the key
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU- If either
WindowsUpdateor its subkeyAUdo not exist, create them manually by right-click on the right-hand panel, thenNew -> Key, type the missing key name and press Enter.- Once positioned into the
AUkey, right-click in the right-hand panel, selectNewand thenDWORD (32-bit).- Type
NoAutoRebootWithLoggedOnUsersand press Enter- Double-click on the item, change its value to 1 and press OK.
- Press Win+R, type
gpedit.msc, and hit Enter.- Navigate to
Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update.- Locate the
Configure Automatic Updatespolicy on the right pane and double-click it.- Select Enabled and Options to
2(Notify for download and notify for install).- Click Apply.
- Press OK to save the changes.
Finally, reboot the PC.
Note about Windows 10 Enterprise
I am running Windows 10 Enterprise with deferred updates.
For what it may help, here are my registry settings from
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU :
And in the Local Group Policy Editor,
Configure Automatic Updates is set to Enabled with Option set to 2.
**** No third party software required for this method ****
For more control ensuring that Windows Update operations only apply to your Windows 10 OS when you want them to, see the below steps using two scripts and one scheduled task job.
This method will work regardless of any scheduled tasks or other processes that kick off Windows Update if it's setup correctly and the job is enabled and running at short enough intervals.
Essentially this will
- Check once a minute to see if the Windows Update service is running and take one of the two below actions whether TRUE or FALSE. . .
- if it is running, then the service is forcefully stopped with NET STOP ensuring that no Windows Updates are applied
- if it is not running, then the process ends until executed on the next scheduled trigger with Task Scheduler
You will need to do three things to ensure this works as expected
- create the simple Batch Script that'll check if Windows Update is running and kill it if it is
- this is just a text document renamed with a
.cmdfile extension- create the simple VB Script that'll execute the batch script but in a hidden manner so there's not a pop up every time it runs
- this is just a text document renamed with a
.vbsfile extension- create the scheduled task to run once a minute indefinitely with Windows Task Scheduler
Below are the detailed steps to follow for setting up these three simple things.
1. Batch Script
NOTE: Save the below logic to a text file and rename to have an extension of .cmd e.g . DisableWU.cmd.
@ECHO OFF
TASKLIST /SVC | FINDSTR /I /C:"wuauserv"
IF %ERRORLEVEL%==0 GOTO :StopWUService
GOTO :EOF
:StopWUService
FOR %%A IN (wuauserv) DO NET STOP /Y "%%~A"
GOTO :EOF
2. VBS Script
NOTE: Save the below logic to a text file and rename to have an extension of .vbs e.g . DisableWUHidden.vbs. Also be sure that you put the correct full path and file name value where the batch file is saved in place of the C:\FolderPath\DisableWU.cmd value in the below logic accordingly.
Set WinScriptHost = CreateObject("WScript.Shell")
WinScriptHost.Run Chr(34) & "C:\FolderPath\DisableWU.cmd" & Chr(34), 0
Set WinScriptHost = Nothing
3. Task Scheduler Job
Press + R, type in taskschd.msc and press Enter. Right-click on the Task Scheduler Library option in the right pane and then select the Create Task option.
From the General tab be sure the Run whether user is logged on or not and Run with highest privileges options are checked so both are enabled and effective.
From the Triggers tab be sure the Daily option is set with Recur every: 1 days and check the Repeat task every 1 minute for a duration of 1 day is set and specified and that the Enabled option is checked.
From the Actions tab be sure Program\script: points to the full explicit path of the VB Script, and be sure the Start in (optional): points to the folder path only where that same VB Script resides.
To finalize and save, press OK (maybe twice), and then type in the username and password credential information from an account that (1. has permissions to run Task Scheduler tasks, and (2. has execute and read access to the location where you saved the scripts it'll execute.
For a quick test to confirm this works as expected you can:
+ R, type in services.msc and press Enter F5 every so many seconds to refresh the screen to see if the service status changes
Blank/Null/Empty/Nothing indicating the service is not running. If you refresh in the middle of a stop operation, you may notice a status value of Stopping for the serviceThis means whether you start Windows Update, a scheduled task starts it, or whatever other process(es) start it, it will be killed every 60 seconds if it is running when this job is enabled and running. This helps ensure Windows Update operations never have sufficient time to ever complete a download or install of any update.
Note: The scheduled interval can easily be adjusted to run more frequently than 60 seconds if that's not quick enough in some instances.
You should apply Windows Updates periodically though at your regular scheduled maintenance intervals to ensure your system is up to date with the latest security patches and so forth. This is not a method intended to totally never apply Windows Updates as these are critical and necessary in many environments so this is intended to just give you better control to choose when you want to apply these updates in your environment.
To disable this process to allow you to manually install Windows Updates when you're ready, you will simply go to the job you scheduled with Task Scheduler, right-click it, and select the Disable option to disable the job and thus preventing the killing of the Windows Updates service.
Once disabled, just run through the motions of applying Windows Updates manually to patch the OS. Once the updates are applied and your power cycles are complete if applicable, simplly Enable the job for it to start running again.
There seems to be two reason people come to this post for an answer to...
Since there are so many answers for this post and a Canonical Answer was requested per a bounty, I figured I'd take a stab at giving a little more clear guidance for the task at hand per the answers from this post.
Note: It's possible that Microsoft releases updates that change the way this correlated functionality works, so if you apply such updates, then these processes may not work as expected afterwards.
Warning
As stated in the "Stop Windows 10 from automatically updating your PC" post. . .
"As a general rule, an up-to-date operating system is a secure operating system. Windows 10 automatically checks for, downloads and installs new updates to your PC -- whether you like it or not. This new feature is actually pretty convenient for most users, but not everyone wants their operating system updated on Microsoft's schedule."
To disable Windows Updates entirely you can follow the instructions from two specific answers on this post linked just below as #1 and #2 and perform the operations specified in both but #1 at a minimum or #1 and #2 for extra thoroughness.
Turn off Windows Updates in Windows 10 and Disabling Task Scheduler Jobs
/Microsoft/Windows/Windows Updates container, it might be worth disabling all those jobs in there for complete thoroughness.Warning
Please note that rebooting may be required before any newly patched vulnerability becomes effective so you need to understand this and still routinely reboot when patches are applied in a somewhat timely manner to ensure your system stays secure.
There seems to be at least two answer that work best here for most people so I'll start with the Windows native solution and then tell you about the 3rd party solution.
To control when Windows reboots post Windows Update installs you can follow the instructions from either of these two answers on this post. . .
3rd Party App: Windows 10 Reboot Blocker
As Windows rules and methods change and no method works forever, here are some free third-party products that will postpone shutdown (and more). They may use the Windows API which allows any program to veto an impending shutdown or disable Windows system services.
A portable freeware that helps to completely disable or enable Automatic Updates on Windows with one button click. It does a good job of disabling Windows Update system services, including the unstoppable Windows Update Medic Service.
A small program that can block various Windows events from the traybar, only recently updated on January 2019.
An older program that sits in the system tray and prevents Windows from shutting down,
rebooting or logging off.
There are a few options available in the tray menu such as hiding the tray icon,
disabling the program temporarily and forcing a shutdown, and a few other
configuration settings are available in an .ini file which can be edited with Notepad.
Shut It! can monitor and block shutdowns and restarts etc, but also it can do so in view of the currently executing application processes or windows and perform a different action for those that match.
It's only available for download from third-party websites.
Source:
If you absolutely must not allow your system to reboot due to Windows Updates without it being "controlled" when you are present, schedule down time for maintenance, or whatever the case, then you could disable the Windows Update service.
Manually Controlling Windows Updates
This would mean that this machine would not get critical security updates, etc. unless you re-enable and then manually download, install, reboot, etc. and then disable once the patching is complete.
WARNING: This could be dangerous and is not recommended and especially in a home network environment. In a business or data center environment though, it is normal for companies to control when they will make changes, install security updates, patch OSes, and so on.
Turn off Windows Updates in Windows 10
You can do this using the Windows Update service. Via Control Panel > Administrative Tools, you can access Services. In the Services window, scroll down to Windows Update and turn off the process. To turn it off, right-click on the process, click on Properties and select Disabled. That will take care of Windows Updates not being installed on your machine.
But since Windows is a Service now onwards, you have to keep your computer updated. To be able to install the next set of features or a newer build, you will require the earlier updates to be installed. That’s why if you use the above workaround, you will have to go to the Services and turn it on once in a while to download and update your copy of Windows.
Manually Starting Windows Updates and Running it
After you turn on the Windows Update service, when you open Windows Update in PC Settings, you will see a message that updates were not installed because computer was stopped. You will have to click on Retry so that all the available updates are downloaded and installed. This may take two or three “Check for Updates”. You will have to keep on clicking “Check for updates” until it says your computer is up to date. Then you can go back and turn off the Windows Update service until next time you feel you are free enough to spend time updating your copy of Windows 10.
It seems that there are some scheduled tasks related to Windows Update scheduled to trigger Windows Updates perhaps.
Press + R, type in taskschd.msc and press Enter. Navigate to Task Scheduler Library > Microsoft > Windows > WindowsUpdates, and then right click and select the Disable option for the job named Scheduled Start.
Update: After testing, my previous solution failed to be effective. Microsoft seems to have implemented features that prevent even it from working.
My final solution was to use a utility called StopUpdates10. It combines all of the techniques I've read about over the last few months, notably multiple registry changes and the disabling of multiple services—rather than just the couple that keep being mentioned but which don't work on their own.
Up until last night, I had prevented my computer (which hosts services requiring it to be on 24/7 unless I specifically scheduled downtime) from automatically applying updates and rebooting. I had done this by disabling the Windows Update service—one of the answers here.
This morning, I discovered that it had rebooted automatically and that the Windows Update service had been re-enabled. This is not behaviour that Windows 10 has ever exhibited for me before. I can only assume that something has changed in 2018, and that Microsoft has rolled out an update this year (which I would have applied when manually updating my system) that re-enables the Windows Update service even if you've disabled it.
I have since disabled the Windows Update service once more—but now also removed all inherited permissions from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv, and given only myself anything other than read-only access to it.
In addition, I have taken ownership of C:\Windows\System32\sihclient.exe (the binary responsible for background updates), removed all permissions to it aside from myself, and renamed it.
I will not know if this is successful (one or the other or both) until one or more months have passed.
A simple option is to set active hours outside your working hours.
Windows now only has a 6-hour window to reboot and I'm actively working during that time so it will ask me.
OK, so this is an old thread but I found nothing working for Windows 10 20H2.
It appears that in Windows 10 20H2 two scheduled tasks are created in \Microsoft\Windows\UpdateOrchestrator\, named Reboot_AC and Reboot_Battery.
When there are no pending reboots, the tasks have a start date in the past and are set to Disabled.
These tasks can only be edited by System, but when you do attempt that, you are prompted for a password when saving.
So I created a task in Task Scheduler, that runs every minute and calls a small PowerShell script that for each scheduled Reboot_* task, replaces the trigger with a new one with a start date 7 days in the future and disables the task nonetheless.
Note that this does not disable any reboot notifications.
Also, I use this in conjunction with Active Hours so that it is most likely a reboot is scheduled somewhere in the future.
Powershell file PostponeWindowsUpdateReboot.ps1:
$TaskPath = '\Microsoft\Windows\UpdateOrchestrator\'
$NewTrigger = New-ScheduledTaskTrigger -At ([DateTime]::Now.AddDays(7)) -Once
'Reboot_AC', 'Reboot_Battery' | ForEach-Object {
Set-ScheduledTask -TaskName $_ -TaskPath $TaskPath -Trigger $NewTrigger
Disable-ScheduledTask -TaskName $_ -TaskPath $TaskPath
}
The scheduled task that disables both Reboot_* tasks must run as System and set to run with highest privileges.
This is an XML dump of it (assuming that the script is named D:\tools\PostponeWindowsUpdateReboot.ps1):
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Date>2021-05-03T12:46:10.9447093</Date>
<Author>PC\eelco</Author>
<URI>\PostponeWindowsUpdateReboot</URI>
</RegistrationInfo>
<Triggers>
<CalendarTrigger>
<Repetition>
<Interval>PT1M</Interval>
<Duration>P1D</Duration>
<StopAtDurationEnd>false</StopAtDurationEnd>
</Repetition>
<StartBoundary>2021-05-03T00:00:00</StartBoundary>
<ExecutionTimeLimit>PT30M</ExecutionTimeLimit>
<Enabled>true</Enabled>
<ScheduleByDay>
<DaysInterval>1</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>S-1-5-18</UserId>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>true</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT72H</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>powershell.exe</Command>
<Arguments>-File D:\tools\PostponeWindowsUpdateReboot.ps1</Arguments>
</Exec>
</Actions>
</Task>
I am currently still testing if the tasks ever get a new trigger assigned when new updates are received, and if an interval of 1 minute is sufficient (or overkill).
Hope this helps anybody searching to tame Windows Update.
Most of the answers here are rather old now and I wanted to have a "clean" solution that doesn't involve renaming system files or running background tasks. The latter might also not work when putting the system to sleep, as I often do at night when I go to sleep, but want to keep the system state/continue with my work the next day. Disabling Windows Update completely is also not wanted.
After about two hours of research, reading up on multiple ways, I tried and came up with the following solution, for the "Pro" Edition:
gpupdate /forceThat's it! The changes are immediately effective and you can put your system to sleep safely if there was a restart pending already - Windows should keep your system in sleep mode and will not automatically restart if you leave it running, as one would expect.
I researched and applied these settings back in November 2021 and wanted to put them to the test before posting - so far I haven't had (these) troubles with Windows updates anymore and I've had a few pending restarts since then and uptimes of up to ~2 weeks. At least on Windows 10 Pro Version 21H1 that is; things might change in the future/with newer versions again.
Some sources I used (maybe additionally helpful), besides this question:
https://superuser.com/a/973029/457901
https://www.itechtics.com/disable-automatic-restart/?expand_article=1
I have really appreciated this previous answer, using the Native Windows Solution of a Batch Script to continually update active hours.
I have made a few minor tweaks, both for readability and usability:
@echo off
REM -- Command line parameters
set VERBOSE=Y
if [/Q] == [%~1] set VERBOSE=
if [/q] == [%~1] set VERBOSE=
REM -- Get the current timestamp
set D=%date%
set T=%time: =0%
set dow=%D:~0,3%
set mm=%D:~4,2%
set dd=%D:~7,2%
set yy=%D:~12,2%
set yyyy=%D:~10,4%
set hh=%T:~0,2%
set min=%T:~3,2%
set ss=%T:~6,2%
set ms=%T:~9,2%
REM -- Source: https://superuser.com/a/1208866/
if %hh%==00 set HH_START=17 & set HH_END=0d
if %hh%==01 set HH_START=00 & set HH_END=0e
if %hh%==02 set HH_START=01 & set HH_END=0f
if %hh%==03 set HH_START=02 & set HH_END=10
if %hh%==04 set HH_START=03 & set HH_END=11
if %hh%==05 set HH_START=04 & set HH_END=12
if %hh%==06 set HH_START=05 & set HH_END=13
if %hh%==07 set HH_START=06 & set HH_END=14
if %hh%==08 set HH_START=07 & set HH_END=15
if %hh%==09 set HH_START=08 & set HH_END=16
if %hh%==10 set HH_START=09 & set HH_END=17
if %hh%==11 set HH_START=0a & set HH_END=00
if %hh%==12 set HH_START=0b & set HH_END=01
if %hh%==13 set HH_START=0c & set HH_END=02
if %hh%==14 set HH_START=0d & set HH_END=03
if %hh%==15 set HH_START=0e & set HH_END=04
if %hh%==16 set HH_START=0f & set HH_END=05
if %hh%==17 set HH_START=10 & set HH_END=06
if %hh%==18 set HH_START=11 & set HH_END=07
if %hh%==19 set HH_START=12 & set HH_END=08
if %hh%==20 set HH_START=13 & set HH_END=09
if %hh%==21 set HH_START=14 & set HH_END=0a
if %hh%==22 set HH_START=15 & set HH_END=0b
if %hh%==23 set HH_START=16 & set HH_END=0c
REM -- Clear any previous settings
set "OUTPUT_FILE=%TEMP%\UpdateWindowsActiveHours.reg"
if exist "%OUTPUT_FILE%" del "%OUTPUT_FILE%" >nul 2>&1
if exist "%OUTPUT_FILE%" if [Y] == [%VERBOSE%] echo.
if exist "%OUTPUT_FILE%" if [Y] == [%VERBOSE%] echo Cannot create output file: "%OUTPUT_FILE%"
if exist "%OUTPUT_FILE%" goto end
REM -- Create the registry settings for active hours
echo Windows Registry Editor Version 5.00 >"%OUTPUT_FILE%"
echo. >>"%OUTPUT_FILE%"
echo [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings] >>"%OUTPUT_FILE%"
echo "ActiveHoursEnd"=dword:000000%HH_END% >>"%OUTPUT_FILE%"
echo "ActiveHoursStart"=dword:000000%HH_START% >>"%OUTPUT_FILE%"
echo "IsActiveHoursEnabled"=dword:00000001 >>"%OUTPUT_FILE%"
REM -- Import the file into the Windows registry
if [Y] == [%VERBOSE%] echo Updating settings for active hours. Please wait...
reg import "%OUTPUT_FILE%" >nul 2>&1
if exist "%OUTPUT_FILE%" del "%OUTPUT_FILE%" >nul 2>&1
:end
if [Y] == [%VERBOSE%] echo.
if [Y] == [%VERBOSE%] pause
There is also an AutoHotkey version (in case you get tired of the little black command prompt popping up briefly every hour):
#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
#Warn ; Enable warnings to assist with detecting common errors.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.
; Hide the tray icon
#NoTrayIcon
; Configuration
G_REG_ROOT := "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings"
; Numbers that rollover need to be kept within the boundaries
G_hhMin := 0
G_hhMax := 23
; For active hours, Windows will allow a maximum duration of 18 hours
; (below will use only a 14 hour duration)
G_hhStartOffset := -1
G_hhEndOffset := 13
; -----------------------------------------------------------------------------
; -----------------------------------------------------------------------------
; Get the current hour of the day, with leading zero
; 24-hour format (00 – 23)
FormatTime, hh,, HH
hhStart := PadWithZeros(GetHHStart(hh, G_hhStartOffset))
hhEnd := PadWithZeros(GetHHEnd(hh, G_hhEndOffset))
SetRegistryKey(G_REG_ROOT, "ActiveHoursStart", "000000" hhStart)
SetRegistryKey(G_REG_ROOT, "ActiveHoursEnd", "000000" hhEnd)
SetRegistryKey(G_REG_ROOT, "IsActiveHoursEnabled", "00000001")
; -----------------------------------------------------------------------------
; -----------------------------------------------------------------------------
GetHHStart(hh, hhOffset)
{
local
global G_hhMin, G_hhMax
hhStart := hh + hhOffset
return (hhStart < G_hhMin ? (G_hhMax + hhStart + 1) : hhStart)
}
GetHHEnd(hh, hhOffset)
{
local
global G_hhMin, G_hhMax
hhEnd := hh + hhOffset
return (G_hhMax < hhEnd ? (hhEnd - G_hhMax - 1) : hhEnd)
}
PadWithZeros(s)
{
return (StrLen(s) < 2 ? "0" . s : s)
}
; -----------------------------------------------------------------------------
SetRegistryKey(regRoot, regKey, regVal)
{
RegWrite, REG_DWORD, %regRoot%, %regKey%, %regVal%
}
Verified on
Edition Windows 10 Pro
Version 22H2
OS build 19045.3324
Experience Windows Feature Experience Pack 1000.19041.1000.0
