Win XP Processes?

[SKJohn]

Can somebody post a list of the processes that should be running in Win XP?  I thought I saw it here before, but can't find it again.  The computer my wife & kids use has been getting slow, and it has 63 processes running the last time I checked.  IIRC, that is about 2 -3 times more than it should have.  Any help would be greatly appreciated!
Thanks,
John

[Nwbie]

http://www.blackviper.com/

check out his recommendations

[MrRiplEy[H]]

I could just screenshot the processes of my computer with 17 running processes

Then again I only play with it so even print spooler etc. is disabled. You can still use any application, play and browse internet though.

[batch]

I created a tutorial for some of the guys on here to use. Gives step by step instructions on how to turn off all the processes and has a list of suggestions for each one. If you want a copy send me your email addy in PM and I'll be happy to forward.

I run 11 processes while Im in AH, outside of AH it just depends on what software I open.

[gyrene81]

Can somebody post a list of the processes that should be running in Win XP?  I thought I saw it here before, but can't find it again.  The computer my wife & kids use has been getting slow, and it has 63 processes running the last time I checked.  IIRC, that is about 2 -3 times more than it should have.  Any help would be greatly appreciated!
Thanks,
John

Short and sweet...ideally with a fresh load, all drivers and peripherals installed you should have somewhere between 42 and 50 processes running depending...if you have 63 and it's running slow...malware/spyware...get rid of whatever corporate bloatware anti-virus you have been running and grab either Avira or Avast (both free but require registration).

Download Malwarebytes, Spybot Search and Destroy, Asquared...and whatever other recommendations you get in this thread.

[Skuzzy]

Uh, I just did an OEM installation of Windows XP, and it had 24 processes running in it, before I started to whack then down.  19 to 21 is a pretty clean system. 

42 to 50 is Windows Vista territory, but even then I have a stock Windows Vista Ultimate installation setting here and it has 38 processes in the background.

[gyrene81]

WTH are you running Skuzzy? Windows XP Professional SP3 has 23 processes without adding drivers and turning power management and auto-updates completely off...throw in anti-virus and you add 3 to 8 more...printer adds a few...usb devices...sound, video, network adds a few depending...a clean build for normal home use is 50 processes (generally speaking)...I suppose a dedicated Windows XP gaming box without any added software would be between 25 and 30...but that's no anti-virus, no firewall, no added device management processes.

[Skuzzy]

Windows XP Pro w/SP3.

My home box runs 19 processes, total.  That is with everything installed.  I do not run a software firewall, as I have a hardware firewall.  I do not run anti-virus programs as they are a waste of time for me.  The easiest way to keep from getting a virus is to disable the delivery mechanisms viral/spyware programs make use of.

Over 20 years on the ARPA/InterNet and none of my computers have ever had any spyware/malware/viruses installed on them.

My work box has 23 processes running and that includes 6 applications being run right now.

I thought we were talking about the OS, and not all the applications.  40 is way too high even with anti-virus and drivers installed.

[gyrene81]

See now that explains a lot.

Very few people know how to disable the "open door" processes in Windows and even then the list is huge so I don't even bring it up.
I take it you also disabled the Windows update process, all the log services, system restore, etc...

I would be interested to know exactly which services and processes you kill...

[Skuzzy]

I only killed a handful of services.  Like I said before, immediately after a fresh OS install, including drivers, there are about 24 processes running on it. 

This is before I disable some of the processes that default on.  I only kill windows update, windows restore, security center, dhcp, remote asst., and themes.  I end up with 19 after that.

[batch]

As I said in my earlier post.......... I run 11 processes (including AH) in XP SP3........ its not that hard to get rid of the junk.......... IMO any thing more than 25 and youre doing something wrong....... I could even get my number down to 9 processes if I took it off my network........ 99% of the crap thats default in an install is exactly that........ crap

[TequilaChaser]

I only killed a handful of services.  Like I said before, immediately after a fresh OS install, including drivers, there are about 24 processes running on it. 

This is before I disable some of the processes that default on.  I only kill windows update, windows restore, security center, dhcp, remote asst., and themes.  I end up with 19 after that.

my XPpro SP3 has 19 processes running,  including AHII (18 without AH ) ......and I still have my ESET Smart Security 4 ( software firewall & Anitvirus ) running



have been working on my Windows 7 64 bit OS.......now that is a whole nother ballgame.......

[Skuzzy]

Oh, I know TC.  I am a very conservative person when it comes to shutting things off.

The only Windows XP default install I have seen with over 25 processes was the HP/Compaq Windows XP installer.  I have never seen an OEM copy of Windows XP that had over 25 processes running in the background.  Again, just the full OS install with drivers.

[gyrene81]

I have a Windows XP Pro (MSDN copy) with SP3 and Sata drivers slipstreamed...23 processes upon first boot...then the poop hits the fan.

I won't put a system online without a virus/malware scanner...too many websites with embedded crap...I actually found a trojan embedded in the installer for a reliable program that I have used repeatedly...but the last update installer was infected. Makes you wonder.


I'll wait for Win7 service pack 1 before I make that jump...fun to play with though.

[Skuzzy]

The embedded garbage in WEB sites is the easiest thing to defeat.  Disable Java, disable any type of automatic downloads, disable .NET, kill ActiveX, stomp out any scripting whatsoever.

Once you have determined the site is safe (i.e. it is not running on a Windows OS platform) and clean, then you can drop it in your trusted sites, but sill leave Java and ActiveX dead even for trusted sites.

The reason I specifiy Windows OS servers is they are most susceptible to having viruses/spyware embedded on them without the local admin even knowing it.

I have left out a lot of details here as I figure no one would ever want to operate a computer like I operate mine.  You would have to do without Youtube, MyFace, Facebook, and a plethora of other sites I find useless.