Useful Links:

Computer Tweaking & Tuning

Computer Resources

Computer Software

Computer Virus &  Spyware Prevention

Computer Security

Internet Speed        Testing

XP Services

Health Issues

Online Trip Planning

Online Classifieds

Misc Information

Members Area

Downloads  

Windows XP Service Configuration

Introduction

For the most part, Microsoft took 3 years to create a "default" configuration for Windows XP Services that took me only one month to test and post on July 28, 2001. Several services that I previously recommended to be disabled are either gone or disabled by default after the installation of Service Pack 2.

An * (asterisk) indicates changes from Service Pack 1a to Service Pack 2.

Notes for a Happier Computer and User

• Do NOT use "msconfig" to disable services, type "services.msc" in the Run box instead! (WHY?)
• Before disabling ANY service, check out the service information about each by selecting the service name links provided.
• Service settings are global, meaning changes apply to all users.
• An "*" (asterisk) indicates changes from Service Pack 1a to Service Pack 2.
• Additional recommended configuration settings besides "Safe" is located on the Windows XP Services Configuration page.
• For an easy method of creating multiple Service Configurations, please check out the Windows XP Services Profile Guide.
• All of these services are "Standard" with Windows XP after the installation of Service Pack 2. If you discover something other than these listed here running, another program installed them. View a listing of the more common ones.
• Still unsure? Put your setting to "manual" or the listing under "Safe." Manual allows Windows XP to start the service when it needs to (or when ever it feels like it), but not at boot up. Depending on your configuration, not all services will start when required while in "Manual" mode. If you find you need a service, place it in Automatic.
• After adjusting your service settings, reboot your computer.
• If you do not have some of these services listed, do not panic! If your computer manufacture "pre-installed" your XP, they choose not to have certain services installed for you. This is, in most cases, a fact with OEM versions of Windows XP Home.
• Before E-Mailing me, see if your question has been addressed in the FAQ!
• More items about how to speed up your system can be found on the Windows XP Super Tweaks Page!
• Disabling all of the "unneeded services" frees up 12-70 MB of RAM, depending on system.
• Do you mean that out of 87 (Home), 96 (Pro) services, 32 (Home), 34 (Pro) are set to Automatic as DEFAULT, but, we MAY only need 6 running?!? YES.
• Viewing Instructions: If the information is hard to read, please check out your viewing options.
• Printable Version: A printable version will be posted as soon as all information is updated.

Configuration Information

• DEFAULT Home ~ What Bill G. thinks should be running on Windows XP Home.
• DEFAULT Pro ~ What Bill G. thinks should be running on Windows XP Professional.
• "SAFE" Configuration ~ This is the configuration that 95% of the people will be able to use with little or no side effects. It will also minimizes the amount of "errors" that is reported in the Event Viewer. This does not guarantee it will work for you, but if adjusting your services scares you, this configuration would be a good starting point.
• Dependencies ~ Describes what other services this service needs to run as reported in the services.msc control panel.
• Automatic ~ With a service in this state, it will start at boot time. Some services, when no longer required, will also automatically stop when not needed. However, this is very rare. If you find you do not need a service, place it into Manual or Disabled.
• Manual ~ Manual mode allows Windows to start a service when needed. However, very few services will start up when required in Manual mode. If you find you need a service, place it into Automatic.
• Disabled ~ This setting will stop a service from starting, even if needed. Errors in the Event Viewer will show up complaining of that fact. Some services, while Disabled, will constantly complain. However, this situation is taken care of if placed in Manual. The service descriptions identifies those that should be in Manual vice Disabled.

This information was originally created and belongs to Black Viper (Dead link, obviously). We have reproduced it, in large part until the original website returns, if ever.

1. Do not use msconfig to disable services. Type in the Run box "services.msc" instead!
2. Before disabling ANY service, check out the information listed about each service by clicking on the name.
3. Only disable a few services at a time to avoid changing "50" settings and trying to figure out "what broke it."
4. Still unsure? Put your setting to "manual" or the listing under "Safe." Manual allows Windows XP to start the service when it needs to (or when ever it feels like it,) but not at boot up. NOTE: Depending on your configuration, not all services will start when required while in Manual mode. If you find you need a service, place it in Auto.
5. After adjusting your service settings, reboot your computer.
6. If you do not have some of these services listed, don't panic! If your computer manufacture "pre-installed" your XP, they choose not to have certain services installed for you.

Notes

