Upgrades AFTER installation

With Win 10 HOME upgrades and required reboots are done automatically at
MS's discretion when on a wired network.

Is it true that these upgrades and reboots will wait until the PC is idle?

If yes, would a running batch waiting in a TIMEOUT be considered idle?

--
Zaidy036

On 03/18/2016 12:25 PM, Zaidy036 wrote:
With Win 10 HOME upgrades and required reboots are done automatically at
MS's discretion when on a wired network.

Is it true that these upgrades and reboots will wait until the PC is idle?

If yes, would a running batch waiting in a TIMEOUT be considered idle?





It's an insanely horrible process.

Though you have a limited amount of control in postponing a reboot,
Windows will happily reboot right in the middle of a job.


I have a Win10 machine setup merely for testing...the other day I left
the house as an update had started and when I got home the machine had
just completely shut itself off...with no direction from me to do so.

On Fri, 18 Mar 2016 13:29:19 -0500, philo wrote:

On 03/18/2016 12:25 PM, Zaidy036 wrote:
With Win 10 HOME upgrades and required reboots are done automatically at
MS's discretion when on a wired network.

Is it true that these upgrades and reboots will wait until the PC is idle?

If yes, would a running batch waiting in a TIMEOUT be considered idle?





It's an insanely horrible process.

Though you have a limited amount of control in postponing a reboot,
Windows will happily reboot right in the middle of a job.


I have a Win10 machine setup merely for testing...the other day I left
the house as an update had started and when I got home the machine had
just completely shut itself off...with no direction from me to do so.

I routinely have documents open for 4-6 weeks at a time, making running
changes throughout each day. I save and close them when I do my monthly
(also 4-6 weeks) reboot. It would suck if the computer would shut down or
reboot without permission.

I have multiple reasons not to move to Win 10, but that's one of the bigger
ones.

On 03/18/2016 02:00 PM, Char Jackson wrote:
On Fri, 18 Mar 2016 13:29:19 -0500, philo wrote:

On 03/18/2016 12:25 PM, Zaidy036 wrote:
With Win 10 HOME upgrades and required reboots are done automatically at
MS's discretion when on a wired network.

Is it true that these upgrades and reboots will wait until the PC is idle?

If yes, would a running batch waiting in a TIMEOUT be considered idle?





It's an insanely horrible process.

Though you have a limited amount of control in postponing a reboot,
Windows will happily reboot right in the middle of a job.


I have a Win10 machine setup merely for testing...the other day I left
the house as an update had started and when I got home the machine had
just completely shut itself off...with no direction from me to do so.

I routinely have documents open for 4-6 weeks at a time, making running
changes throughout each day. I save and close them when I do my monthly
(also 4-6 weeks) reboot. It would suck if the computer would shut down or
reboot without permission.

I have multiple reasons not to move to Win 10, but that's one of the bigger
ones.





I found this:


Kind of an insane way to do things but really the only thing sensible to do


http://www.thewindowsclub.com/turn-o...-in-windows-10



Normally I update Windows *only* when I have absolutely nothing else to
do. My machines may go months at a time with no updates.

On 03/18/2016 02:58 PM, Ken1943 wrote:


Normally I update Windows *only* when I have absolutely nothing else to
do. My machines may go months at a time with no updates.

MS will probably find a way to screw that method also.

The only way, I see, is to disconnect from the internet. Bet there are
plenty of people doing that if they got "got" in the first place.

I don't have a problem with second tuesday updates as I can check for
new updates around Noon time. It's just the in between ones that mess
my routine up.


Ken1943




Next time I turn on my Win10 machine I may fool with that and see what
happens.

On 18/03/2016 17:25, Zaidy036 wrote:
With Win 10 HOME upgrades and required reboots are done automatically
at MS's discretion when on a wired network.

Is it true that these upgrades and reboots will wait until the PC is
idle?

If yes, would a running batch waiting in a TIMEOUT be considered idle?


Please ignore all the muppets who have replied.

