Re: wuauclt + svchost vs CPU issue, need comments.

As I restarted the workstation, it went frenzy again and pretty much "locked
up" for 20 mins.

I cannot allow this "non workstable state" to happens during the day, users
have to work and use their computer.

Thanks tho.


On another note, this isn't really an issue while scanning has to be done.
Now, the problem is that it happens during the day, it happens when someone
is using it. That is the problem. Even if it would take 4hrs, I wouldn't
mind at midnight.

Anyhow... dont we all love microsoft?

"Jim Byrd" wrote:

Hi MJ - The following seems to be working. One respondent did note some
additional steps he had to take in two cases to handle the WSUS issue, and
I've added his response to the end. This is a general posting intended for
all levels of users:


How knowledgable about doing things are you? Do you know how to start and
stop services? How to run a .cmd file? If not, you'll need access to
someone who does to avoid problems. The following assumes you're on Windows
XP but will probably work OK for Win2k as well. If you're confident about
what you're doing, then try the following first - only if it doesn't work,
then there's another level of stuff that can be done following:

1. Stop and Disable Automatic Updates, Background Intelligent Transfer
Service and the Cryptographic Service.
2. Rename the folder %SystemRoot%\SoftwareDistribution to
%SystemRoot%\OldSoftwareDistribution
3. Open Notepad and create a file containing the following:

REGSVR32 WUAPI.DLL
REGSVR32 WUAUENG.DLL
REGSVR32 WUAUENG1.DLL
REGSVR32 ATL.DLL
REGSVR32 WUCLTUI.DLL
REGSVR32 WUPS.DLL
REGSVR32 WUPS2.DLL
REGSVR32 WUWEB.DLL


Save this file as 'Wudll.cmd' (without the quotes) to any convenient
location then exit Notepad and double click on the file you just saved. You
should get a 'Sucess' mesage for each of the .dll's listed above.

4. Now Re-enable to Automatic status and then Start each of the services
you stopped before - Automatic Updates, Background Intelligent Transfer
Service and the Cryptographic Service.

5. Now Reboot. Now Reboot Again. (Yes, twice.)

See if that solves it - give it a couple of days. If so, then you can
delete 'OldSoftwareDistribution'. I would request that you post back with
your results. _Only if the problem does re-occur_, then do the following
_exactly_:

1. Go to http://wiki.djlizard.net/Dial-a-fix and download Dial-a-fix
v0.60.0.24 (2006-10-27) Here's a direct download link:
http://djlizard.net.nyud.net:8080/software/Dial-a-fix-v0.60.0.24.zip and a
secondary: http://djlizard.net/software/Dial-a-fix-v0.60.0.24.zip from
that page's download section, here:
http://wiki.djlizard.net/Dial-a-fix#Mirrors.2Fdownload_locations.2C_and_articles .

2. Unzip it to a new folder at root with any name, e.g.
c:\Dial-a-fix-v0.60.0.24

3. Double click on Dial-a-fix.exe in that folder.

4. Click on the following:
Options/tooltips (just to get an idea of what it does in each section.
:) )
Both boxes under Prep
The 'all' (top) box for Sections 2, 3 and 4 (which will automatically
be set when you check 3)
In Section 5, 'Programming cores/runtimes' and
'Explorer/IE/OE/shell/WMP' only.
Click 'Go' . (Some of the re-registrations may take what seems like a
long time for some .dll's - Don't be impatient.)

5. Reboot (if Dial-a-fix doesn't do it automatically at the end). Now
Reboot Again. (Yes, twice.)


See if that does the trick, and, again please post back with your
experience.



MS is well aware of the problem and has provided privately two different
responses concerning a fix:

"I regret to say that I was told that this known issue requires too much
change to be implemented in a hotfix. A change will instead be implemented
in the next Automatic Updates client, which we are planning to release in Q2
this year."

"According to the feedback from Product Development team, this fix will be
published as a security update on the Windows Update site and the relevant
KB article will also be released by us. Therefore, we just need to keep the
system on the network up to date. In addition, the Product Development team
also indicates that the WSUS 3.0 client may contain this patch if this fix
can released timely. At that moment, we can also attempt to upgrade to the
WSUS client 3.0 to test the issue."




Here's feedback from one respondent reference this fix and the WSUS issues:


"I have applied Jim Byrd's suggested fix on a number of my affected
computers. This is my methodology and my results.


I have conclusively identified 23 computers [out of 389 total domain
computers] affected with the behavior described in KB 932494. Of the 23 I
applied the hotfix described in KB 916089 to 10 keeping the other 13 as a
control group. As I mentioned before, the hotfix achieved a 0% effective
rate. Then I selected 8 computers, 4 in the hotfix group and 4 in the
control group and applied the Byrd solution. Of the 8 eventually all
achieved nominal performance. I say eventually because 2 computer [both in
the control group] required me to delete AccountDomainSis, PingID and
SusClientId from the Registry and /resetauthorization before they would
check in with the WSUS server.


So either the Byrd solution is good for me or I haven't yet taken a broad
enough sampling. Since I intend to apply the solution to the rest of my
affected computers, should I find a clunker I'll let you know."



--
Regards, Jim Byrd,
My Blog, Defending Your Machine,
http://defendingyourmachine2.blogspot.com/



In news:81F5E114-4FFF-4410-AAE1-274CEB59277E@xxxxxxxxxxxxx,
M.J. <MJ@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
|| What do you guys think of this link?
||
||
http://msmvps.com/blogs/bradley/archive/2007/04/14/wsus-celerons-and-svchost.aspx
||
|| So far, I'm really hoping this last one would fix it for good.
||
|| Also, why is there we cannot choose "when" the scan happens while
|| using WSUS? Why does it have to be every 22hrs?



.

Relevant Pages

  • Re: wuauclt + svchost vs CPU issue, need comments.
    ... Stop and Disable Automatic Updates, ... "According to the feedback from Product Development team, this fix will be ... also indicates that the WSUS 3.0 client may contain this patch if this fix ... computers] affected with the behavior described in KB 932494. ...
    (microsoft.public.windowsupdate)
  • Re: wuauclt + svchost vs CPU issue, need comments.
    ... additional steps he had to take in two cases to handle the WSUS issue, ... Stop and Disable Automatic Updates, ... "According to the feedback from Product Development team, this fix will ... computers] affected with the behavior described in KB 932494. ...
    (microsoft.public.windowsupdate)
  • Re: wuauclt + svchost vs CPU issue, need comments.
    ... additional steps he had to take in two cases to handle the WSUS issue, ... Stop and Disable Automatic Updates, ... "According to the feedback from Product Development team, this fix will ... I have conclusively identified 23 computers [out of 389 total domain ...
    (microsoft.public.windowsupdate)
  • Re: wuauclt + svchost vs CPU issue, need comments.
    ... "PA Bear" wrote: ... Stop and Disable Automatic Updates, ... "According to the feedback from Product Development team, this fix will ... I have conclusively identified 23 computers [out of 389 total domain ...
    (microsoft.public.windowsupdate)
  • Re: wuauclt + svchost vs CPU issue, need comments.
    ... Also, I didn't compare everything, but the dial-a-fix does everything you ... "According to the feedback from Product Development team, this fix will be ... also indicates that the WSUS 3.0 client may contain this patch if this fix ... I have conclusively identified 23 computers [out of 389 total domain ...
    (microsoft.public.windowsupdate)