Windows Update 100% CPU usage issue - a NEW twist on an old proble

Being unable to perform any useful work for 2 minutes shortly after I wake up
from hibernation my 2 GHz laptop does not seem acceptable to me, especially
since this problem did not exist previously (i.e. when I had XP SP2)...I
wouldn't call 2 minutes of 100% CPU a "spike"...If at least the offending
process was running in a lower priority !

"PA Bear [MS MVP]" wrote:

> >>> And I noticed the same 100% CPU utilization in svchost (Automatic
> >>> Updates)
> >>> for 1~2 minutes every now and then.
>
> Every now and then is not unusual; prolonged or unending spikes of 100% are
> not.
>

I just ran the following test:
- Disabled Avira AntiVir Guard
- Exited TeaTimer
I then manually went to Windows Update

Result: more than 3 minutes at 100% CPU !

After installation of a couple of Office updates, I then restarted my laptop.
As I am writing this, the fan is again spinning at 100% just like the CPU,
and Process Explorer is already reporting 4:23 minutes of CPU time for
svhost.exe, of which 3:40 min just for wuaueng.dll....

Any suggestions for further t'shooting would be welcome

"benoitm" wrote:

> Being unable to perform any useful work for 2 minutes shortly after I wake up
> from hibernation my 2 GHz laptop does not seem acceptable to me, especially
> since this problem did not exist previously (i.e. when I had XP SP2)...I
> wouldn't call 2 minutes of 100% CPU a "spike"...If at least the offending
> process was running in a lower priority !
>
> "PA Bear [MS MVP]" wrote:
>
> > >>> And I noticed the same 100% CPU utilization in svchost (Automatic
> > >>> Updates)
> > >>> for 1~2 minutes every now and then.
> >
> > Every now and then is not unusual; prolonged or unending spikes of 100% are
> > not.
> >
>

Try these, in order:

• Change your default update source from Microsoft Update to Windows Update:

Go to Microsoft Update | Click on Change Settings in left pane | Scroll to
bottom of page | To Stop Using Microsoft Update | Disable Microsoft Update
software and let me use Windows Update only (check).

With Windows Update as your default, you will need to check in at Office
Update to keep your Office applications fully patched:
http://office.microsoft.com/en-us/do...incatalog.aspx

• Delete or rename SoftwareDistribution folder:

1. Stop the Automatic Updates service:

Start > Run > (type in) services.msc > [OK]
Double-click Automatic Updates > Click on Stop
(Stopping the service will take a moment)

2. Delete %windir%\SoftwareDistribution <=this folder or rename it (e.g.,
SoftwareDistribution.OLD).

NB: The above step will have the consequence of deleting your Update History
at Windows Update.

3. Start the Automatic Updates service:

Start > Run > (type in) services.msc > [OK]
Double-click Automatic Updates > Click on Start
(Starting the service will take a moment)
--
~PA Bear


benoitm wrote:
> I just ran the following test:
> - Disabled Avira AntiVir Guard
> - Exited TeaTimer
> I then manually went to Windows Update
>
> Result: more than 3 minutes at 100% CPU !
>
> After installation of a couple of Office updates, I then restarted my
> laptop. As I am writing this, the fan is again spinning at 100% just like
> the CPU, and Process Explorer is already reporting 4:23 minutes of CPU
> time
> for svhost.exe, of which 3:40 min just for wuaueng.dll....
>
> Any suggestions for further t'shooting would be welcome
>
> "benoitm" wrote:
>
>> Being unable to perform any useful work for 2 minutes shortly after I
>> wake
>> up from hibernation my 2 GHz laptop does not seem acceptable to me,
>> especially since this problem did not exist previously (i.e. when I had
>> XP
>> SP2)...I wouldn't call 2 minutes of 100% CPU a "spike"...If at least the
>> offending process was running in a lower priority !
>>
>> "PA Bear [MS MVP]" wrote:
>>
>>>>>> And I noticed the same 100% CPU utilization in svchost (Automatic
>>>>>> Updates)
>>>>>> for 1~2 minutes every now and then.
>>>
>>> Every now and then is not unusual; prolonged or unending spikes of 100%
>>> are not.

"PA Bear [MS MVP]" wrote:

