Unneeded Services in Windows XP

Disable unnecessary services to improve performance without sacrificing functionality

The code-bloat problem seems to get worse with every release of Windows—each new release seems to run slower than the preceding one. In most cases, the problem doesn't stem from the base OS code but from the fact that each new release tends to incorporate more functionality. One key area that continues to expand is services: Windows XP automatically starts 36 services. Few users need all those services, however, and by trimming back unused services, you can make your system run more efficiently.

To disable a service, open the Control Panel Services applet and double-click the service to open its Properties sheet. On the General tab, click the Startup type drop-down box and select Disabled. If you discover that you've lost important functionality, restart the service by resetting its Startup type to Automatic or Manual. Here are 10 XP services that you can consider turning off.

10. Automatic Updates service—Some users depend on Microsoft's Automatic Updates to keep their systems up-to-date and will want to leave this service enabled. Personally, I like to be in control of the updates that are applied to my systems, so I turn off Automatic Updates.

9. Messenger service—The Messenger service sends and receives messages that the Net Send command or the Alerter service has transmitted. If you don't use the Net Send function or receive Alerter messages, you can safely disable this service.

8.TCP/IP NetBIOS Helper service—If you're still running WINS and NetBIOS on your network, you'll want the TCP/IP NetBios Helper service to remain enabled. However, if you run only TCP/IP, you can probably eliminate this service.

7. Wireless Zero Configuration service—As its name suggests, the Wireless Zero Configuration service supports automatic configuration of 802.11 wireless connections. Mobile users of laptops and tablet PCs should probably leave this service active, but networked client systems usually have no need for wireless connections and can safely disable the service.

6. Upload Manager service—The Upload Manager service performs asynchronous file transfers. This service lets your system send Microsoft information that's used to search for drivers for your system. I prefer to explicitly manage the drivers I use, so I disable the Upload Manager service.

5. Task Scheduler service—The Task Scheduler lets your system automatically run programs and scripts at a prescheduled time. Some third-party virus scanners and backup utilities use this service; others install their own scheduling service. To see whether anything on your system uses this service, open the Scheduled Tasks folder in Control Panel. If the folder is empty, you probably can disable Task Scheduler without sacrificing functionality.

4. Error Reporting service—The Error Reporting service contacts Microsoft when applications encounter an error. At first, I thought this service was cool, but after taking the time to send an error report to Microsoft several dozen times for a variety of problems with no visible result, I gave up on this service as more trouble than it's worth.

3. Remote Registry service—The Remote Registry service lets you access and manipulate the registry on other networked systems. This service can be useful on administrative workstations, but it can also be a potentially serious security exposure on end users' network clients. I recommend disabling the Remote Registry service on most client systems.

2. Server service—The Server service provides remote procedure call (RPC) support as well as support for file and print serving. Although this service is necessary on server systems, it can pose a security risk on network clients that don't need to provide file and print serving.

1. Computer Browser service—The Computer Browser service maintains and publishes to network clients a list of computers that are on the network. Although this service is useful on one or two key servers, network clients usually shouldn't run this service.

Discuss this Article 44

