Disable Windows 10 automatic restart after updates

When I attempt to save the changes in Step # 7, I get a pop-up box titled "Task Scheduler", which asks for an username and password.  The problem is that my username is not among the list of users, yet I am the only user of this computer, and I am an authorized Administrator for the PC.  Additionally, none of the listed "users" are actually authorized accounts for this computer.

Furthermore, I have been unable to find any way to give my user account permission to save the new file location.

Your help on this would be greatly appreciated.

I finally found a simple solution for this, tested on 1809 and 1903, home & pro (hopefully they don't break it on 1909).

It is not perfect as you will stop getting the notifications but I think you still get the little dot(I think only on 1903) on the Power button when you open the Start.

original solution(most likely you'll want to ignore the reboot script part): https://lazyadmin.nl/it/how-to-stop-automatic-restart-win-10-after-installing-updates/

backup: https://redd.it/d4b6du

The solution is this .reg file:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\MusNotification.exe]

"Debugger"="cmd.exe"

Windows ten update auto restart just lost a week of my work.. Can I sue Microsoft.. how do I handle this?

Windows ten update auto restart just lost a week of my work.. Can I sue Microsoft.. how do I handle this?

We all wish!!! The response will be Save and Backup. You can pay for online space with MS for your backups in the cloud. 

But the truth is that it would appear they don't give a hoot about small users. I never received a call back after putting in a support request regarding this issue either. Possibly all their funds have gone toward the telephone help desk and training people to tell users how to restart their systems.

Such a sad state of affairs and I wish there were something that could be done legally to hold them accountable.

For those that consider Linux too small a contender for that last sentence to be anything but a joke:  consider that Android is just a modified Linux OS, and currently holds the largest market share among all internet-connected devices, having overtaken Windows by 2017.  Not long after Windows 10 was released, come to think...

I know that this is not going to work for many, but I can only tell that I am for some time always working with two computers: one main computer with Linux, and a second one with Windows. I am doing software development for large projects that often take hours to compile and build, and I am running also lengthy simulations. And of course software development is a field where Linux is really strong, and it is not a big deal to rely on tools that work on both Linux and Windows (like Qt, CMake...).

On the Linux machine I am doing all the trials and developments - because it is "my computer" and it does what I want! Updates? No problem: the system will tell me that updates are ready, and most of the time reboot is not required afterwards. And if it is, I am told and I can do it whenever it is convenient. So EXACTLY the behaviour that I would like to see for Windows as well!

If they want they can make it an option that has to be enabled first - because I can also believe that 90% of users have a) no problems with the auto-update and auto-reboot, b) would not do it if they were asked ("it worked so far - why should I update?"), but also c) would never change any setting - so problem is solved - for all. Don't forget that the remaining 10% are still MANY! And for them this auto-reboot is really a nightmare. And this "feature" is one of the reasons why I avoid the system as much as possible for real professional IT work.

Once some software needs to be packaged and delivered I have to go for a build on Windows (and still fix some Windows specific quirks after the software is overall running well). Because most customers are using Windows. So just yesterday I started such a build overnight - and in the morning I found again the entire thing not done - because Microsoft in their infinite wisdom had decided that they wanted to kill the run!!

Which brought me to another round of research if there is not finally a solution of that problem, but it looks that there is none so far.