> Try these, in order:
>
> • Change your default update source from Microsoft Update to Windows Update:
>
> • Delete or rename SoftwareDistribution folder:
>
> 3. Start the Automatic Updates service:
>

Thank you! My notebook no longer pegs at 100% CPU every time it starts, and
Windows Update actually finds updates instead of burning a hole through my
lap.

This started for me about 2 days ago, first it only affected Windows Update
(but not Automatic Update) on a machine that was installed 4 days ago! Clean
install of SP3 slipstream, etc. I started installing Office 2003, and the
issue(s) started, and I wasn't about to spend another 12 hours reinstalling
the machine either.

This is an issue, probably related to the MSI/MSP issue of 2007, and it's
going to affect a lot of people. If MS wants logs of either WindowsUpdate or
something under SoftwareDistribution, please let me know because I now know
this isn't an isolated issue, and I have backups that I can retrieve.

Basic repro is:
1) Install Windows XP SP3 slipstream
2) Run Windows Update (IE7, etc. etc.)
3) Install Office 2003
4) Install Office SP3 from network install
5) Run Windows Update again

As you can see, this is a pretty standard setup on a new install, and
something like this should never have happened. My poor laptop has been
spinning it's fan off for the past two days trying to get Windows Update to
recognize itself, now I can give it a rest for a while.

Thanks again.

YW. You may need this, too:

Updates are not installed successfully from Windows Update, from Microsoft
Update, or by using Automatic Updates after you repair a Windows XP
installation:
http://support.microsoft.com/kb/943144

NB: Also applies to clean installs, upgrade installs, and Recovery installs.
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/


RealityBytes wrote:
> "PA Bear [MS MVP]" wrote:
>
>> Try these, in order:
>>
>> • Change your default update source from Microsoft Update to Windows
>> Update:
>>
>> • Delete or rename SoftwareDistribution folder:
>>
>> 3. Start the Automatic Updates service:
>>
>
> Thank you! My notebook no longer pegs at 100% CPU every time it starts,
> and
> Windows Update actually finds updates instead of burning a hole through my
> lap.
>
> This started for me about 2 days ago, first it only affected Windows
> Update
> (but not Automatic Update) on a machine that was installed 4 days ago!
> Clean install of SP3 slipstream, etc. I started installing Office 2003,
> and the issue(s) started, and I wasn't about to spend another 12 hours
> reinstalling the machine either.
>
> This is an issue, probably related to the MSI/MSP issue of 2007, and it's
> going to affect a lot of people. If MS wants logs of either WindowsUpdate
> or something under SoftwareDistribution, please let me know because I now
> know this isn't an isolated issue, and I have backups that I can retrieve.
>
> Basic repro is:
> 1) Install Windows XP SP3 slipstream
> 2) Run Windows Update (IE7, etc. etc.)
> 3) Install Office 2003
> 4) Install Office SP3 from network install
> 5) Run Windows Update again
>
> As you can see, this is a pretty standard setup on a new install, and
> something like this should never have happened. My poor laptop has been
> spinning it's fan off for the past two days trying to get Windows Update
> to
> recognize itself, now I can give it a rest for a while.
>
> Thanks again.

If you have a backup of the original slipstreamed SP3 installation,
would you please post the size of DataStore.edb ?
It's located in WINDOWS\SoftwareDistribution\DataStore.
That might be the file that is causing this issue.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


RealityBytes wrote:

> "PA Bear [MS MVP]" wrote:
>
>
>>Try these, in order:
>>
>>• Change your default update source from Microsoft Update to Windows Update:
>>
>>• Delete or rename SoftwareDistribution folder:
>>
>>3. Start the Automatic Updates service:
>>
>
>
> Thank you! My notebook no longer pegs at 100% CPU every time it starts, and
> Windows Update actually finds updates instead of burning a hole through my
> lap.
>
> This started for me about 2 days ago, first it only affected Windows Update
> (but not Automatic Update) on a machine that was installed 4 days ago! Clean
> install of SP3 slipstream, etc. I started installing Office 2003, and the
> issue(s) started, and I wasn't about to spend another 12 hours reinstalling
> the machine either.
>
> This is an issue, probably related to the MSI/MSP issue of 2007, and it's
> going to affect a lot of people. If MS wants logs of either WindowsUpdate or
> something under SoftwareDistribution, please let me know because I now know
> this isn't an isolated issue, and I have backups that I can retrieve.
>
> Basic repro is:
> 1) Install Windows XP SP3 slipstream
> 2) Run Windows Update (IE7, etc. etc.)
> 3) Install Office 2003
> 4) Install Office SP3 from network install
> 5) Run Windows Update again
>
> As you can see, this is a pretty standard setup on a new install, and
> something like this should never have happened. My poor laptop has been
> spinning it's fan off for the past two days trying to get Windows Update to
> recognize itself, now I can give it a rest for a while.
>
> Thanks again.