I have seen no reboots yet on my 5 difernet machines. If at all, I
reboot my machine at my own choosing.

What you could do is to block all automatic Windows updates from the
Services APP. This is simple and every month you can download a big fat
file called "Cumulative update for Windows 10"

It is a catalog file and it will download and update your machine at
your own good will. You can then reboot the machine after the update is
finished. Of course, I am assuming you are interested in monthly
updates and so this is the best way I can think of. Windows 10 is here
and unless you are in your 80s and likely to die by the end of this
year, you should get hang of Windows 10 and I see it no different from
Windows 7 and/or Windows 8.1 (or even Windows XP which we used in the
past). It only requires some willingness and interest from the users
point of view to learn new things in life. Learning should be a fun
thing and should never be a bore!. Me thinks so. I like to learn new
things all the time. I have almost mastered C++, C#, SQL, Delphi,
Javascript & PHP. Of course, I am hooked into Microsoft's ASP/MVC
methodology!! It is wonderful and there is no need to use PHP again.

Office applications can be updated from within the applications. See
this pictu



Office Updates http://s28.postimg.org/pice5udt9/2016_03_18_2126.png




--

1. /*This post contains rich text (HTML). if you don't like it then you
can kill-filter the poster without crying like a small baby.*/
2. /*This message is best read in Mozilla Thunderbird as it uses 21st
century technology.*/

On 3/18/2016 3:24 PM, philo wrote:
On 03/18/2016 02:00 PM, Char Jackson wrote:
On Fri, 18 Mar 2016 13:29:19 -0500, philo wrote:

On 03/18/2016 12:25 PM, Zaidy036 wrote:
With Win 10 HOME upgrades and required reboots are done
automatically at
MS's discretion when on a wired network.

Is it true that these upgrades and reboots will wait until the PC is
idle?

If yes, would a running batch waiting in a TIMEOUT be considered idle?


snip


http://www.thewindowsclub.com/turn-o...-in-windows-10

Normally I update Windows *only* when I have absolutely nothing else to
do. My machines may go months at a time with no updates.

I have a laptop with win 10 Home and it gets 2 or 3 file updates every
day at first power up.

I started this topic because my current Win7 Home desktop runs an
unattended batch at 12:45 AM every morning. It does various house
keeping tasks, data backups, and then 6 days a week a/v scans. On the
7th day it makes an incremental image. Total time every night is 4 to 6
hours and the first thing I do is review the logs to check for problems.

If upgrades or reboots were to occur during the batch run I loose that
nights results, or worse, maybe have a corrupted system requiring an
image install.

Thanks for the above URL. If it is correct the following commands should
solve the problem:

At the start of the batch:
SC STOP "wuauserv" NUL
SC CONFIG "wuauserv" START=DISABLED NUL
At the end of the batch:
SC CONFIG "wuauserv" START=AUTO NUL
SC START "wuauserv" NUL

The START commands should not be required except as a "belts &
suspenders" approach.

On 3/18/2016 5:44 PM, Zaidy036 wrote:
On 3/18/2016 3:24 PM, philo wrote:
On 03/18/2016 02:00 PM, Char Jackson wrote:
On Fri, 18 Mar 2016 13:29:19 -0500, philo wrote:

On 03/18/2016 12:25 PM, Zaidy036 wrote:
With Win 10 HOME upgrades and required reboots are done
automatically at
MS's discretion when on a wired network.

Is it true that these upgrades and reboots will wait until the PC is
idle?

If yes, would a running batch waiting in a TIMEOUT be considered idle?


snip


http://www.thewindowsclub.com/turn-o...-in-windows-10

Normally I update Windows *only* when I have absolutely nothing else to
do. My machines may go months at a time with no updates.

I have a laptop with win 10 Home and it gets 2 or 3 file updates every
day at first power up.

I started this topic because my current Win7 Home desktop runs an
unattended batch at 12:45 AM every morning. It does various house
keeping tasks, data backups, and then 6 days a week a/v scans. On the
7th day it makes an incremental image. Total time every night is 4 to 6
hours and the first thing I do is review the logs to check for problems.

