A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » General XP issues or comments
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Update Tuesday



 
 
Thread Tools Display Modes
  #1  
Old May 11th 17, 05:26 AM posted to microsoft.public.windowsxp.general
Ben Myers[_9_]
external usenet poster
 
Posts: 30
Default Update Tuesday

Tuesday's Windows Update took my svchost running wuaserv
up to nearly one hundred percent cpu usage for about three hours.
Wondering if anyone else experienced this.

Ben

Ads
  #2  
Old May 11th 17, 05:44 AM posted to microsoft.public.windowsxp.general
Ant[_2_]
external usenet poster
 
Posts: 554
Default Update Tuesday

Ben Myers wrote:
Tuesday's Windows Update took my svchost running wuaserv
up to nearly one hundred percent cpu usage for about three hours.
Wondering if anyone else experienced this.


This is a common problem for years. Even W7 has this problem. I know in
W7, you need specific KBs to install to avoid them. I don't know about
XP SP3. See
https://www.google.com/search?q=svch...windows+xp+CPU ...

--
Quote of the Week: "Busy as ants hurrying orcs were digging, digging
lines of deep trenches in a huge ring, just out of bowshot from the
walls;" --The Return of the King (book)
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail privately. If credit-
( ) ing, then please kindly use Ant nickname and AQFL URL/link.
  #3  
Old May 11th 17, 05:53 AM posted to microsoft.public.windowsxp.general
Ben Myers[_9_]
external usenet poster
 
Posts: 30
Default Update Tuesday

"Ant" wrote in message ...
Ben Myers wrote:
Tuesday's Windows Update took my svchost running wuaserv
up to nearly one hundred percent cpu usage for about three hours.
Wondering if anyone else experienced this.


This is a common problem for years. Even W7 has this problem. I know in
W7, you need specific KBs to install to avoid them. I don't know about
XP SP3. See
https://www.google.com/search?q=svch...windows+xp+CPU ...

--
Quote of the Week: "Busy as ants hurrying orcs were digging, digging
lines of deep trenches in a huge ring, just out of bowshot from the
walls;" --The Return of the King (book)
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail privately. If credit-
( ) ing, then please kindly use Ant nickname and AQFL URL/link.


Thanks for the advice. It doesn't usually last that long. I was thinking that last
month's update installed something that might have caused it. I've already
downloaded kb2909921. Just wondering if anyone else was affected.

Ben

  #4  
Old May 11th 17, 07:54 AM posted to microsoft.public.windowsxp.general
Mike Isaacs
external usenet poster
 
Posts: 6
Default Update Tuesday

My Win 7 machine said that it had 4 important updates to download before
it shut down on Tuesday, and then33,000+ updates to install before it
restarted yesterday!

In message , Ben Myers
writes
Tuesday's Windows Update took my svchost running wuaserv
up to nearly one hundred percent cpu usage for about three hours.
Wondering if anyone else experienced this.

Ben


--
Mike
  #5  
Old May 11th 17, 08:28 AM posted to microsoft.public.windowsxp.general
Ben Myers[_9_]
external usenet poster
 
Posts: 30
Default Update Tuesday

"Mike Isaacs" wrote in message ...
My Win 7 machine said that it had 4 important updates to download before
it shut down on Tuesday, and then33,000+ updates to install before it
restarted yesterday!

In message , Ben Myers
writes
Tuesday's Windows Update took my svchost running wuaserv
up to nearly one hundred percent cpu usage for about three hours.
Wondering if anyone else experienced this.


Sounds like it might not have been confined to XP.

Ben
  #6  
Old May 11th 17, 11:01 AM posted to microsoft.public.windowsxp.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Update Tuesday

Ben Myers wrote:
"Mike Isaacs" wrote in message ...
My Win 7 machine said that it had 4 important updates to download before
it shut down on Tuesday, and then33,000+ updates to install before it
restarted yesterday!

