This morning, yet another update

My computer was sleeping overnight. When I woke it up it proved to be
running like glue - very slowly. Task Manager (took about two minutes
to load) didn't show anything out of the way except that Firefox which
I had been trying to load seemed to be running four copies and
occupying +800MB.

I decided to restart: Lo and behold a green screen "Please do not
switch off your computer etc". After several restarts all came back to
life about 10 minutes later. After all that I'm still on 1809 now
build 17763.437. It was 17134.165. This seems to be yet another update
when you don't get an update. I haven't noticed anything different
yet.
--

Regards,

Eric Stevens

On Wed, 10 Apr 2019 15:20:01 +1200, Eric Stevens wrote:

Firefox which
I had been trying to load seemed to be running four copies


Multiple firefox.exe processes is normal for the current Firefox,
like it is with other current browsers Chrome, IE and Edge.


--
Kind regards
Ralph
🦊

On Wed, 10 Apr 2019 19:26:30 +1200, Ralph Fox
wrote:

On Wed, 10 Apr 2019 15:20:01 +1200, Eric Stevens wrote:

Firefox which
I had been trying to load seemed to be running four copies


Multiple firefox.exe processes is normal for the current Firefox,
like it is with other current browsers Chrome, IE and Edge.

But 800 MB?
--

Regards,

Eric Stevens

Eric Stevens wrote:

Ralph Fox wrote:

Multiple firefox.exe processes is normal for the current Firefox,
like it is with other current browsers Chrome, IE and Edge.

But 800 MB?

Pretty normal for it to take 2x to 3x that amount of memory here (with
about 60 tabs open)

On 4/9/19 11:20 PM, Eric Stevens wrote:
My computer was sleeping overnight. When I woke it up it proved to be
running like glue - very slowly. Task Manager (took about two minutes
to load) didn't show anything out of the way except that Firefox which
I had been trying to load seemed to be running four copies and
occupying +800MB.

I decided to restart: Lo and behold a green screen "Please do not
switch off your computer etc". After several restarts all came back to
life about 10 minutes later. After all that I'm still on 1809 now
build 17763.437. It was 17134.165. This seems to be yet another update
when you don't get an update. I haven't noticed anything different
yet.

As much as people try, Microsoft seems to persist in doing updates. I'm
totally taken aback at anyones surprise that on the 2nd Tuesday of the
month, and it's been this way for decades, that @ 10am PST (Redmond
Washington USA) time, updates are released to the wild by Microsoft.

You have one hell of a good chance with Windows 10 of getting an update.
For me, it was just a cumulative update and Adobe fixes, minor crap, but
I could count on it like clockwork.

Al

On 4/10/2019 7:05 AM, Andy Burns wrote:
Eric Stevens wrote:

Ralph Fox wrote:

Multiple firefox.exe processes is normal for the current Firefox,
like it is with other current browsers Chrome, IE and Edge.

But 800 MB?

Pretty normal for it to take 2x to 3x that amount of memory here (with
about 60 tabs open)
I believe that the people who complain about the monthly updates to
their MS subscription would be quite unhappy if they did not get their
monthly updates to their Sport Illustrated subscription.

With both updates, some time is taken from their day because of the update.

--
2018: The year we learn to play the great game of Euchre

Big Al wrote:

I'm totally taken aback at anyones surprise that on the 2nd Tuesday of
the month

Nothing (other than defender A/V updates) since 15th March here

On 10/04/2019 04:20, Eric Stevens wrote:
My computer was sleeping overnight. When I woke it up it proved to be
running like glue - very slowly. Task Manager (took about two minutes
to load) didn't show anything out of the way except that Firefox which
I had been trying to load seemed to be running four copies and
occupying +800MB.

I decided to restart: Lo and behold a green screen "Please do not
switch off your computer etc". After several restarts all came back to
life about 10 minutes later. After all that I'm still on 1809 now
build 17763.437. It was 17134.165. This seems to be yet another update
when you don't get an update. I haven't noticed anything different
yet.


Microsoft Updates always occur on the second Tuesday of each month.

https://en.wikipedia.org/wiki/Patch_Tuesday

I've updated too; I am also on Version 1809 and OS Build 17763.437.

All seems to be working just fine.

--
David B.
Devon, UK

Eric Stevens said:

I decided to restart: Lo and behold a green screen "Please do not
switch off your computer etc".

Green screen? I didn't know they had a green screen.
I've only seen light blue lately (lighter than BSOD).

Here's mine this morning still cranking away for a long time.
https://www.picoolio.net/image/dgvV

It's light blue. Not green.
Since my boot is too slow, maybe this will fix it (but probably not).

PT French wrote:
Eric Stevens said:

I decided to restart: Lo and behold a green screen "Please do not
switch off your computer etc".

Green screen? I didn't know they had a green screen.
I've only seen light blue lately (lighter than BSOD).

Here's mine this morning still cranking away for a long time.
https://www.picoolio.net/image/dgvV

It's light blue. Not green.
Since my boot is too slow, maybe this will fix it (but probably not).

Microsoft does use green. On the Insider.

https://betanews.com/2016/12/29/gsod...reen-of-death/

On blue-green screens, some users perceive the color
differently than you do.

I don't think Personalize affects an Update screen, so
there should be better consistency there.