If upgrades or reboots were to occur during the batch run I loose that
nights results, or worse, maybe have a corrupted system requiring an
image install.

Thanks for the above URL. If it is correct the following commands should
solve the problem:

At the start of the batch:
SC STOP "wuauserv" NUL
SC CONFIG "wuauserv" START=DISABLED NUL
At the end of the batch:
SC CONFIG "wuauserv" START=AUTO NUL
SC START "wuauserv" NUL

The START commands should not be required except as a "belts &
suspenders" approach.

Just tried the CMDs on my laptop and one must use NET instead of SC and
the service name is "Windows Update". Also since it is Wi-Fi only and
set to "Metered Connection" the service is configured START=Manual

The proper commands a
NET STOP "Windows Update" NUL

NET START "Windows Update" NUL

On 03/18/2016 05:12 PM, Zaidy036 wrote:
On 3/18/2016 5:44 PM, Zaidy036 wrote:
On 3/18/2016 3:24 PM, philo wrote:
On 03/18/2016 02:00 PM, Char Jackson wrote:
On Fri, 18 Mar 2016 13:29:19 -0500, philo wrote:

On 03/18/2016 12:25 PM, Zaidy036 wrote:
With Win 10 HOME upgrades and required reboots are done
automatically at
MS's discretion when on a wired network.

Is it true that these upgrades and reboots will wait until the PC is
idle?

If yes, would a running batch waiting in a TIMEOUT be considered
idle?


snip


http://www.thewindowsclub.com/turn-o...-in-windows-10

Normally I update Windows *only* when I have absolutely nothing else to
do. My machines may go months at a time with no updates.

I have a laptop with win 10 Home and it gets 2 or 3 file updates every
day at first power up.

I started this topic because my current Win7 Home desktop runs an
unattended batch at 12:45 AM every morning. It does various house
keeping tasks, data backups, and then 6 days a week a/v scans. On the
7th day it makes an incremental image. Total time every night is 4 to 6
hours and the first thing I do is review the logs to check for problems.

If upgrades or reboots were to occur during the batch run I loose that
nights results, or worse, maybe have a corrupted system requiring an
image install.

Thanks for the above URL. If it is correct the following commands should
solve the problem:

At the start of the batch:
SC STOP "wuauserv" NUL
SC CONFIG "wuauserv" START=DISABLED NUL
At the end of the batch:
SC CONFIG "wuauserv" START=AUTO NUL
SC START "wuauserv" NUL

The START commands should not be required except as a "belts &
suspenders" approach.

Just tried the CMDs on my laptop and one must use NET instead of SC and
the service name is "Windows Update". Also since it is Wi-Fi only and
set to "Metered Connection" the service is configured START=Manual

The proper commands a
NET STOP "Windows Update" NUL

NET START "Windows Update" NUL




How horrible that MS does not have a simple setting!

Zaidy036 wrote:
On 3/18/2016 5:44 PM, Zaidy036 wrote:
On 3/18/2016 3:24 PM, philo wrote:
On 03/18/2016 02:00 PM, Char Jackson wrote:
On Fri, 18 Mar 2016 13:29:19 -0500, philo wrote:

On 03/18/2016 12:25 PM, Zaidy036 wrote:
With Win 10 HOME upgrades and required reboots are done
automatically at
MS's discretion when on a wired network.

Is it true that these upgrades and reboots will wait until the PC is
idle?

If yes, would a running batch waiting in a TIMEOUT be considered
idle?


snip


http://www.thewindowsclub.com/turn-o...-in-windows-10

Normally I update Windows *only* when I have absolutely nothing else to
do. My machines may go months at a time with no updates.

I have a laptop with win 10 Home and it gets 2 or 3 file updates every
day at first power up.

I started this topic because my current Win7 Home desktop runs an
unattended batch at 12:45 AM every morning. It does various house
keeping tasks, data backups, and then 6 days a week a/v scans. On the
7th day it makes an incremental image. Total time every night is 4 to 6
hours and the first thing I do is review the logs to check for problems.