In message , Ben Myers
writes
Tuesday's Windows Update took my svchost running wuaserv
up to nearly one hundred percent cpu usage for about three hours.
Wondering if anyone else experienced this.


Sounds like it might not have been confined to XP.

Ben


The biggest improvement I see this month, is WinXP
Windows Update no longer works with IE6. You'd have to
install a later version of IE, to hope to have a chance
of it working. AFAIK, IE8 is the last version of IE
you can download for WinXP.

And the looping behavior is "normal". The looping is
under the control of Microsoft from their end, via
the manifest. If the wsusscn2 file is properly
curated, the looping can be reduced to under five
minutes.

As of today, Microsoft still supports WinXP
era stuff, in the form of the POS/WePOS (Point Of Sale)
products, so they're still working on it. I don't
know what the end-date is for that stuff.

Paul
  #7  
Old May 11th 17, 01:45 PM posted to microsoft.public.windowsxp.general
Ben Myers[_9_]
external usenet poster
 
Posts: 30
Default Update Tuesday

"Paul" wrote in message news
Ben Myers wrote:
"Mike Isaacs" wrote in message ...
My Win 7 machine said that it had 4 important updates to download before
it shut down on Tuesday, and then33,000+ updates to install before it
restarted yesterday!

In message , Ben Myers
writes
Tuesday's Windows Update took my svchost running wuaserv
up to nearly one hundred percent cpu usage for about three hours.
Wondering if anyone else experienced this.


Sounds like it might not have been confined to XP.

Ben

The biggest improvement I see this month, is WinXP
Windows Update no longer works with IE6. You'd have to
install a later version of IE, to hope to have a chance
of it working. AFAIK, IE8 is the last version of IE
you can download for WinXP.


I have IE8, but I rarely use it.

And the looping behavior is "normal". The looping is
under the control of Microsoft from their end, via
the manifest. If the wsusscn2 file is properly
curated, the looping can be reduced to under five
minutes.


If you mean "wsusscn2.cab", I can't even find that on my computer.

As of today, Microsoft still supports WinXP
era stuff, in the form of the POS/WePOS (Point Of Sale)
products, so they're still working on it. I don't
know what the end-date is for that stuff.


All I get anymore are Microsoft Office updates and the occasional
malicious software removal tool.
I typically just put up with it every month, but it has never taken three
hours. And it wasn't downloading, just hogging the processor.

Ben
  #8  
Old May 11th 17, 02:26 PM posted to microsoft.public.windowsxp.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Update Tuesday

Ben Myers wrote:
"Paul" wrote in message news
Ben Myers wrote:
"Mike Isaacs" wrote in message ...
My Win 7 machine said that it had 4 important updates to download before
it shut down on Tuesday, and then33,000+ updates to install before it
restarted yesterday!

In message , Ben Myers
writes
Tuesday's Windows Update took my svchost running wuaserv
up to nearly one hundred percent cpu usage for about three hours.
Wondering if anyone else experienced this.
Sounds like it might not have been confined to XP.

Ben

The biggest improvement I see this month, is WinXP
Windows Update no longer works with IE6. You'd have to
install a later version of IE, to hope to have a chance
of it working. AFAIK, IE8 is the last version of IE
you can download for WinXP.


I have IE8, but I rarely use it.

And the looping behavior is "normal". The looping is
under the control of Microsoft from their end, via
the manifest. If the wsusscn2 file is properly
curated, the looping can be reduced to under five
minutes.


If you mean "wsusscn2.cab", I can't even find that on my computer.

As of today, Microsoft still supports WinXP
era stuff, in the form of the POS/WePOS (Point Of Sale)
products, so they're still working on it. I don't
know what the end-date is for that stuff.


All I get anymore are Microsoft Office updates and the occasional
malicious software removal tool.
I typically just put up with it every month, but it has never taken three
hours. And it wasn't downloading, just hogging the processor.

Ben