Anonymous User (not verified)
on Mar 17, 2005
eTrust EZAV does not require Remote Registry Svc for updates. My only remaining wish is that Automatic Updates could be told to stop telling me that my computer may be at risk. I regularly check for updates, am running a good FW on computer AND whole network is behind a firewall. Thanks for good info! I made notes so I can correct any that cause problems.
Domenic Alvaro (not verified)
on May 28, 2004
Network administrators should be aware that disabling the server service (tip 2) will disable the ability to remotely manage WinXP systems, a very handy feature for networks of all sizes (the same goes for disabling File & Printer sharing for the LAN Connection).
mark (not verified)
on May 31, 2008
Manual. Here are 10 XP services that you can consider turning off. 10. Automatic Updates service—Some users depend on Microsoft's Automatic Updates to keep their systems up-to-date and will want to leave this service enabled. Personally, I like to be in control of the updates that are applied to my systems, so I turn off Automatic Updates. . . . Where is the rest?
E (not verified)
on Dec 19, 2005
5) Task Scheduler - While could be disabled, stops a nice nifty feature in windows xp and above, remember bootvis? Well that code is intwined into startup and it helps to speed startups some, disabling task scheduler will stop this boot optimization. Also, in case some do not know this optimization also "learns" what you do with the pc and optimizes it accordingly. Disabling Task Schheduler also disables this functionality. But your call... =)
Rajeev Ramanujan (not verified)
on Jul 8, 2004
Its a always better to keep the PC switched off
Rick (not verified)
on Jul 8, 2004
This link refers to a page with a comprehensive list of services installed by Windows. It does not contain information about services that are installed by add-on software. http://www.blackviper.com/WinXP/servicecfg.htm
Abraham (not verified)
on Dec 19, 2003
Suggesting to turn Off Automatic Updates is half-way to have a new Nachi/Welchia/Blaster virus. Number 10 and 4 are quite usefull.
jim (not verified)
on Jun 7, 2004
Ditto on the comment from Al in regards disabling the Remote Registry Service here. Doing so causes McAfee products to fail at Startup on Winxp Pro. It would appear any file updates for the AV service fail implicity if this service is disabled. The rest are a mandatory at this network.
Theresa Baldwin (not verified)
on Jan 23, 2004
I'd like to pass along a tip regarding disabling one of the services mentioned in Michael Otey's article Top 10: "Unneeded Services in Windows XP" (January 2004, http://www.winnetmag.com, InstantDoc ID 40722). When I turned off the TCP/IP NetBIOS Helper service, I discovered that I could no longer add groups or users in Active Directory (AD).
Andres Fontanez (not verified)
on Jul 2, 2004
What other ones can I turn off?
Al (not verified)
on May 28, 2004
I have run into some software installation programs that refuse to correctly install if the remote registry service is off. From what I can gather, their install routine uses the remote registry service even if being locally installed. I guess they thought to save some programming time by using that service regardless of whether the software was being installed locally or to a remote PC. Its one of major virus manfucturers....
mark (not verified)
on Jun 1, 2008
I do not understand. I do not see the whole article only step 10
Dale (not verified)
on Jun 8, 2004
Turning off Automatic Update is foolish - this service can be used as merely an alerter and certainly since Sasser we all should know now the speed at which a Critical Windows Updates are applied may be the difference in having a trajic network wide infection.
chuck (not verified)
on Jul 1, 2004
My organization kept getting event ID 1058 (unable to access SYSVOL ... network path is not available) .... compared 2 servers found TCP/IP NetBIOS Helper turned off on the problematic server. Turned it back on and the error went. Other symptom was that we could not access group policies on the AD server.
Ron Stewart (not verified)
on Jun 1, 2004
Tips 9, 7, 5, 2, and 1 are good--several of them will make the system more secure. Tip #8 is a dangerous over-simplification. If you have any NetBIOS-based apps (such as Outlook), leave this service ON. Tip #4 is a bad idea; Microsoft says it finds this information vital in fixing 85% of bugs.
Pete (not verified)
on Jun 3, 2004
I find it safest to take away the network cables from all my users and issue them with pencil and paper.
Geoff (not verified)
on May 28, 2004
It is unwise to disable RPC, applications that use it for communications will fail unexpectadly.
Rod Stewart (not verified)
on Jun 22, 2004
Turning of Remote Registry will also prevent Microsoft's Baseline Security Analizer from working correctly.
BD (not verified)
on Jun 1, 2004
We have always disabled all of these services except for #10 (we have a SUS server that all pc's pull their updates from), and sometimes #8, tho #8 will happily work in an active directory environment if you map to your servers by ip address instead of name. (Outlook & AD in native mode work just fine with all of the above disabled). We have also never installed (or allowed) file & print sharing on a workstation. We even uninstall it from all servers not specifically requiring file shares.
Matt S. (not verified)
on May 27, 2004
Shutting off the server service is not an option in an environment where patches are pushed to client machines IE: SMS/Update Expert.
RONALD LEE (not verified)
on May 29, 2004
If you disable the server service, you also lose the ability to remotely access this computer for administrative services. It will not affect remote desktop or remote help in Windows XP.
brian (not verified)
on Jun 7, 2004
Does Windows NetMeeting run on the RPC service?
brian (not verified)
on May 12, 2004
In tip 3 it says that this service allows you to access another computer's registry and seems to indicate that it is only necessary to be runnning on the computer connecting to the remote registry. However, this service is needed on both the computer connecting and the computer receiving the registry connection.

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering SharePoint 2013: Succeeding, Not Just Surviving

Building on the success of the “Mastering SharePoint 2010” seminars, the presenters have updated the content to cover the latest and greatest SharePoint product: SharePoint 2013. While SharePoint 2013 is relatively new on the marketplace, the presenters have been working with SharePoint 2013 for well over a year, and have implemented it with a number of clients in production environments.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.