bkoehle replied on 14-Apr-07 02:27 PM
On machines experience the 100% CPU issue; are there pending updates
that have been downloaded but not installed?




JB Miha replied on 14-Apr-07 04:39 PM
The best temp fix is to disable AU service and wait till problem is fixed.







Miha
PA Bear replied on 14-Apr-07 08:01 PM
NB: CogX started this thread. <snicker>
--
~PA├×
M replied on 23-Apr-07 08:02 AM
FYI regarding this point :

1.  Go to http://wiki.djlizard.net/Dial-a-fix ; and download Dial-a-fix
v0.60.0.24 (2006-10-27)


From the website :

Dial-a-fix
From TechWiki
Jump to: navigation, search
There is currently no text in this page, you can search for this page title
in other pages or edit this page.
Jim Byrd replied on 23-Apr-07 11:39 AM
Hi MJ - I gather that you had difficulty getting to that page?  I got there
fine just now.  However, 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
both of which are working fine as of this moment.  See if those help.

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



M.J. <MJ@> typed:
Kell replied on 23-Apr-07 05:24 PM
I have applied the update talked about in this thread with out success. Kelly
Jim Byrd replied on 23-Apr-07 07:41 PM
Hi Kelly et al in this thread.  Please try the following if able.  It seems
to work, at least for all those from whom I've had feedback so far:


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)

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:

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."

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."


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



Kelly <Kelly@> typed:
allen60 replied on 02-May-07 04:35 PM
Hi Jim, I'm very technical and we've tried all as mentioned below and
from Technet and Various newsgroups.  I even went as far as building 2
WSUS servers (1 standalone and 1 child to our existing).
Standalone looked like it was working and now it's doing the same
thing and highly suspect it's the Microsoft Update engine as opposed
to the WIndows Update agent that is causing it, and it's also
happening to the laptops (which are slower than the desktops).

I'll search around on the newsgroup some more as I've basically turned
off AutoUpdates via GPO so users can work and I can research while
also working on other things.

Allen

On Apr 20, 12:15 am, "Jim Byrd" <jrb...@spamless.roadrunner.com>
allen60 replied on 02-May-07 04:45 PM
looks like there maybe a fix
http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx
Jim Byrd replied on 02-May-07 05:32 PM
Hi Allen - There apparently is.  Even if you're not still having problems,
this would be a good idea:


The newly released 'standalone' version of Windows Update Agent 3.0, v.
7.0.6000.374, for 32 bit machines is available here:
http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe

You will also need to install or re-install KB927891, here:
http://support.microsoft.com/?kbid=927891 for a complete fix.


For those using Windows Server - Courtesy of Bobby Harter, Program Manager,
WSUS, Microsoft, WSUS 3.0 was released on April 30th and is avaialble now on
the Microsoft Download Center.  Full information, documentation, samples and
links to the bits can be found here:  http://www.microsoft.com/wsus.  WSUS
3.0 RC will be supported until May 31st 2007 - WSUS 3.0 supports upgrade of
WSUS 2.0 SP1 and WSUS 3.0 RC.

The MS WSUS team believes that this solves all three 'svchost' problems that
folks have been experiencing.  See here:
http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx





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



allen604@gmail.com <allen604@gmail.com> typed:
allen60 replied on 03-May-07 02:54 PM
Hi Jim
So from reading the newsgroups:
1) install the hotfix 927891
2) install the WUA agent 3.0
3) upgrade the Server to 3.0

For the Hotfix: can that be applied to machines not affected? We
aren't sure who's really affected as our user base is 3,000, and I'd
like to push the hotfix via SMS to XP machines to make things
simpler.

Any harm in doing that?
thanks
Allen
Ottmar Freudenberger replied on 03-May-07 11:21 PM
Yes.


No.

Bye,
Freudi
Windows 7 - Hi Allen - I don't think that that's any kind of problem as long as you are
Asked By Jim Byrd on 04-May-07 01:49 AM
Hi Allen - I don't think that that's any kind of problem as long as you are
careful to push the appropriate version of 927891 for the box involved -
there are several depending on whether a box is XP or Windows Server and
whether the box OS is 32 or 64-bit.  See here:
http://support.microsoft.com/?kbid=927891  If they are _all_ 32-bit XP, then
the only one you will need to push is here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=7A81B0CD-A0B9-497E-8A89-404327772E5A
That hotfix and the new Update Agent should probably be upgraded on all
machines to prevent the occurance of the 'svchost' related issues on those
that haven't had the problem as well as to correct it (hopefully
permanently) on those that have.

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



allen604@gmail.com <allen604@gmail.com> typed: