That's right bitches. Here's some food for thought for the "run nothing unless you need it" crowd, copied from http://kadaitcha.cx/performance.html. - - - Tweak #10: Don't disable unwanted Windows services. Does that tweak surprise you? How can doing nothing be considered a performance tweak? There are thousands of requests on Internet Web forums and Usenet newsgroups for advice on services that can be disabled, and there are an equal number of Windows-related Websites offering lists of services that can be disabled. So, given that large body of knowledge and apparent expertise in service disabling, you may be surprised to learn that kadaitcha.cx asserts it is potentially foolish, certainly it's counter-productive, and it is technically naive. Why is it so? There are four main reasons. First, services that are loaded often do not run when they are unused. At worst, an unused service will consume RAM; RAM is cheap, and adding RAM to your machine is one of the best tweaks you can perform anyway. When a service starts up, it tells the Operating System that it needs to be invoked when such and such an event takes place, and the OS dutifully does not invoke the service until such and such an event actually does take place. Thus the service lies dormant until it is invoked by the operating system. Services like the Indexing Service and Perflib (Performance Monitor, see Tweak #11) execute at regular intervals and can be disabled if they are causing performance issues, but there are very few other services in this class. If you need proof of this, just start Task Manager and look at the list of services sitting there, doing nothing other than consuming marginal amounts of RAM. Second, disabling services that you feel you do not need now can lead to major problems when you do need a certain disabled service to run. This is especially going to be a problem if you forget that you have disabled particular services and are unaware that you need the service running to use an application. What happens if you disable the Windows Fax and Scan service, then, say some months later, decide to install Microsoft Office, for example, and try to send a fax or scan a document from within Office? It isn't going to work, and unless you immediately remember that you've disabled the Windows Fax and Scan service, you're going to be spending far more time troubleshooting the problem than you will save over the entire life of several computers by disabling it. Still with the second reason for not disabling services, some websites, no doubt managed by the technically incompetent in many cases, suggest that the DNS Client Service can be disabled, especially if you have a modem/router that performs DNS services; the idea being, "if the modem/router performs the DNS tasks, why let XP do it?". The fact of the matter is, the Windows DNS Client Service is a cache of IP and Web addresses, so if you disable this service then you disable the cache. Since caches are intended to boost performance, it should be obvious that disabling a cache will reduce performance. If the DNS cache is enabled then your OS already knows the IP address of the site it wants to communicate with, and it can do so directly, without the router needing to look up the host name on a remote name server in order to retrieve the IP address. To put this in simple terms, by disabling the DNS cache in XP, you force your modem/router to lookup the IP address on a name server somewhere in the big-Internet-cloud-in-the-sky before every single connection is made to a site using its name, and this can take up to several seconds, even if you have a high-speed connection. Third, any performance gains from disabling services that don't execute unless they're needed anyway will be so insignificant that you will not be able to perceive a performance increase at all. So, if a performance gain cannot be perceived, why bother? To be worthwhile, a performance tweak must have a perceptible performance gain, and the best you can expect from disabling unused services is a few hundred nanoseconds in operating system boot time, which in the scheme of things for today's PCs, is much less than a small fraction of the time it takes to blink. Fourth, there are a number of idle-time tasks that must be performed on a regular basis by the OS. The Task Scheduler runs at regular intervals to check if the system is idle, i.e. not being used, and if the machine is idle, the idle-time tasks are executed. It is pointless to disable tasks that only run when the system is not being used. So don't disable apparently unused, running services or tasks.