Disable automatic reboot after Windows Updates in Windows 10

Martin Brinkmann
Sep 20, 2016
Updated • Jul 5, 2017
Windows, Windows 10

One of the most frustrating experiences on Windows is the operating system's default updating behavior.

Windows is configured to download and install patches automatically when they become available. Many require a restart before they are fully installed on the system, and Windows will restart the system automatically if that is the case.

While you can delay the inevitable restart if you are in front of the PC at that time, there is little that you can do about it if you are not.

Previous versions of Windows allowed you to block Windows Update restarts using the Group Policy or Registry, but it appears that these options don't work currently on Windows 10.

Disable automatic reboot after Windows Updates in Windows 10

windows update restart prompt

At least some users reported that they cannot block Windows 10 from restarting the PC after updates are installed. They changed the Group Policy entry that let them do so on previous versions of Windows, but it does not do a thing on Windows 10 on their PCs.

There is another solution as Reddit user Scurro points out on the site. It is a bit technical in nature, as it requires the disabling of a scheduled task, and taking ownership of the file associated with that task.

The process itself is straightforward however, here it goes:

Step 1: Task Scheduler

disable windows update reboot

First thing you do is open the Windows Task Scheduler and disable the reboot task. Here is how that is done:

  1. Tap on the Windows-key on your keyboard, type Task Scheduler, and hit enter.
  2. Use the left pane to navigate to the following task: Task Scheduler > Task Scheduler Library > Microsoft > Windows > UpdateOrchestrator
  3. Locate the task with the name Reboot, right-click on it, and select Disable from the context menu.

This completes the first step in the process.

Step 2: Download and run Take Ownership

take ownership

While you can take ownership manually, I suggest you use a program for that instead as it makes things a lot simpler.

  1. Download Take Ownership from this Ghacks article (we host the program on our own server).
  2. Extract the archive on your system, and run the executable file afterwards.
  3. Click on the install button to add a "Take Ownership" option to the right-click menu of File Explorer.
  4. Verify that the option is available by right-clicking on any file in File Explorer or on the desktop.

Step 3: Take Ownership of the reboot task file

reboot take ownership

Now that all preparations are done, it is time to take ownership of the reboot file. We need ownership later on as we will remove access to reboot for all other users and groups.

  1. Open a File Explorer window.
  2. Navigate to the location: C:\Windows\System32\Tasks\Microsoft\Windows\UpdateOrchestrator
  3. Please note that you can copy and paste it, as it is easier than navigating to the location manually.
  4. Right-click on the file called Reboot, and select the "Take Ownership" option from the context menu.

Step 4: Disable access to reboot for all other users and groups

reboot permissions

  1. Right-click on Reboot and select properties.
  2. Switch to Security, and click on the Advanced button.
  3. Select the "change permissions" button to edit permissions for the file.
  4. Select "disable inheritance" next, and on the prompt that opens "remove all inherited permissions from this object".
  5. This should remove the majority of users and groups.
  6. Remove any other user or group still listed there.
  7. Click on the "add" button afterwards.
  8. Click on "select principal".
  9. Add your username under "enter the object name to select", and click "check names" afterwards.
  10. Click ok.
  11. Select Full Control on the next page and click on ok.
  12. You should see one permission now on the "Advanced Security Settings for Reboot" page, and that one permission should be full control for your user account.
  13. Click ok to complete the process.

The result of this lengthy process is that updates get installed automatically, but restarts are not scheduled anymore.

Now You: How do you handle Windows Updates?

Disable automatic reboot after Windows Updates in Windows 10
Article Name
Disable automatic reboot after Windows Updates in Windows 10
Find out how to block Windows 10 from automatically restarting your PC after Windows updates are installed on the system.
Ghacks Technology News

Tutorials & Tips

