|
|
I have many XP devices that are still having svchost staying on 100% CPU even
after installing the 3.0 client. What's next?
|
|
But it's still responsive and you are able to work with it during this
period, is it?
Then, that's the change.
Franz
"AG" <AG[ at ]discussions.microsoft.com> schrieb im Newsbeitrag
news:7520BB60-BDF0-4F72-9735-32E4836F8F53[ at ]microsoft.com...
[Quoted Text] >I have many XP devices that are still having svchost staying on 100% CPU
>even
> after installing the 3.0 client. What's next?
|
|
On Fri, 11 May 2007 18:09:27 +0200, "Franz Leu"
<franz.spam-removal.leu[ at ]norfolk.spam-removal.ch> wrote:
[Quoted Text] >But it's still responsive and you are able to work with it during this >period, is it? >Then, that's the change. >Franz > >"AG" <AG[ at ]discussions.microsoft.com> schrieb im Newsbeitrag >news:7520BB60-BDF0-4F72-9735-32E4836F8F53[ at ]microsoft.com... >>I have many XP devices that are still having svchost staying on 100% CPU >>even >> after installing the 3.0 client. What's next?
To be frank that is what you need. 100% CPU use to get the thing done ASAP. But
not locking the system. AU should take every bit of CPU that is not required for
other work, i.e. don't waste the CPU on the Idle process but make sure it in low
priority.
>
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.
|
|
No, it is still totally unresponsive for extensive periods of time. There is
no chage from previous behavior with the new client.
"Franz Leu" wrote:
[Quoted Text] > But it's still responsive and you are able to work with it during this > period, is it? > Then, that's the change. > Franz > > "AG" <AG[ at ]discussions.microsoft.com> schrieb im Newsbeitrag > news:7520BB60-BDF0-4F72-9735-32E4836F8F53[ at ]microsoft.com... > >I have many XP devices that are still having svchost staying on 100% CPU > >even > > after installing the 3.0 client. What's next? > > > |
|
Yes, we had done that when it was released, before the WUA3 was released.
"Myweb" wrote:
[Quoted Text] > Hello AG, > > Did you also change the installer for XP? > > http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7a81b0cd-a0b9-497e-8a89-404327772e5a> > It is also new and can only be used with the WINDOWSUPDATEAGENT30-X86.exe > from 01.May 2007 > > > > Best regards > > Myweb > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > No, it is still totally unresponsive for extensive periods of time. > > There is no chage from previous behavior with the new client. > > > > "Franz Leu" wrote: > > > >> But it's still responsive and you are able to work with it during > >> this > >> period, is it? > >> Then, that's the change. > >> Franz > >> "AG" <AG[ at ]discussions.microsoft.com> schrieb im Newsbeitrag > >> news:7520BB60-BDF0-4F72-9735-32E4836F8F53[ at ]microsoft.com... > >> > >>> I have many XP devices that are still having svchost staying on 100% > >>> CPU > >>> even > >>> after installing the 3.0 client. What's next? > > > |
|
Hi AG - Try this. It's part of a 'pre-Agent update fix' workaround I
developed with some MS personnel. 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 3 click on 'Flush Software Distribution' and choose 'Yes'
to force the deletion of the folder.
- In Section 5, 'Programming cores/runtimes',
'Explorer/IE/OE/shell/WMP', and 'Object linking libraries (OLE)' 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. Now Reboot Again. (Yes, twice.)
See if that does the trick, and, again please post back with your
experience.
--
Regards, Jim Byrd,
My Blog, Defending Your Machine,
http://defendingyourmachine2.blogspot.com/
In news:34FBB988-4CD3-414D-B034-51FED8D26316[ at ]microsoft.com,
AG <AG[ at ]discussions.microsoft.com> typed:
|| Yes, we had done that when it was released, before the WUA3 was
|| released.
||
|| "Myweb" wrote:
||
||| Hello AG,
|||
||| Did you also change the installer for XP?
|||
|||
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7a81b0cd-a0b9-497e-8a89-404327772e5a
|||
||| It is also new and can only be used with the
||| WINDOWSUPDATEAGENT30-X86.exe from 01.May 2007
|||
|||
|||
||| Best regards
|||
||| Myweb
||| Disclaimer: This posting is provided "AS IS" with no warranties,
||| and confers no rights.
|||
|||| No, it is still totally unresponsive for extensive periods of time.
|||| There is no chage from previous behavior with the new client.
||||
|||| "Franz Leu" wrote:
||||
||||| But it's still responsive and you are able to work with it during
||||| this
||||| period, is it?
||||| Then, that's the change.
||||| Franz
||||| "AG" <AG[ at ]discussions.microsoft.com> schrieb im Newsbeitrag
||||| news:7520BB60-BDF0-4F72-9735-32E4836F8F53[ at ]microsoft.com...
|||||
|||||| I have many XP devices that are still having svchost staying on
|||||| 100% CPU
|||||| even
|||||| after installing the 3.0 client. What's next?
|
|
Thanks, will let you know.
|
|
"AG" <AG[ at ]discussions.microsoft.com> schrieb:
[Quoted Text] > Thanks, will let you know.
In case that didn't help, you may wish to try a "netsh winsock reset"
via "Run" in the Start menu (http://support.microsoft.com/kb/811259).
Bye,
Freudi
|
|
|