If upgrades or reboots were to occur during the batch run I loose that
nights results, or worse, maybe have a corrupted system requiring an
image install.

Thanks for the above URL. If it is correct the following commands should
solve the problem:

At the start of the batch:
SC STOP "wuauserv" NUL
SC CONFIG "wuauserv" START=DISABLED NUL
At the end of the batch:
SC CONFIG "wuauserv" START=AUTO NUL
SC START "wuauserv" NUL

The START commands should not be required except as a "belts &
suspenders" approach.

Just tried the CMDs on my laptop and one must use NET instead of SC and
the service name is "Windows Update". Also since it is Wi-Fi only and
set to "Metered Connection" the service is configured START=Manual

The proper commands a
NET STOP "Windows Update" NUL

NET START "Windows Update" NUL

And before you start celebrating too soon, Windows Update
is now controlled by Update Orchestrator. That's something
they added, which puts a bunch of stuff in Task Scheduler.

Display name: Update Orchestrator Service
Service name: UsoSvc
Type: share

http://answers.microsoft.com/en-us/w...0436a58?auth=1

When Win10 boots, maybe 60 seconds after the
desktop appears, you might see a black Command Prompt
window appear and disappear. And that's UsoSvc being
started. Or something related to it. Possibly, it starts
itself using a Task Scheduler entry. (It could be
they used a schtasks to load a script into the
Task Scheduler, and the clumsy Command Prompt window
is a side effect.)

So if you thought that killing wuauserv, that it's the
end of the story, it's not. Like a malware, it doesn't
have to keep running, if it keeps shoving something
into the Task Scheduler.

First of all, using the Services control panel, you'd want
to modify wuauserv recovery policies, so it won't restart
on its own. Stopping wuauserv, might be considered a
"failure", after which the service will be restarted.

But the usosvc could also have loaded things into
the Task Scheduler, to restart wuauserv. I haven't
had a look at it, but you should check your system
to see what hides in there. For example, any time
the usosvc runs, it might look over and check
its "buddy" wuauserv is running, and then issue its
own start command. The recovery policy you see in
Services, doesn't prevent some other service from
kicking the tires.

The possibilities are endless. As in "malware endless".

Paul

On 3/18/2016 7:16 PM, Paul wrote:

snip

Just tried the CMDs on my laptop and one must use NET instead of SC
and the service name is "Windows Update". Also since it is Wi-Fi only
and set to "Metered Connection" the service is configured START=Manual

The proper commands a
NET STOP "Windows Update" NUL

NET START "Windows Update" NUL

And before you start celebrating too soon, Windows Update
is now controlled by Update Orchestrator. That's something
they added, which puts a bunch of stuff in Task Scheduler.

Display name: Update Orchestrator Service
Service name: UsoSvc
Type: share

http://answers.microsoft.com/en-us/w...0436a58?auth=1


When Win10 boots, maybe 60 seconds after the
desktop appears, you might see a black Command Prompt
window appear and disappear. And that's UsoSvc being
started. Or something related to it. Possibly, it starts
itself using a Task Scheduler entry. (It could be
they used a schtasks to load a script into the
Task Scheduler, and the clumsy Command Prompt window
is a side effect.)

So if you thought that killing wuauserv, that it's the
end of the story, it's not. Like a malware, it doesn't
have to keep running, if it keeps shoving something
into the Task Scheduler.

First of all, using the Services control panel, you'd want
to modify wuauserv recovery policies, so it won't restart
on its own. Stopping wuauserv, might be considered a
"failure", after which the service will be restarted.

But the usosvc could also have loaded things into
the Task Scheduler, to restart wuauserv. I haven't
had a look at it, but you should check your system
to see what hides in there. For example, any time
the usosvc runs, it might look over and check
its "buddy" wuauserv is running, and then issue its
own start command. The recovery policy you see in
Services, doesn't prevent some other service from
kicking the tires.

