On Sun, 26 Aug 2018 22:48:13 -0700, Justin Tyme
wrote:

On Mon, 27 Aug 2018 01:04:06 -0400, Paul
wrote:

Bob_S wrote:
"Justin Tyme" wrote in message
...

This is mostly for the diehard Windows 7 fans who often mention auto
reboots after running Windows Update as a huge problem with Windows
10. Those of you who use and trust the settings in Windows Update
probably don't need this info. It is nice to have Windows ask you to
download updates instead of updates happening automagically.


Permanently stop WU Auto Restarts

Copy paste in Run:

C:\Windows\System32\Tasks\Microsoft\Windows\Update Orchestrator

snipe....

That path not valid for Windows 7

Bob S

UpdateOrchestrator only exists on Windows 10.

Why would you care about it on Windows 7 ?
It's not part of how Windows Update works there.

Windows 7 has the 0..4 setting that actually
works to give the user control over updates.

UpdateOrchestrator, as the name implies, is an Enterprise
scheme for beating employees into compliance. If you
disable Windows Update (or try), there are task scheduler
entries owned by UpdateOrchestrator, which are there
to defeat your attempts. A guess would be, it's also
placed on regular user desktop systems for "test"
purposes. Microsoft uses the desktop fleet, to ensure
a higher quality on the Enterprise releases later.

So if you want to play Whack-A-Mole with Windows Update
in Windows 10, you have to defeat two things. Defeat
Windows Update itself. But also defeat UpdateOrchestrator
plus the garbage stuffed into Task Scheduler. It's a kind
of belt-and-suspenders thing from Microsoft (pretty close
to a tag-team malware design).

Paul

This only stops auto reboot, it doesn't interfere with Windows update,
it just won't reboot on it's own. You have to click reboot but other
than that everything works normally in Windows Update. A person can
easily reverse it and it goes back to default. If you have any doubts
try it in a VM.

I have only used this method in a VM since I find the WU schedule
settings to be good for the one computer I have that runs Pro and, as
I have mentioned, my main computer runs LTSB which is set to Notify
before download. All the windows updates have worked in the VMs for
the past couple of months, so far no problem.

Winaero has this on their site. I am not at home and the wifi is bad
here so I can't give you a link. Winaero says you can disable reboot
in Task Scheduler but it can come back, they went on to describe this
method to permanently stop the reboot. I was only able to turn off
reboot in Task Scheduler on two of my VMs, the third, permissions
would not allow. Strange as all three VMs were from the same Pro iso.
So far it doesn't seem to matter if you disable it in Task Scheduler
as doing the rest of the procedure, as I posted, works well for me.
There is no harm from this because everything reverts back when you
remove the .bak extension and delete the folder named Reboot.

I tried the same registry edit that I used on my LTSB version to make
it 'Notify to download' but at first it didn't work on Pro, so I
looked in the registry for the key to change the DWord but AU wasn't
in registry. I did the reboot fix and the .reg file worked, so I
looked in the registry and the AU section of Windows update was there
now. It must be hidden and only appears after fixing the reboot. In
the early versions of Win10 you could also do this with gpedit but no
longer.

As I mentioned, I did this sometime in June and have not seen any
problems in any of the VMs I did. I tested a vm copy the other day to
see what remained of tweaks after updating to v1803 and Windows Update
still was set to Notify for download. If you find problems with this
method I would be very interested.
--
JT