The manifest is available as one file, or as pieces.

Windows Update doesn't use the whole thing. Presumably
just the WinXP-relevant part is provided. I'm not aware
of any "residue" you can look at on WinXP, to see
what it's consulting. The connection time does not
indicate a long download of stuff. The computation that
wuauserv does, appears to be memory bound, and during
the lengthy looping, you should not be seeing any I/O
related to it.

The wsusscn2.cab file that MBSA 2.3 uses, is the whole thing.
Some of the dates in the file, predate particular OS release
dates, so the time horizon of the content in the file
can be puzzling at times.

Windows Update really should not have been used for
recurring updates. The MRT for example, released
monthly, should never have come through Windows Update.
It could have been installed once (just the one release),
and had its own updater to do monthly scans if needed.
Pouring that into Windows Update is a mistake.

The lengthy calculation that Windows Update does,
works out the "supersedence" of updates. It works
out which updates are irrelevant, and which is the
latest update that covers things. It looks at the
20 or 30 different "Cumulative Updates for Internet Explorer"
apply to your machine, and recognizes it should be
installing the May 2017 one.

There appears to be some way to modify the file manifest
on the server side by Microsoft, as needed. When
Microsoft wanted to put a push on, to have Windows 10
free update delivered through Microsoft Update, it
needed to "clean the plumbing" on Windows 7 machines.
Magically, a month before the end of the free update
interval, suddenly the Windows 7 version of Windows
Update, wasn't spinning in a loop that month. That was
to aid the delivery of the Windows 10 update sitting in
queue. When it suits their purpose, staff at Microsoft
will spend the extra time "bandaiding" the problem.

The delivery vehicle on Win7 and Win8.1 has been changed
over the last few months. Larger update files are now
delivered (multiple updates in one jumbo KB), and the
modifications are supposed to be delivered easier. But
note that really none of the changes to the client agent,
have anything to do with the basic tracking mechanism.
It's been the same for at least the last 15 years. And
it can and will break again, you can be assured of that.
I've even had the Win10 Release install here, screw
up a couple of times, and repeat the same actions
for hours on end, but those could be fixed by resetting
Windows Update and cleaning out SoftwareDistribution by
renaming it to SoftwareDistribution.bak (from some place
where you are allowed to do that).

