On Mon, 24 Sep 2018 05:57:31 -0400, Paul wrote:

Justin Tyme wrote:
On Sun, 23 Sep 2018 22:58:51 -0700, Justin Tyme
wrote:

On Mon, 24 Sep 2018 01:09:17 -0400, Paul
wrote:

Justin Tyme wrote:
On Sun, 23 Sep 2018 21:06:15 -0500, Char Jackson
wrote:

On Sun, 26 Aug 2018 10:32:12 +0100, mechanic
wrote:

On Sat, 25 Aug 2018 16:10:10 -0700, Justin Tyme wrote:

IIRC, you mentioned the unexpected reboots as one of the big
issues. You no doubt have Windows 7 set to 'Notify you before
downloading updates' and the unexpected reboot thing is totally
unacceptable. I get that. A reboot/update just as you are about
to do a business presentation must be fairly disturbing, to say
the least. You can schedule these things in Windows Update and it
does seem to work effectively. If you still do not trust Windows
10 it can be fixed permanently.
If you're talking business presentations you're using Win10 Pro no
doubt. If not you're going to come across as a clueless amateur. In
that edition it's easy to control updates and reboots.
https://docs.microsoft.com/en-us/win...e/waas-restart
Please tell me more about controlling updates and reboots. I know about
the Active Hours control, but I'm not clear on how I can reboot on my
schedule, which is roughly every 60-90 days, or longer if I feel like
it.
Control Reboots


https://winaero.com/blog/how-to-perm...lling-updates/

Auto reboots won't happen. You will have to click restart manually.
Just like Windows 7. This setting sticks even after major updates, so
far I tested v1709 to v1803 and it didn't change. We'll see what
happpens when the fall update arrives.


Make windows ask to download updates:

GPedit.msc computer configuration administrative templateswindows
componentswindows update configure automatic updates select 2

'Notify before downloading'. Yes this still works or you can change
the the D word to 2 in the registry key. Don't have the name of the
key handy. It is the AU section of the Windows update key.

With v1803 it has changed to 'Notify before download and Auto install'
but it will not reboot unless you want it to. You also have to
manually click Download, if you don't it will message in the corner of
your screen. 'Updates are ready to download'. You can ignore it if you
like but every day or two the message will appear in the corner of the
screen saying you need updates. Just dismiss the message.

You will at some point click the message and install the updates. I
don't recall Windows 7 being any different but Win7 gave you the
choice for no updates. I have almost forgotton the Windows 7 stuff.

If you do the reboot fix first, which I recommend, then you
essentially have Windows 7 style. In Windows 7 you could set to
notify before downloading updates and reboot when you wanted. This
will be exactly the same.

Didn't mean to get carried away and push Windows 10 on you. I know the
last post was a littly pushy, what can I say, I like Windows 10. I was
kind of waiting for a post from you with your cutting whit

Weekends I stand on the street corners and hand out Windows 10
pamphlets. The rest of the week I knock on doors to see if everyone
has heard the good word

PS: Better yet get, the LTSC when it comes out. Like Windows 7 but
modern and good. Much more control and no BS feature updates all the
time.

Take care,
The comments at the end of your page, tell the story.
The feasibility of the fix changes with time.

https://winaero.com/blog/how-to-perm...lling-updates/

This is why I don't even need to test this stuff :-(

Paul
Nope you are wrong. Test it, it remains after updates. So do a lot
more things that you thought, according to the last (vm) test I did
We'll see what the next update brings.

This is why I don't even need to test this stuff :-(

This really surprises me. I always thought you were the mad scientist
in the group. How can you make these statements without testing that
the statement is true? Sometimes things that you always thought were
true are not. I think that is the case here.

When I see a comment section on a page like that, and
a commenter there says "it's no longer working", I tend to believe
them.

How do we know that there isn't another mechanism for
rebooting after an update ? We can't "prove" there isn't
a way. Or a way that only applies to a particular update.

Now, the winaero web page has a "recipe" shown that
uses the Win10 GUI. I take it you didn't use that, and
you're using the script from the comment section.
This script.

http://textuploader.com/dsvox

The most powerful part of that script, is the last line.
I didn't read the thing all the way to the bottom the
first time.

schtasks /create /tn "Win10 update auto-reboots disable check"
/tr "c:\tools\disable-win10-update-reboots.bat" /sc onlogon
/rl highest /f nul

That re-applies the fix at every logon. Versus the graphical recipe
which is the subject of the web page, doesn't have that feature.
The script (like USO), uses the Task Scheduler to increase
the effectiveness of the script. C:\tools will be preserved from
one OS revision to the next. The method will work as long as:

1) Schtasks isn't cleaned out by an Upgrade.
2) The tasknames don't change, or the USO design
doesn't change. And we have no assurance as to how
many reboot mechanisms exist. Such mechanisms have to
exist for "emergencies", where Microsoft needs to use
a back door to update the OSes (under exploit conditions),
and the emergency update must be applied immediately.

On the first reboot after an Upgrade, the script will be running,
and will remove the Reboot item.

For the people who might report "it isn't working", we
don't know what isn't working, if we don't know whether
they followed the given GUI recipe, or they read the
comment section and used the script.

I'm not getting a warm fuzzy here. I'll stick with Win7 for work and a
mix of 7 and 8 at home, with some 10's as unused VMs.