The possibilities are endless. As in "malware endless".

Paul

It does seem to be getting more complicated!

Because my laptop is Wi-Fi set as "metered connection" the following are
set to Manual:
"Update Orchestrator Service" AKA "UsoSvc"
"Windows Update" AKA "wuauserv"

For a wired desktop batch the following seems a good start but may require
NET STOP both and then SC CONFIG both
Reverse order of "Windows Update" and "Update Orchestrator Service"

NET STOP "Windows Update" NUL
SC CONFIG wuauserv START= Disabled NUL
NET STOP "Update Orchestrator Service" NUL
SC CONFIG UsoSvc START= Disabled NUL
....[main part of batch]...
SC CONFIG UsoSvc START= Auto NUL
NET START "Update Orchestrator Service" NUL
SC CONFIG wuauserv START= Auto
NET START "Windows Update" NUL

In article , Zaidy036 wrote:
On 3/18/2016 7:16 PM, Paul wrote:

snip

Just tried the CMDs on my laptop and one must use NET instead of SC
and the service name is "Windows Update". Also since it is Wi-Fi only
and set to "Metered Connection" the service is configured START=Manual

[ ... ]

And before you start celebrating too soon, Windows Update
is now controlled by Update Orchestrator. That's something
they added, which puts a bunch of stuff in Task Scheduler.

Display name: Update Orchestrator Service
Service name: UsoSvc
Type: share


http://answers.microsoft.com/en-us/w...0436a58?auth=1


When Win10 boots, maybe 60 seconds after the
desktop appears, you might see a black Command Prompt
window appear and disappear. And that's UsoSvc being
started. Or something related to it. Possibly, it starts
itself using a Task Scheduler entry. (It could be
they used a schtasks to load a script into the
Task Scheduler, and the clumsy Command Prompt window
is a side effect.)

So if you thought that killing wuauserv, that it's the
end of the story, it's not. Like a malware, it doesn't
have to keep running, if it keeps shoving something
into the Task Scheduler.
[ ... ]

The possibilities are endless. As in "malware endless".

Paul

It does seem to be getting more complicated!


[ ... ]

Very much more; check here to see how pervasive the registry settings
are;

http://www.theregister.co.uk/2016/03...x_vs_humanity/

Malware is an apt comparison. At this point, I'm not installing Win10 or
enabling any automatic updating.


Gary

On Fri, 18 Mar 2016 13:25:02 -0400, Zaidy036 wrote
in

Is it true that these upgrades and reboots will wait until the PC is idle?

No.
--
Web based forums are like subscribing to 10 different newspapers
and having to visit 10 different news stands to pickup each one.
Email list-server groups and USENET are like having all of those
newspapers delivered to your door every morning.

On Fri, 18 Mar 2016 14:24:52 -0500, philo wrote in


Normally I update Windows *only* when I have absolutely nothing else to
do. My machines may go months at a time with no updates.

My WinXPproSP3 machine has gone for 9 years without an update or
problem.
--
Web based forums are like subscribing to 10 different newspapers
and having to visit 10 different news stands to pickup each one.
Email list-server groups and USENET are like having all of those
newspapers delivered to your door every morning.

On Fri, 18 Mar 2016 13:58:31 -0600, Ken1943 wrote
in



Normally I update Windows *only* when I have absolutely nothing else to
do. My machines may go months at a time with no updates.

MS will probably find a way to screw that method also.

The only way, I see, is to disconnect from the internet. Bet there are
plenty of people doing that if they got "got" in the first place.

I don't have a problem with second tuesday updates as I can check for
new updates around Noon time. It's just the in between ones that mess
my routine up.

Take a look at gwx control panel to stop Win10 updates
http://blog.ultimateoutsider.com/201...ly-remove.html
--
Web based forums are like subscribing to 10 different newspapers
and having to visit 10 different news stands to pickup each one.
Email list-server groups and USENET are like having all of those
newspapers delivered to your door every morning.