SVCHOST.EXE inscreases in size until nothing works on the computer now..

[Galpersonal]

Anyone know why the process "SCVHOST.EXE" would grow and grow larger and
larger? What's happening is a few people's computers will get slower and
slower, and then services won't run any longer, until the SVCHOST.EXE is
Ended.

Anti-virus is installed and it's not finding anything on the PC. Also, anti
spyware has also scanned the systems and didn't fine anything either.

-Blake

 

[JS]

From Ramesh's web site: http://windowsxp.mvps.org/svchost.htm
Also: http://support.microsoft.com/?kbid=314056

To find out more about Svchost.exe entries try Process Explorer:
http://www.microsoft.com/technet/sysinternals/SystemInformation/ProcessExplorer.mspx

Once you have Process Explorer installed and running:
In the taskbar select View and check 'Show Process Tree' and 'Show Lower
Pane' options.
(This will provide the detailed info you need)
Next click/Expand the Svchost.exe process that you are interest in.
Then highlight one of the process listed under Svchost, right click and from
the options listed select: google
This should display what out there on the web about that process.

Still another tool is What's Running
http://www.whatsrunning.net/whatsrunning/main.aspx

JS

 

[NewScience]

Normally, the one that is the largest (SVCHOST), is the one handling most of
the network related services .... specifically WIndows Update.

Depending on how your systems are set up, when you connect to the Internet,
Automatic Updates starts processing ... checking your system against what
needs to be downloaded.

This snapshot of the system is memory intensive. However, Memory Usage is
not a concern, because it will be returned to the system. The item to check
is CPU, if that number stays high, then you have a corrupted Automatic
Update DataStore log or such.

Usually clearing out the C:\Windows\SoftwareDistribution folder puts SVCHOST
back in order.

 

[paul]

I have the same problem.
Can any MVP's verify it is safe to delete these files?

 

[Galpersonal]

Yes, there are a bunch of folders in that directory. What needs to be
"cleaned out"? Or do all folders get deleted?

-Blake

 

[NewScience]

If you want to put everything back to square one and re-sync everything up:

1. Start Menu | Run ... cmd
2. net stop bits
3. net stop wuauserv
4. CD C:\windows (or your %windir% folder)
5. RM WindowsUpdate.log
6. CD SoftwareDistribution
7. RD /s DataStore
8. RD /s Download
9. CD C:\Documents and Settings\All Users\Application
Data\Microsoft\Network\Downloader
10. DEL *.dat
11. net start bits
12. net start wuauserv

If you want to re-initialize the entire Windows Update operations (have
support files re-install), in Step 6, change to RD /s SoftwareDistribution
and skip Steps 7 and 8.

This will cause Windows/Microsoft Update to sense that the support files are
missing and will reinstall/ re-register and re-sync everything.

But do the other steps.

NOTE: this will cause the View History option on the Web-site to display
nothing. The information is kep in each PCs DataStore/DataStore.edb file.

You can check how valid everything is prior to doing all this using the
ESENTUTL utility. It will verify the DataStore.edb file as far as
integrity.

Just type ESENTUTL and a CMD prompt and follow the instructions. The main
one is:

1. STart Menu | Run ... cmd
2. CD C:\Windows\SoftwareDistribution\DataStore
3. ESENTUTL /g datastore.edb

 

[Guest]

Thanks for your reply. Excuse my ignorance but what do CD, RM & RD mean. When
I put these into the string the command is not recognised.

I look forward to hearing from you
Martin

 

[paul]

They should be lowercase

Thanks for your reply. Excuse my ignorance but what do CD, RM & RD mean.
When
I put these into the string the command is not recognised.

I look forward to hearing from you
Martin

 

[paul]

Just curious. Do you have Norton Anti-Virus 2007 installed?

 

[NewScience]

SOunds like you didn't Click OK when you typed cmd in the STart Menu | Run
window.

Sorry about the RM, should have been DEL

Uppercase/lowerecase makes no difference at COmmand Prompt (DOS)