1903 finally

MS has bugged me forever to upgrade. I was 2 levels behind. The
update process failed time after time. I have little interest in the
new features, I just want the most current security environment.

I tried the update again. I put it on a USB stick and ran Setup
under an admin id (I'd just run it under mine before, which supposedly
has admin rights).

The update succeded. Wizard Paul had mentioned the fact in some recent
post that you can hit ctrl-alt-del and open the Task Manager
while the update is running. I did, it was interesting to
watch.

Jason wrote:
MS has bugged me forever to upgrade. I was 2 levels behind. The
update process failed time after time. I have little interest in the
new features, I just want the most current security environment.

I tried the update again. I put it on a USB stick and ran Setup
under an admin id (I'd just run it under mine before, which supposedly
has admin rights).

The update succeded. Wizard Paul had mentioned the fact in some recent
post that you can hit ctrl-alt-del and open the Task Manager
while the update is running. I did, it was interesting to
watch.


I'm surprised you didn't get the message I got, about
"this install is blocked because we have detected a USB stick" :-)

I had to switch over to a DVD I'd already burned, and it
didn't belch out any more error/warnings stuff.

I watch these Upgrade Installs like a hawk, because
I've caught the installer in a "lull", taking a "snooze",
and on my dime. Then I have to dream up some slapping-around
techniques, to try to get the software adrenalin flowing again.
(You can try disabling real-time Windows Defender and
pause the Search Indexer. Superfetch service was something
you could turn off, if the Win10 version you upgrade from
is old enough. It's possible Superfetch is gone now.)

What boggles my mind, is how the install seems to be mostly
CPU limited, when you would expect an "install" to be disk
limited somehow. I wonder how fast of a CPU you need, before
the disk is actually the slowest part.

Paul

On 7/3/2019 12:30 AM, Jason wrote:
The update succeded. Wizard Paul had mentioned the fact in some recent
post that you can hit ctrl-alt-del and open the Task Manager
while the update is running. I did, it was interesting to
watch.
That is the way I monitor the progress of all updates and installs. It
is the best way to monitor the progress of an update

--
Judge your ancestors by how well they met their standards not yours.
They did not know your standards, so could not try to meet them.

Keith Nuttle wrote:
On 7/3/2019 12:30 AM, Jason wrote:
The update succeded. Wizard Paul had mentioned the fact in some recent
post that you can hit ctrl-alt-del and open the Task Manager
while the update is running. I did, it was interesting to
watch.
That is the way I monitor the progress of all updates and installs. It
is the best way to monitor the progress of an update


When the screen is covered by blue during the start of the
install, you can use control-alt-delete to bring back the
Task Bar, and stay in control of the machine during the
file copy phase. That's the point of control-alt-delete
at that point in time, is to point out that the "blue cover"
during that phase isn't absolute.

By watching the machine, if something is "competing" with the
install, you can do something about it. With the Task Bar visible,
you can get to Control Panels and "pause" the Indexing thing.
Or using the security icon, switch off Windows Defender
real time (if you forgot to do that before the install started).

Control-alt-delete would be a mistake during the "juggling balls"
reboot phases. That might interrupt some process, rather than
achieve "observer status". I've never tried that to see
whether it would tip over, with too much prompting.

The most irritating part, is watching an activity like this,
and see close to zero CPU usage, no disk, and you're wondering
why it isn't working hard to finish the install. There are
still some performance puzzles. I expect to see the disk light
stay real busy when an install is happening, no coffee breaks
or the like.

Paul

In article ,
lid says...
What boggles my mind, is how the install seems to be mostly
CPU limited, when you would expect an "install" to be disk
limited somehow. I wonder how fast of a CPU you need, before
the disk is actually the slowest part.

I saw what appeared to be slack time often throughout
the process, but cpu utilization never exceeded about
20%.

I had to sit through the whole process because there
have been issues during installations when the system
restarted and would get stuck. I found from the initial
Win 10 installation a few years ago that during restart I
could kill the power during the BIOS startup. Turning
the machine back on worked, and the installation
continued.

In article ,
lid says...
....

By watching the machine, if something is "competing" with the
install, you can do something about it. With the Task Bar visible,
you can get to Control Panels and "pause" the Indexing thing.
Or using the security icon, switch off Windows Defender
real time (if you forgot to do that before the install started).

I paused the Indexing process a few times and turned off
Defender.


The most irritating part, is watching an activity like this,
and see close to zero CPU usage, no disk, and you're wondering
why it isn't working hard to finish the install.

Amen.

In article -
september.org, says...

MS has bugged me forever to upgrade. I was 2 levels behind. The
update process failed time after time. I have little interest in the
new features, I just want the most current security environment.

I tried the update again. I put it on a USB stick and ran Setup
under an admin id (I'd just run it under mine before, which supposedly
has admin rights).

The update succeded. Wizard Paul had mentioned the fact in some recent
post that you can hit ctrl-alt-del and open the Task Manager
while the update is running. I did, it was interesting to
watch.

The laptop seems fine a day later.

In light of that success, I did the same to my years-old
deskside machine. Per Paul's suggestion I was able to
slightly assuage the boredome by watching Task Manager...

So, two down, one to go. My wife's Dell is only a year
old and so I don't expect the sorts of issues I ran into
with my antiques.

Thanks, Paul!

On 2019-07-03, Jason wrote:
MS has bugged me forever to upgrade. I was 2 levels behind. The
update process failed time after time. I have little interest in the
new features, I just want the most current security environment.

I tried the update again. I put it on a USB stick and ran Setup
under an admin id (I'd just run it under mine before, which supposedly
has admin rights).

The update succeded. Wizard Paul had mentioned the fact in some recent
post that you can hit ctrl-alt-del and open the Task Manager
while the update is running. I did, it was interesting to
watch.


I got my 1903 on D-day; subsequently, I have received several
'cumalative' updates.

The 'interesting' part is that when I booted up my computer in the
morning on 7-1, I got a screen msg before the login with the welcome
msg saying 'welcome to the May 2019' update! Don't know whose
calander is messed up.

On 7/3/2019 8:00 AM, Paul wrote:
Keith Nuttle wrote:
On 7/3/2019 12:30 AM, Jason wrote:
The update succeded. Wizard Paul had mentioned the fact in some recent
post that you can hit ctrl-alt-del and open the Task Manager
while the update is running. I did, it was interesting to
watch.
That is the way I monitor the progress of all updates and installs.
It is the best way to monitor the progress of an update


When the screen is covered by blue during the start of the
install, you can use control-alt-delete to bring back the
Task Bar, and stay in control of the machine during the
file copy phase. That's the point of control-alt-delete
at that point in time, is to point out that the "blue cover"
during that phase isn't absolute.

By watching the machine, if something is "competing" with the
install, you can do something about it. With the Task Bar visible,
you can get to Control Panels and "pause" the Indexing thing.
Or using the security icon, switch off Windows Defender
real time (if you forgot to do that before the install started).

Control-alt-delete would be a mistake during the "juggling balls"
reboot phases. That might interrupt some process, rather than
achieve "observer status". I've never tried that to see
whether it would tip over, with too much prompting.

The most irritating part, is watching an activity like this,
and see close to zero CPU usage, no disk, and you're wondering
why it isn't working hard to finish the install. There are
still some performance puzzles. I expect to see the disk light
stay real busy when an install is happening, no coffee breaks
or the like.

Â*Â* Paul
I find it interesting to watch interaction of the graphs CPU, Memory,
Disk, and WIFI. Even when the machine appears to be taking a break,
most of the time, there is something happening in one of the graphs.

--
Judge your ancestors by how well they met their standards not yours.
They did not know your standards, so could not try to meet them.

In article ,
says...
Even when the machine appears to be taking a break,
most of the time, there is something happening in one of the graphs.

That's what I noticed. It just seemed that it was all
rather leisurely! I also noticed that downloads (updates,
I presume) noodled along at a rather slow pace - on the
order of 1-5 MB/s whereas downloading the image for use
with the Media Builder typically ran faster than 100 MB/s+

In article -
september.org, says...

In article ,
says...
Even when the machine appears to be taking a break,
most of the time, there is something happening in one of the graphs.

That's what I noticed. It just seemed that it was all
rather leisurely! I also noticed that downloads (updates,
I presume) noodled along at a rather slow pace - on the
order of 1-5 MB/s whereas downloading the image for use
with the Media Builder typically ran faster than 100 MB/s+

Three upgrades in a single day fried my brain. Change
MB/s to Mb/s everywhere. Sigh.

Jason wrote:
In article -
september.org, says...
In article ,
says...
Even when the machine appears to be taking a break,
most of the time, there is something happening in one of the graphs.

That's what I noticed. It just seemed that it was all
rather leisurely! I also noticed that downloads (updates,
I presume) noodled along at a rather slow pace - on the
order of 1-5 MB/s whereas downloading the image for use
with the Media Builder typically ran faster than 100 MB/s+

Three upgrades in a single day fried my brain. Change
MB/s to Mb/s everywhere. Sigh.

An OS Upgrade consists of "a thousand or two" packages.
The DoSVC can open parallel connections and process as
many as 20 packages in parallel. It opens so many
connections in fact, the round robin policy of
your router will ensure other computers on the
same LAN segment will almost "starve" because
of the greedy behavior of that one Win10 machine.

Don't ask me what happens when multiple Win10 machines
attack the same router at the same time. I would expect
anyone working on those computers, to take the day off.

There are GPEdit controls for modifying that behavior.
I felt compelled to see if I could modify the behavior
for the better.

Even if you reduce DoSvc to around four connections,
it can still do an OS Upgrade. What it does in those
cases, is downloads a single 2.5GB "blob" of some sort,
so the upgrade strategy changes if the installer notices
that it's not getting the "traction" it deserves. You
can still easily max a residential Internet service with
the one connection. I waited *weeks* for that test case
to run all by itself. I couldn't accelerate it and
had to wait until the machine got the usual servicing
stack update as a precursor. (You notice after a
Windows Update and reboot, that it's packing a
picnic lunch for itself. It requires you to be
attentive to what happens after the reboot happens.)

Paul

On Wed, 03 Jul 2019 00:42:03 -0400, Paul
wrote:

Jason wrote:
MS has bugged me forever to upgrade. I was 2 levels behind. The
update process failed time after time. I have little interest in the
new features, I just want the most current security environment.

I tried the update again. I put it on a USB stick and ran Setup
under an admin id (I'd just run it under mine before, which supposedly
has admin rights).

The update succeded. Wizard Paul had mentioned the fact in some recent
post that you can hit ctrl-alt-del and open the Task Manager
while the update is running. I did, it was interesting to
watch.


I'm surprised you didn't get the message I got, about
"this install is blocked because we have detected a USB stick" :-)