And to answer the question about your slow boot,
no, things hardly resolve on their own. Microsoft
isn't that clever. They "sing an AI song", but
are brutally manual in practical things. There is
nobody sitting at a terminal, working out why your
boot is slow. Even though there may be telemetry
sent to MS with that detail.

And the thing is, even if we reinstalled your OS,
there is no guarantee that the result would be
fast and snappy. Whatever has befallen it, could
happen a second time.

Boot time is partially affected by amount of RAM.
A 64GB machine boots slower than a 2GB RAM machine.

Windows Defender works pretty hard at startup, to
scan critical areas before you're allowed to use it.
And switching to an SSD in place of a hard drive, the
CPU really isn't fast enough typically, to really
speed up a boot process.

The record for boot is in the 5 to 10 second range.
With 10 seconds being the "no cheating" best case.
If you overclock the machine, rip the guts out of it,
you can get it down to 5 seconds.

17763 removed Superfetch, and I think 17134 still had it.
That contributes sometimes, to less I/O available for
the user to speed to completion. Sometimes, on 17134,
I would switch off both Windows Defender and Superfetch,
so the most I/O possible would be available to finish
the update.

But none of these, is your "slow boot problem". A
ten minute delay is way way outside the norm. And
is something we might not have seen before.

I've had some boot-ups, where the screen remains black
for several minutes. These are probably related to updates,
but I don't "count that as a boot time", as a subsequent
boot could be a lot faster and more "logical". If you
consistently see ten minute delays, day after day after day,
then you need to study that to see what could possibly
be wrong with it.

Check your Windows Update in Settings, and the History
tab, just in case the same update is happening over and
over again, and failing each and every time. You should
be seeing the "juggling balls" display though, if an Update
is doing this. That would be a hint, like say, at shutdown
time.

Paul

David in Devon wrote:
On 10/04/2019 04:20, Eric Stevens wrote:
My computer was sleeping overnight. When I woke it up it proved to be
running like glue - very slowly. Task Manager (took about two minutes
to load) didn't show anything out of the way except that Firefox which
I had been trying to load seemed to be running four copies and
occupying +800MB.

I decided to restart: Lo and behold a green screen "Please do not
switch off your computer etc". After several restarts all came back to
life about 10 minutes later. After all that I'm still on 1809 now
build 17763.437. It was 17134.165. This seems to be yet another update
when you don't get an update. I haven't noticed anything different
yet.


Microsoft Updates always occur on the second Tuesday of each month.

https://en.wikipedia.org/wiki/Patch_Tuesday

I've updated too; I am also on Version 1809 and OS Build 17763.437.

All seems to be working just fine.

Unless it is an emergency as an out of bound release.
--
Quote of the Week: "If you're an ant, and you're walking along across
the top of a cup of pudding, you probably have no idea that the only
thing between you and disaster is the strength of that pudding skin."
--Jack Handey from Saturday Night Live
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

On 10/04/2019 21:57, Ant wrote:
David in Devon wrote:
On 10/04/2019 04:20, Eric Stevens wrote:
My computer was sleeping overnight. When I woke it up it proved to be
running like glue - very slowly. Task Manager (took about two minutes
to load) didn't show anything out of the way except that Firefox which
I had been trying to load seemed to be running four copies and
occupying +800MB.

I decided to restart: Lo and behold a green screen "Please do not
switch off your computer etc". After several restarts all came back to
life about 10 minutes later. After all that I'm still on 1809 now
build 17763.437. It was 17134.165. This seems to be yet another update
when you don't get an update. I haven't noticed anything different
yet.


Microsoft Updates always occur on the second Tuesday of each month.

https://en.wikipedia.org/wiki/Patch_Tuesday

I've updated too; I am also on Version 1809 and OS Build 17763.437.

All seems to be working just fine.

Unless it is an emergency as an out of bound release.

I'll concede! :-)

--
David B.
Devon, UK

On Wed, 10 Apr 2019 12:05:33 +0100, Andy Burns
wrote:

Eric Stevens wrote:

Ralph Fox wrote:

Multiple firefox.exe processes is normal for the current Firefox,
like it is with other current browsers Chrome, IE and Edge.

But 800 MB?

Pretty normal for it to take 2x to 3x that amount of memory here (with
about 60 tabs open)

But this wa only the home page (which never actually got to the point
of being visible. Right now I have the same home page fully loaded at
4 process and 576.9 MB.
--

Regards,

Eric Stevens

Eric Stevens wrote:

Right now I have the same home page fully loaded at
4 process and 576.9 MB.

I closed all but two tabs, restarted to upgrade to 66.0.3 my memory
usage is 615MB, but with 7 processes, some add-ons that'll use memory
(uBO and lastpass)

On Wed, 10 Apr 2019 07:39:09 -0400, Big Al wrote
in

As much as people try, Microsoft seems to persist in doing updates. I'm
totally taken aback at anyones surprise that on the 2nd Tuesday of the
month, and it's been this way for decades, that @ 10am PST (Redmond
Washington USA) time, updates are released to the wild by Microsoft.

You have one hell of a good chance with Windows 10 of getting an update.
For me, it was just a cumulative update and Adobe fixes, minor crap, but
I could count on it like clockwork.

Why not just get off the update treadmill?

https://www.oo-software.com/en/shutup10
--
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.