If you see wuauserv looping, it really should
not come as a surprise... I've managed to
"fix it kinda", on WinXP, Vista (using info from
Wsusoffline site), Win7, Win8.1. The repair lasts
for a month, until the next Patch Tuesday (that's
why it's a "bandaid", and worthless to anyone). I don't
consider my Win10 problems to be comparable to
the others, so it doesn't fit into the same failure
class. But it does respond to some of the standard
repair approaches.

https://www.tenforums.com/tutorials/...dows-10-a.html

Paul
  #9  
Old May 11th 17, 04:31 PM posted to microsoft.public.windowsxp.general
Ben Myers[_9_]
external usenet poster
 
Posts: 30
Default Update Tuesday

"Paul" wrote in message news
Ben Myers wrote:
"Paul" wrote in message news
Ben Myers wrote:
"Mike Isaacs" wrote in message ...
My Win 7 machine said that it had 4 important updates to download before
it shut down on Tuesday, and then33,000+ updates to install before it
restarted yesterday!

In message , Ben Myers
writes
Tuesday's Windows Update took my svchost running wuaserv
up to nearly one hundred percent cpu usage for about three hours.
Wondering if anyone else experienced this.
Sounds like it might not have been confined to XP.

Ben
The biggest improvement I see this month, is WinXP
Windows Update no longer works with IE6. You'd have to
install a later version of IE, to hope to have a chance
of it working. AFAIK, IE8 is the last version of IE
you can download for WinXP.


I have IE8, but I rarely use it.

And the looping behavior is "normal". The looping is
under the control of Microsoft from their end, via
the manifest. If the wsusscn2 file is properly
curated, the looping can be reduced to under five
minutes.


If you mean "wsusscn2.cab", I can't even find that on my computer.

As of today, Microsoft still supports WinXP
era stuff, in the form of the POS/WePOS (Point Of Sale)
products, so they're still working on it. I don't
know what the end-date is for that stuff.


All I get anymore are Microsoft Office updates and the occasional
malicious software removal tool.
I typically just put up with it every month, but it has never taken three
hours. And it wasn't downloading, just hogging the processor.

Ben


The manifest is available as one file, or as pieces.

Windows Update doesn't use the whole thing. Presumably
just the WinXP-relevant part is provided. I'm not aware
of any "residue" you can look at on WinXP, to see
what it's consulting. The connection time does not
indicate a long download of stuff. The computation that
wuauserv does, appears to be memory bound, and during
the lengthy looping, you should not be seeing any I/O
related to it.

The wsusscn2.cab file that MBSA 2.3 uses, is the whole thing.
Some of the dates in the file, predate particular OS release
dates, so the time horizon of the content in the file
can be puzzling at times.


I downloaded the wsusscn2.cab file and it is collection of more .cab
files. The web page seems to indicate that the idea is to modify some
update component so it knows where to find the .cab file.

I actually used the stand-alone updater. When I first installed XP,
I couldn't get Windows Update to work. The stand-alone updater
somehow kicked it into operation.

Windows Update really should not have been used for
recurring updates. The MRT for example, released
monthly, should never have come through Windows Update.
It could have been installed once (just the one release),
and had its own updater to do monthly scans if needed.
Pouring that into Windows Update is a mistake.


The last MRT I got from Windows Update was in August of 2016

The lengthy calculation that Windows Update does,
works out the "supersedence" of updates. It works
out which updates are irrelevant, and which is the
latest update that covers things. It looks at the
20 or 30 different "Cumulative Updates for Internet Explorer"
apply to your machine, and recognizes it should be
installing the May 2017 one.


Sounds like the more updates you already have, the harder it
is for the updater to figure out what you need.

There appears to be some way to modify the file manifest
on the server side by Microsoft, as needed. When
Microsoft wanted to put a push on, to have Windows 10
free update delivered through Microsoft Update, it
needed to "clean the plumbing" on Windows 7 machines.
Magically, a month before the end of the free update
interval, suddenly the Windows 7 version of Windows
Update, wasn't spinning in a loop that month. That was
to aid the delivery of the Windows 10 update sitting in
queue. When it suits their purpose, staff at Microsoft
will spend the extra time "bandaiding" the problem.


I actually tried the Windows 10 preview, but it uses a
relatively new processor instruction that my Pentium 4
doesn't have.

The delivery vehicle on Win7 and Win8.1 has been changed
over the last few months. Larger update files are now
delivered (multiple updates in one jumbo KB), and the
modifications are supposed to be delivered easier. But
note that really none of the changes to the client agent,
have anything to do with the basic tracking mechanism.
It's been the same for at least the last 15 years. And
it can and will break again, you can be assured of that.
I've even had the Win10 Release install here, screw
up a couple of times, and repeat the same actions
for hours on end, but those could be fixed by resetting
Windows Update and cleaning out SoftwareDistribution by
renaming it to SoftwareDistribution.bak (from some place
where you are allowed to do that).

If you see wuauserv looping, it really should
not come as a surprise... I've managed to
"fix it kinda", on WinXP, Vista (using info from
Wsusoffline site), Win7, Win8.1. The repair lasts
for a month, until the next Patch Tuesday (that's
why it's a "bandaid", and worthless to anyone). I don't
consider my Win10 problems to be comparable to
the others, so it doesn't fit into the same failure
class. But it does respond to some of the standard
repair approaches.
https://www.tenforums.com/tutorials/...dows-10-a.html
Paul


I appreciate your input on all this. Good to see that Windows 10
still supports batch files.

Ben

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 10:28 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.