I had to switch over to a DVD I'd already burned, and it
didn't belch out any more error/warnings stuff.

I've just made a clean install from a USB stick. No warnings.

I watch these Upgrade Installs like a hawk, because
I've caught the installer in a "lull", taking a "snooze",
and on my dime. Then I have to dream up some slapping-around
techniques, to try to get the software adrenalin flowing again.
(You can try disabling real-time Windows Defender and
pause the Search Indexer. Superfetch service was something
you could turn off, if the Win10 version you upgrade from
is old enough. It's possible Superfetch is gone now.)

What boggles my mind, is how the install seems to be mostly
CPU limited, when you would expect an "install" to be disk
limited somehow. I wonder how fast of a CPU you need, before
the disk is actually the slowest part.

Paul

Eric Stevens wrote:
On Wed, 03 Jul 2019 00:42:03 -0400, Paul
wrote:

Jason wrote:
MS has bugged me forever to upgrade. I was 2 levels behind. The
update process failed time after time. I have little interest in the
new features, I just want the most current security environment.

I tried the update again. I put it on a USB stick and ran Setup
under an admin id (I'd just run it under mine before, which supposedly
has admin rights).

The update succeded. Wizard Paul had mentioned the fact in some recent
post that you can hit ctrl-alt-del and open the Task Manager
while the update is running. I did, it was interesting to
watch.

I'm surprised you didn't get the message I got, about
"this install is blocked because we have detected a USB stick" :-)

I had to switch over to a DVD I'd already burned, and it
didn't belch out any more error/warnings stuff.

I've just made a clean install from a USB stick. No warnings.

I was doing a 1903 upgrade install at the time, with the network
isolated, so I brought over a USB stick. The purpose of doing that,
was cutting off the 4GB download it was about to do. Beat it to the
punch.

Paul

On 7/3/2019 12:30 PM, Jason wrote:
MS has bugged me forever to upgrade. I was 2 levels behind. The
update process failed time after time. I have little interest in the
new features, I just want the most current security environment.
....
The update succeded. Wizard Paul had mentioned the fact in some recent
post that you can hit ctrl-alt-del and open the Task Manager
while the update is running. I did, it was interesting to
watch.

Is it V1 or V2?

--
@~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!!
/ v \ Simplicity is Beauty!
/( _ )\ May the Force and farces be with you!
^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
¤£Â*ɶU! ¤£¶BÄF! ¤£½ä¿ú! ¤£´©¥æ! ¤£¥´¥æ! ¤£¥´§T! ¤£¦Û±þ! ¤£¨D¯«!
½�¦Ò¼{ºî´© (CSSA):
http://www.swd.gov.hk/tc/index/site_...sub_addressesa