What is an effective way to tun off Windows 10 updates until YOU want them back on?

On 4/3/2018 9:45 AM, Maurice wrote:
On Mon, 26 Mar 2018 11:37:29 -0700, mike wrote:

The elephant in the room is, "what happens when you actually want to
install an update?"

Awaiting delivery of a desktop with W10 Pro installed, I've learned it's
level as
pre-installed on it is "the 1709 deployment".

Is there a way I can find out in advance how many more updates I am
likely to be
landed with when I first start it up?

Ideally, I would delay until finished for the day and then hand it over
to the
Windows Update machinery, though I really don't know if it lends itself
to
unattended updating or whether the user has to be be sitting there
answering
questions at intervals...

I have no idea how often, if ever, the DVD for a major upgrade like 1709
gets updated.
From my experience, a fresh DVD made from mediacreationtool
about a week after release still results in hundreds of megabytes
of additional updates immediately after the update is applied.

Things change rapidly, but I believe you can use the "pause updates"
function in the windows setup/update/advanced menu. But do it before
you let it connect to the internet.


Whether you have to watch it update varies. My experience is that it will
hang at a couple of places. When it hangs waiting for you to authorize
a reboot, you'll have a long delay as the first reboot configures things.

The safest strategy is to pretend that you're getting it delivered
tomorrow and just let it waste the day updating itself. Keep using
whatever you have for the first day. Depending on your apps and
peripheral hardware, you may have a lot of fun in store.

Don't decommission your old machine until a week or so after you think
you're happy with your new machine. Stock up on booze and anti-anxiety
medications. You may need both.

Maurice wrote:
On Mon, 26 Mar 2018 11:37:29 -0700, mike wrote:

The elephant in the room is, "what happens when you actually want to
install an update?"

Awaiting delivery of a desktop with W10 Pro installed, I've learned it's
level as
pre-installed on it is "the 1709 deployment".

Is there a way I can find out in advance how many more updates I am
likely to be
landed with when I first start it up?

Ideally, I would delay until finished for the day and then hand it over
to the
Windows Update machinery, though I really don't know if it lends itself
to
unattended updating or whether the user has to be be sitting there
answering
questions at intervals...


If it arrives with 1709, it might be unpatched, and then
the Windows Update can apply one or two Cumulatives to it,
to bring it up to date. It will also receive a Windows Defender update (~100MB),
a copy of MSRT perhaps (~100MB), a load of App Cruft (unknown and
not logged), a copy of the latest Flash plugin for IE11 and MSEdge.

Really, 1GB of data downloads ought to handle it :-)

Hope you're not on dialup :-)

*******

In Cortana, type "winver"

16299.334

The first number is the major release, while the second
number is the patch level. The .334 arrived not long ago,
and it would have a KB number associated with it.

If you're feeling some sort of emergency situation, then
you can download some of these things before your Windows
box arrives and install them yourself. But I don't
think that's going to help all that much, in terms
of "nuisance". For example, if it says the .334 .msu file
you're offering it is "not appropriate", the OS may be in need
of a small Servicing Stack update first, after which the
..334 becomes appropriate. While you can "rush" the process,
there might not be sufficient tools available to completely
out-guess the update process. (MBSA can be used on the
other OSes, to map out the missing updates.)

But I have whipped in updates in that fashion before,
in VM environments, to speed up the update process and
make the VM quiet down. Some years, this approach goes
better than others. The Spectre/Meltdown may contribute
to a few surprises if you're trying to force the updates
in currently.

*******

Another way to prepare for a computer arrival, might be
wsusoffline, as this appears to have some Win10 capability.
What that does, is look at the available updates on the MS
server, and download them straight from Microsoft. You can
run the update group in there, to update a computer. It
functions as a kind of "cache" of updates.

http://download.wsusoffline.net/

"...Replaced superseded servicing stack update === example of a
for Windows 10 Version 1709 kb4074608" small blocker

But with the Cumulative update scheme of Windows 10, I'm
not sure this is really going to give you much of an edge.
Like, if you download 5GB of stuff, and only install 1GB
of stuff, that's not very efficient.

Paul

"Maurice" wrote in message news
The elephant in the room is, "what happens when you actually want to
install an update?"

Awaiting delivery of a desktop with W10 Pro installed, I've learned it's
level as pre-installed on it is "the 1709 deployment".

Is there a way I can find out in advance how many more updates I am
likely to be landed with when I first start it up?

Typically new devices unless the OEM updated their 1709 images deployed on
new devices, would have 1709 RTM(Build 16299.15 o 16299.19). The current
released updated 1709 version is 16299.334(March 2018)

To arrive at 16299.334 Windows Update would install one or two pre-x.334
cumulative updates, one to three Servicing Stack Updates(SSU), Flash Update,
MSRT, and a Windows Defender Update, and then x.334 update
- Total 9 max, 6 minimum.

One can minimize the total Windows cumulative and stack updates by
downloading them from the Catalog and installing manually. If following this
route, install the Jan and March SSU prior to installing Cumulative
Updates(Jan, and Mar).



--
....w¡ñ§±¤ñ
msft mvp 2007-2016, insider mvp 2016-2018

On Tue, 03 Apr 2018 12:28:10 -0700, mike wrote:

just let it waste the day updating itself. Keep using whatever you have
for the first day

Will do that, and will be using current working installtion for as long
as it
takes to transfer my routine work over to new PC, e.g. a week or two. No
hurry.

Many thanks for all replies! Much appreiated...

--
/\/\aurice
(Replace "nomail.afraid" by "bcs" to reply by email)