• Display Name ~ Is how it is displayed in the Services Control Panel
• Service Name ~ Is what the service is called, usually the "short" name
• Process Name ~ Name of the Process running in the background (displayed in Task Manager by hitting Ctrl+Alt+Del)
• Dependencies ~ What other services this service needs to run
• Need it? ~ From what I have concluded by trial and error and also the services that I have found pointless.
• MINE ~ My configuration & recommended to start.  Cross between Gaming (Power User) & Safe configuration.
• DEFAULT Pro ~ What Microsoft thinks should be running on Windows XP Professional.
• "SAFE" Configuration ~ This is the configuration that 95% of the people will be able to use with little side effects. It will also minimizes the amount of "errors" that is reported in the Event Viewer. This does NOT guarantee it will work for you, but if you are scared, this configuration should be a good starting point.
• Internet Gateway Configuration ~ Setup to allow multiple computers on a network to share one internet connection access point using Microsoft's "Internet Connection Sharing and Personal Firewall" software. If you do not have this type of setup, compare the differences between "SAFE" and "GAMING" to find a middle ground that works for your system.
• Gaming Configuration ~ The power user setup. DO NOT JUMP RIGHT TO THIS CONFIGURATION. This setup is a system that connects through a network to the internet, provides file and print sharing resources and gaming enjoyment. Some things MAY not function with this setup. No passwords are saved. It is not intended for a computer with analog modems or some DSL/cable connections. Try "Internet Gateway" Configuration first.

• Alerter ~ Notifies users of administrative alerts. Usually not required under normal circumstances. Note: This is NOT "WinPopUp."
  • Dependencies:
    • Workstation
• Application Layer Gateway Service ~ Provides support for 3rd party plug-ins for Internet Connection Sharing/Internet Connection Firewall. Required if using Internet Connection Sharing/Internet Connection Firewall to connect to the internet. This uses about 1.5 MB of memory in an idle state.

• Application Management ~ Used for Assign, Publish and Remove software services. If you cannot modify your software installation of certain applications, put this service in to Automatic or Manual.

• Automatic Updates ~ Used to check up to see if there is any critical or otherwise updates available for download. Requires Cryptographic Services to be running. Place this service in to Automatic if you do not wish to update manually.

• Background Intelligent Transfer Service ~ Used to transfer asynchronous data via http1.1 servers. According to M$'s site, Windows Update uses this "feature." It "continues" a download if you log off or shutdown the system (that is, when you log back in.) Take note: Manual update via Windows Update web site Requires Cryptographic Services to be running.
  • Dependencies:
    • Remote Procedure Call (RPC)
    • Workstation
• ClipBook ~ Used to store information (cut/paste) and share it with other computers. This service alone uses about 1.3 MB of memory.
  • Dependencies:
    • Network DDE
• COM+ Event System ~ You will receive, in the Event Log, a entry from "DCOM" complaining about not having this service running if Disabled. I am unaware of any application that uses COM+, but if set to Manual, many services report to it, so it will start anyway. Required for System Event Notification. For the fun of it, head to
  "C:\Program Files\ComPlus Applications"
  on your system and see if any "COM+" Applications are installed. If not, you can probably disable this service with no side effects (besides the Event Log complaining upon reboots.) Take note: BootVis Requires Task Scheduler and COM+ Event System to be running if you wish to take advantage of the "optimize system" function. Pre-fetching only occurs on boot up, so if you do not care about a few extra seconds of boot time, do not even bother with it and disable Task Scheduler. Windows Media Player may also require this service for some "features" to function. I recommend Disabled for super tweaking, Automatic for "safe" and most other configurations.
  • Dependencies:
    • Remote Procedure Call (RPC)
• COM+ System Application ~ You will receive, in the Event Log, a entry from "DCOM" complaining about not having this service running if Disabled. I am unaware of any application that uses COM+, but if set to Manual, many services report to it, so it will start anyway. For the fun of it, head to:
  "C:\Program Files\ComPlus Applications"
  on your system and see if any "COM+" Applications are installed. If not, you can probably disable this service with no side effects (besides the Event Log complaining upon reboots.) Required for System Event Notification.
  • Dependencies:
    • Remote Procedure Call (RPC)
• Computer Browser ~ Maintains a listing of computers and resources located on the network. This service is not needed on a standalone system.
  • Dependencies:
    • Server
    • Workstation
• Cryptographic Services ~ Mainly, it confirms signatures of Windows files. You may always get a dialog box complaining about uncertified drivers if this is disabled. Required for Windows Update to function in manual and automatic mode. Windows Media Player may also require this service for some "features" to function. This service uses about 1.9 MB of memory.
  • Dependencies:
    • Remote Procedure Call (RPC)
• DHCP Client ~ Receives a Dynamic IP address from your DHCP server. Required for ICS/internet client and also if you run IPSEC, disable on a standalone system or one that has a static IP address. Take note: Most DSL/cable providers use DHCP to provide internet access. If you disable this service and your internet no longer works, place this back into automatic.
  • Dependencies:
    • AFD Networking Support Environment
    • NetBios over TCP/IP
    • TCP/IP Protocol Driver
• Distributed Link Tracking Client ~ Maintains links with NTFS files within your computer or across a domain. Even though this is rather valuable on a large network, I have not found a use for this service. It uses about 3.5 MB to 4 MB in an idle state.
  • Dependencies:
    • Remote Procedure Call (RPC)
• Distributed Transaction Coordinator ~ Takes care of transactions that span multiple resources. Required if using Message Queuing. You may also see complaints in the Event Log if this service is disabled, but I have experienced no side effects.
  • Dependencies:
    • Remote Procedure Call (RPC)
    • Security Accounts Manager