"MowGreen [MVP]" wrote:

> If you have a backup of the original slipstreamed SP3 installation,
> would you please post the size of DataStore.edb ?
> It's located in WINDOWS\SoftwareDistribution\DataStore.
> That might be the file that is causing this issue.
>

Z:\WINDOWS\SoftwareDistribution\DataStore>dir
Volume in drive Z has no label.
Volume Serial Number is 545A-3FA7

Directory of Z:\WINDOWS\SoftwareDistribution\DataStore

05/11/2008 10:34 PM <DIR> .
05/11/2008 10:34 PM <DIR> ..
05/13/2008 01:45 AM 3,153,920 DataStore.edb
05/13/2008 01:45 AM <DIR> Logs
1 File(s) 3,153,920 bytes
3 Dir(s) 8,150,077,440 bytes free

This is the backup from when I was having problems.

"MowGreen [MVP]" wrote:

> If you have a backup of the original slipstreamed SP3 installation,
> would you please post the size of DataStore.edb ?
> It's located in WINDOWS\SoftwareDistribution\DataStore.
> That might be the file that is causing this issue.
>

Nevermind my previous post, I forgot that my backup happens "next day" and
thought that the backup happened the day after. Since I don't have the
backup, I just decided to re-enable Microsoft Update, and see what happens.

Same issue, 100% CPU usage, svchost tends to ramp from 10M to 50M memory
usage in task manager while eating up CPU time, DataStore was 2.5M from when
I was using Windows Update only, jumping to 5.2M, then 9.4M, then 11.5M even
as we speak (same update session). There definately does seem to be an issue
with this file, and the memory usage goes from 10M gradually to 50M according
to Task Manager, then suddenly drops back to 10Mish then goes back again,
each time eating up more memory.

After 10min worth of CPU time ramping at up 24-63M of memory and DataStore
seems to have settled in at 11,542,528 bytes. It finally found an update for
Office, so I'll let it install and see what happens. I think the culprit is
Microsoft Update, so if it decides to burn a hole through my lap, I'll just
disable Microsoft Update and delete the SoftwareDistribution folder which
seems to make it a lot happier.

Installing the latest Version of the Windows Update Agent *should*
mitigate the CPU utilization issue.
Faulty detection logic in previous Vs can cause the a spike in CPU
utilization when it scans datastore.edb

SP3 contains older Vs of the AU core update files and if higher V. files
are found on the OS during the application of it, it leaves them as they
are.
I'm not sure what the behavior would be if it found lower Vs.
Here's a theory ... when the AU service fires up or a system hits one of
the update sites there will be an attempt to update wuaueng.dll first
which then causes the CPU utilization issue to appear since the file
isn't being updated because other AU .dlls needed to download and/or
install it are at a lower V level.
Frankly, I haven't seen this issue on systems on which I applied SP3,
but all of the systems already contained the latest WUA.

There is no AV nor any other anti-malware software installed, correct ?

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============



RealityBytes wrote:

> "MowGreen [MVP]" wrote:
>
>
>>If you have a backup of the original slipstreamed SP3 installation,
>>would you please post the size of DataStore.edb ?
>>It's located in WINDOWS\SoftwareDistribution\DataStore.
>>That might be the file that is causing this issue.
>>
>
>
> Nevermind my previous post, I forgot that my backup happens "next day" and
> thought that the backup happened the day after. Since I don't have the
> backup, I just decided to re-enable Microsoft Update, and see what happens.
>
> Same issue, 100% CPU usage, svchost tends to ramp from 10M to 50M memory
> usage in task manager while eating up CPU time, DataStore was 2.5M from when
> I was using Windows Update only, jumping to 5.2M, then 9.4M, then 11.5M even
> as we speak (same update session). There definately does seem to be an issue
> with this file, and the memory usage goes from 10M gradually to 50M according
> to Task Manager, then suddenly drops back to 10Mish then goes back again,
> each time eating up more memory.
>
> After 10min worth of CPU time ramping at up 24-63M of memory and DataStore
> seems to have settled in at 11,542,528 bytes. It finally found an update for
> Office, so I'll let it install and see what happens. I think the culprit is
> Microsoft Update, so if it decides to burn a hole through my lap, I'll just
> disable Microsoft Update and delete the SoftwareDistribution folder which
> seems to make it a lot happier.