Previous Post: «
Next Post: «


  1. gits68 said on November 12, 2022 at 3:41 am

    Disable Reboot* tasks in \Microsoft\Windows\UpdateOrchestrator isn’t sufficient as they are reactivated by windows.
    The best solution I found is to create a task as the System user which disable these tasks every hour using the following commands :
    C:\Windows\system32\cmd.exe /c “schtasks.exe /change /TN \Microsoft\Windows\UpdateOrchestrator\Reboot_AC /disable”
    C:\Windows\system32\cmd.exe /c “schtasks.exe /change /TN \Microsoft\Windows\UpdateOrchestrator\Reboot_Battery /disable”

  2. marcusant said on November 9, 2016 at 8:04 pm

    great work, thanks

  3. Wim said on October 12, 2016 at 10:34 am

    Thanks for this, after so many times leaving my home automation system in havoc in the middle of the night,
    I am hoping this will bring me back to control MY system, and not some “high level thinkers” without knowledge or fantasy how a system might be “used” and who think a PC is only used for 8 hours max in a family house?

  4. chesscanoe said on October 6, 2016 at 9:28 pm

    I’ll be experimenting with the solutions posed here for my Win10AU home PC. I’m also looking at the last solution posed at
    I want to have confidence the way I choose to “fix” this design flaw stays fixed until I choose to “unfix” it. :-)

  5. linc said on October 1, 2016 at 10:16 am

    @Chris: I’ve tested it and think white space should be fine. To see your actual user name, hit windows-key+r and run this command: “cmd /K whoami” (not the quotes, of course). You’ll see something like “domain\john”, here “john” would be the user name.

  6. Chris said on September 30, 2016 at 11:49 pm

    I’m getting a message saying my name is invalid for the add principal. Is it because it has a space it?

    1. Jay said on November 4, 2016 at 12:10 am

      Your username might not be what you think it is inside the system, especially if you’re logging in with a Microsoft account. Open the Add Principal dialog and then click Advanced->Find Now. Scroll down the list until you find your username/email, select it, press Ok, press Ok.

  7. linc said on September 30, 2016 at 5:03 pm

    You can take ownership without using a third party tool (at least in professional): open the file’s properties and go to the security tab. Click on ‘Advanced’ and you should see the current owner in the upper part of the window. Click on ‘Change’, enter your user name and click ‘Check Names’. Unless you got an error message, you can now ‘OK’ your way out of the window cascade. Done.

    1. Uwe said on October 4, 2016 at 3:41 am

      That works in the standard edition, too. And if you get an error after “Check Names”, just click on “Advanced”, then “Find Now” and you get a list.

  8. JOM said on September 30, 2016 at 4:24 pm

    I have not seen any mention on this site of the Windows 10 problem of random restarting – and I don’t mean after an update download.

  9. Dave said on September 21, 2016 at 7:24 pm

    Why people still think of such a complicated ways??? Just disable the update service and enable it once a week or month to update and then disable it again. You can even create shortcuts with the command if you are that lazy…

    1. Jay said on November 4, 2016 at 12:06 am

      Because I want my computer to be updated, just not rebooted while I’m in the middle of something.

      Manually turning the service off and on is annoying and it’d be another thing I’d have to remember to do. The method described above however allows Windows to download and install the updates, let me know that it’s done so, and I can simply reboot once I’m done whatever I’m doing.

    2. Uwe said on October 4, 2016 at 3:39 am

      People think of complicated ways because easy ways are blocked by people who think they can dictate how we work and how we should be inconvenienced. Anyway, this is my no means more complicated than moving and renaming a file, which you do all day long.
      I find it certainly more complicated (or rather, annoyingly cumbersome) to enable and disable the service every month, let alone every week. Automation rules (or in this case disabling some automation) – set it and forget it. Took me less than 5 minutes to implement this solution. Great idea, Martin!

    3. Mr. Coleman said on September 22, 2016 at 8:31 pm

      I just went to do that and there is no longer a ‘disable’ option under Properties. So I found this page.

  10. simexi said on September 21, 2016 at 11:26 am

    How about only step 1 + rename Reboot -> Reboot.bak ?

    1. Martin Brinkmann said on September 21, 2016 at 11:38 am

      It would probably get re-added at one point then.

      1. simexi said on September 23, 2016 at 11:34 am

        Well.. Not yet… Done this about 2 weeks ago..

  11. Andrew said on September 20, 2016 at 6:07 pm

    I did this just a little while ago after getting fed up waking to find my computer off. This seems like the only way to do it as the GP method doesnt work anymore. Guess I will have to wait and see how well this works.

  12. Mike said on September 20, 2016 at 6:05 pm

    I haven’t updated to the anniversary edition yet, but I’ve just disabled the windows update service. I had problems at home with it downloading updates and slowing my internet at inopportune times. Also we use it at my church and can’t have it deciding to restart in the middle of a service.

  13. Wade said on September 20, 2016 at 5:41 pm

    As a computer technician, half my though, my eyes glazed over and I just scrolled put the rest. My company user doesn’t seem to bother me in the first place with forced updates, and since it can start up in 30 seconds in the first place, updates are no problem. Neat solution. Too much trouble. Thanks for the info though.

    1. Luke said on October 6, 2016 at 7:48 pm

      My problem with automatic updates isn’t the amount of time it takes for the reboot to take place. It’s the fact that Windows doesn’t seem to be able to recognize that there are times when my computer is in the middle of running a really long-lived task which MUST NOT be interrupted for any reason: be it datalogging where even one second of inattention could lead to a completely useless dataset, or compiling a really large piece of software, or synthesizing a comprehensive test suite on a complicated FPGA design. It just isn’t practical for me to stand there watching my computer for the 20 to 30 hours it takes for the task to complete.

      In the mean time, with the default behavior of the Anniversary Update, when an update is pushed to my machine, the best case scenario is that I’ll get a notification in the afternoon (given Microsoft’s typical schedule for pushing out updates) of an update that will automatically be installed the next morning at 3:00 AM. If I catch the notification in time, I can schedule the update to manually install at some time within the next 7 days.

      At the moment, that setting is grayed out and inaccessible, except for the tiny interval between the time when an update has been downloaded, and 3:00 AM the next morning when the update is installed no matter what. Alternatively, I can set my computer’s “Active Hours” for a time when I know my computer won’t be doing anything important. But there is no setting for “My Computer Will Be Active All Day Every Day For The Next 36 Hours”.

      If I miss the notification, or if the notification comes up after I’ve gone home for the day, then the install/reboot will happen at 3:00 AM, no matter what. That’s useless if I already know for a fact that the test I’ve been running since 8:00 this morning will most definitely still be in the thick of it by the time the scheduled moment rolls along.

      For me, the problem could be solved if the “Custom Restart Time” option was accessible all the time, instead of only when an update is already pending. When I was just about to start a long-lived task, I could say to myself, “I know that any automatic reboot at any point during the next 36 hours would cause me to irretrievably miss the ongoing logging of important data from my experiment. I’d better tell Windows about it, so it won’t go behind my back and reboot in the middle of the experiment.”

  14. Patrick said on September 20, 2016 at 3:19 pm

    Thank You for your time & effort you put in these articles.

  15. meepmeep said on September 20, 2016 at 3:18 pm

    Good info. Microsoft must have Rube Goldberg working for them.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.