• DNS Client ~ Resolves and caches DNS names and Active Directory domain controller functions. This service is not needed, but if it makes you happy to have it running, go ahead. Required if using IPSEC. If you attempt to "repair" your network connection and a dialog box complains that the "DNS resolver failed to flush the cache," this service is the reason.
  • Dependencies:
    • TCP/IP Protocol Driver
• Error Reporting Service ~ Calls home to Micro$oft when application errors occurs. A waste of memory and resources. You can do it if you wish.
  • Dependencies:
    • Remote Procedure Call (RPC)
• Event Log ~ Allows Event Log messages from applications to be viewed in Event Viewer. Always helpful to check out the Event Log to see what problems with applications are popping up that is "hidden" from the normal user. Before tweaking your services, you may consider clearing the Event Log to quickly see what, if anything, has resulted in your adjustments. Windows Management Instrumentation also Requires Event Log Service to be running. If you disable the Event Log Service, but do not disable Windows Management Instrumentation, your computer may have an extended boot time while Windows Management Instrumentation is waiting for the Event Log to start. It is just best to keep this service active.

• Fast User Switching Compatibility ~ Unless you have many users on a system, you probably do not even need this service to be running. You could, however, benefit greatly if you use this service in conjunction with Remote Desktop.
  • Dependencies:
    • Terminal Services
• Fax Service ~ Not installed by default, but if needed, you may install it later off of the WinXP CD.
  • Dependencies:
    • Plug and Play
    • Print Spooler
    • Remote Procedure Call (RPC)
    • Telephony
• FTP Publishing Service ~ Not available on Windows XP Home. Not installed by default on Windows XP Pro, but if needed, you may install it later off of the WinXP CD. Used to provide a FTP server on your network.
  • Dependencies:
    • IIS Admin
• Help and Support ~ Required for Micro$ofts online help documents. If you ever "attempt" to use Help and Support, this service will be placed back into "Automatic" even if you already placed this service on Disabled.
  • Dependencies:
    • Remote Procedure Call (RPC)
• Human Interface Device Access ~ I have no peripherals that require this service. If one of yours magically does not function anymore, set it to Automatic. Namely, scanners with function buttons (fax, copy) or even a keyboard with volume or play controls.
  • Dependencies:
    • Remote Procedure Call (RPC)
• IIS Admin ~ Not available on Windows XP Home. Not installed by default on Windows XP Pro, but if needed, you may install it later off of the WinXP CD. Usually used in conjunction with local web site or FTP servers. Leave it uninstalled mainly because IIS has been "popular" for hackers to break.
  • Dependencies:
    • Remote Procedure Call (RPC)
    • Security Accounts Manager
• IMAPI CD-Burning COM Service ~ Used for that cool "drag and drop" CD burn capability. You will need this service to burn CD's. If set to Manual, the service starts and stops itself when used with some software packages. Practically the only service that does do this! If you still cannot burn a CD with it on Manual, switch to Automatic and feel safe. My best guess is that this takes up about 1.6 MB of memory in an idle state.

• Indexing Service ~ This has always and forever been a major resource hog. I never recommend having this service enabled. Remove the function via the "Add/Remove Programs" icon in the control panel (Windows Setup Programs.) It uses about 500K to 2 MB in an idle state, not to mention the amount of memory it takes to actually INDEX the drives.
  • Dependencies:
    • Remote Procedure Call (RPC)
• Internet Connection Firewall and Internet Connection Sharing ~ Used to allow multiple computers on your network to access the internet via only one account. This service is installed on the "modem" computer. If you are using a 3rd party firewall or Internet Connection Sharing software package, this service is not required.
  • Dependencies:
    • Application Layer Gateway Service
    • Network Connections
    • Network Location Awareness
    • Remote Access Connection Manager
• IPSEC Services ~ May be required on some domains, but the "average" user will not need this.
  • Dependencies:
    • IPSEC driver
    • Remote Procedure Call (RPC)
    • TCP/IP Protocol Driver
• Logical Disk Manager ~ Vital to run the Disk Management MMC console for dynamic volumes. If you attempt to "Manage" your hard drives and a dialog box pops up complaining about not being able to do this, start this service. If you think I am being vague, I am. :)
  • Dependencies:
    • Plug and Play
    • Remote Procedure Call (RPC)
• Logical Disk Manager Administrative Service ~ Vital to run the Disk Management MMC console for dynamic volumes.
  • Dependencies:
    • Logical Disk Manager
    • Plug and Play
    • Remote Procedure Call (RPC)
• Message Queuing ~ Not available on Windows XP Home. Not installed by default on Windows XP Pro, but if needed, you may install it later off of the WinXP CD. May be used on some domains, but the "average" home user will never need this service.
  • Dependencies:
    • Distributed Transaction Coordinator
    • Message Queuing access control
    • NT LM Security Support Provider
    • Reliable Multicast Protocol driver
    • Remote Procedure Call (RPC)
    • Server
• Message Queuing Triggers ~ Not available on Windows XP Home. N