Problems seems to be solved now, many thanks

"PA Bear [MS MVP]" wrote:

> Try these, in order:
>
> • Change your default update source from Microsoft Update to Windows Update:
>
> Go to Microsoft Update | Click on Change Settings in left pane | Scroll to
> bottom of page | To Stop Using Microsoft Update | Disable Microsoft Update
> software and let me use Windows Update only (check).
>
> With Windows Update as your default, you will need to check in at Office
> Update to keep your Office applications fully patched:
> http://office.microsoft.com/en-us/do...incatalog.aspx
>
> • Delete or rename SoftwareDistribution folder:
>
> 1. Stop the Automatic Updates service:
>
> Start > Run > (type in) services.msc > [OK]
> Double-click Automatic Updates > Click on Stop
> (Stopping the service will take a moment)
>
> 2. Delete %windir%\SoftwareDistribution <=this folder or rename it (e.g.,
> SoftwareDistribution.OLD).
>
> NB: The above step will have the consequence of deleting your Update History
> at Windows Update.
>
> 3. Start the Automatic Updates service:
>
> Start > Run > (type in) services.msc > [OK]
> Double-click Automatic Updates > Click on Start
> (Starting the service will take a moment)
> --
> ~PA Bear
>
>
> benoitm wrote:
> > I just ran the following test:
> > - Disabled Avira AntiVir Guard
> > - Exited TeaTimer
> > I then manually went to Windows Update
> >
> > Result: more than 3 minutes at 100% CPU !
> >
> > After installation of a couple of Office updates, I then restarted my
> > laptop. As I am writing this, the fan is again spinning at 100% just like
> > the CPU, and Process Explorer is already reporting 4:23 minutes of CPU
> > time
> > for svhost.exe, of which 3:40 min just for wuaueng.dll....
> >
> > Any suggestions for further t'shooting would be welcome
> >
> > "benoitm" wrote:
> >
> >> Being unable to perform any useful work for 2 minutes shortly after I
> >> wake
> >> up from hibernation my 2 GHz laptop does not seem acceptable to me,
> >> especially since this problem did not exist previously (i.e. when I had
> >> XP
> >> SP2)...I wouldn't call 2 minutes of 100% CPU a "spike"...If at least the
> >> offending process was running in a lower priority !
> >>
> >> "PA Bear [MS MVP]" wrote:
> >>
> >>>>>> And I noticed the same 100% CPU utilization in svchost (Automatic
> >>>>>> Updates)
> >>>>>> for 1~2 minutes every now and then.
> >>>
> >>> Every now and then is not unusual; prolonged or unending spikes of 100%
> >>> are not.
>
>

[Blackb68]

I too have had this problem. I bought a new computer about 2 months ago. Installed only Vanguard and Ventrilo. Computer seemed perfect for the first night but unplayable the next morning. I will admit now that I am not a savvy computer person. I know a little. I bought a G15 Keyboard which alerted me to the problem of 100$% CU usage - for the past 2 mths I have been reading posts and trying subtle things to correct it. I have already attempted 3 clean instals of XP - I do not want to do again.I found a work around that works well and may reveal to you (more savvy peeps) a potential problem. My 100% CPU usage was fixed when we had a power failure here at home. Now when I switch on the computer, if 100% CPU usage is evident on my G15 display - I pull the power cord from the back of the computer - and upon startup the 100% CPU usage has disappeared.

Note:-
1. 100% CPU usage never occurs whilst the computer is on. To test - I left the computer on for 1 week
2. The problem only occurs upon startup
3. On one of my clean installs, I did not install anything further, within 1 day, the 100% CPU usage returned.
4. Whatever windows does when it shuts down may be causing this (maybe)

Please help