10 Windows XP services you should never disable

10 Windows XP services you should never disable

Summary: Guest post from TechRepublic's 10 Things blog.There are dozens of guides out there that help you determine which services you can safely disable on your Windows XP desktop.

SHARE:

Guest post from TechRepublic's 10 Things blog.

There are dozens of guides out there that help you determine which services you can safely disable on your Windows XP desktop. Disabling unnecessary services can improve system performance and overall system security, as the system’s attack surface is reduced. However, these lists rarely indicate which services you should not disable. All of the services that run on a Window system serve a specific purpose and many of the services are critical to the proper and expected functioning of the desktop computing environment. In this article, you’ll learn about 10 critical Windows XP services you shouldn’t disable (and why).

Note: This article is also available as a PDF download. For a quick how-to video on the basics, see Disable and enable Windows XP services.

1: DNS Client

This service resolves and caches DNS names, allowing the system to communicate with canonical names rather than strictly by IP address. DNS is the reason that you can, in a Web browser, type http://www.techrepublic.com rather than having to remember that http://216.239.113.101 is the site’s IP address.

If you stop this service, you will disable your computer’s ability to resolve names to IP addresses, basically rendering Web browsing all but impossible.

2: Network Connections

The Network Connections service manages the network and dial-up connections for your computer, including network status notification and configuration. These days, a standalone, non-networked PC is just about as useful as an abacus — maybe less so. The Network Connections service is the element responsible for making sure that your computer can communicate with other computers and with the Internet.

If this service is disabled, network configuration is not possible. New network connections can’t be created and services that need network information will fail.

3: Plug and Play

The Plug and Play service (formerly known as the “Plug and Pray” service, due to its past unreliability), is kicked off whenever new hardware is added to the computer. This service detects the new hardware and attempts to automatically configure it for use with the computer. The Plug and Play service is often confused with the Universal Plug and Play service (uPNP), which is a way that the Windows XP computer can detect new network resources (as opposed to local hardware resources). The Plug and Play service is pretty critical as, without it, your system can become unstable and will not recognize new hardware. On the other hand, uPNP is not generally necessary and can be disabled without worry. Along with uPNP, disable the SSDP Discovery Service, as it goes hand-in-hand with uPNP.

Historical note: Way back in 2001, uPNP was implicated in some pretty serious security breaches, as described here.

If you disable Plug and Play, your computer will be unstable and incapable of detecting hardware changes.

4: Print Spooler

Just about every computer out there needs to print at some point. If you want your computer to be able to print, don’t plan on disabling the Print Spooler service. It manages all printing activities for your system. You may think that lack of a printer makes it safe to disable the Print Spooler service. While that’s technically true, there’s really no point in doing so; after all, if you ever do decide to get a printer, you’ll need to remember to re-enable the service, and you might end up frustrating yourself.

When the Print Spooler service is not running, printing on the local machine is not possible.

5: Remote Procedure Call (RPC)

Windows is a pretty complex beast, and many of its underlying processes need to communicate with one another. The service that makes this possible is the Remote Procedure Call (RPC) service. RPC allows processes to communicate with one another and across the network with each other. A ton of other critical services, including the Print Spooler and the Network Connections service, depend on the RPC service to function. If you want to see what bad things happen when you disable this service, look at the comments on this link.

Bad news. The system will not boot. Don’t disable this service.

6: Workstation

As is the case for many services, the Workstation service is responsible for handling connections to remote network resources. Specifically, this service provides network connections and communications capability for resources found using Microsoft Network services. Years ago, I would have said that disabling this service was a good idea, but that was before the rise of the home network and everything that goes along with it, including shared printers, remote Windows Media devices, Windows Home Server, and much more. Today, you don’t gain much by eliminating this service, but you lose a lot.

Disable the Workstation service and your computer will be unable to connect to remote Microsoft Network resources.

7: Network Location Awareness (NLA)

As was the case with the Workstation service, disabling the Network Location Awareness service might have made sense a few years ago — at least for a standalone, non-networked computer. With today’s WiFi-everywhere culture, mobility has become a primary driver. The Network Location Awareness service is responsible for collecting and storing network configuration and location information and notifying applications when this information changes. For example, as you make the move from the local coffee shop’s wireless network back home to your wired docking station, NLA makes sure that applications are aware of the change. Further, some other services depend on this service’s availability.

Your computer will not be able to fully connect to and use wireless networks. Problems abound!

8: DHCP Client

Dynamic Host Configuration Protocol (DHCP) is a critical service that makes the task of getting computers on the network nearly effortless. Before the days of DHCP, poor network administrators had to manually assign network addresses to every computer. Over the years, DHCP has been extended to automatically assign all kinds of information to computers from a central configuration repository. DHCP allows the system to automatically obtain IP addressing information, WINS server information, routing information, and so forth; it’s required to update records in dynamic DNS systems, such as Microsoft’s Active Directory-integrated DNS service. This is one service that, if disabled, won’t necessarily cripple your computer but will make administration much more difficult.

Without the DHCP Client service, you’ll need to manually assign static IP addresses to every Windows XP system on your network. If you use DHCP to assign other parameters, such as WINS information, you’ll need to provide that information manually as well.

9: Cryptographic Services

Every month, Microsoft provides new fixes and updates on what has become known as “Patch Tuesday” because the updates are released on the first Tuesday of the month. Why do I bring this up? Well, one service supported by Cryptographic Services happens to be Automatic Updates. Further, Cryptographic Services provides three other management services: Catalog Database Service, which confirms the signatures of Windows files; Protected Root Service, which adds and removes Trusted Root Certification Authority certificates from this computer; and Key Service, which helps enroll this computer for certificates. Finally, Cryptographic Services also supports some elements of Task Manager.

Disable Cryptographic Services at your peril! Automatic Updates will not function and you will have problems with Task Manager as well as other security mechanisms.

10: Automatic Updates

Keeping your machine current with patches is pretty darn important, and that’s where Automatic Updates comes into play. When Automatic Updates is enabled, your computer stays current with new updates from Microsoft. When disabled, you have to manually get updates by visiting Microsoft’s update site.

New security updates will not be automatically installed to your computer.


Check out 10 Things… the newsletter

Get the key facts on a wide range of technologies, techniques, strategies, and skills with the help of the concise need-to-know lists featured in TechRepublic’s 10 Things newsletter, delivered every Friday. Automatically sign up today.

Topics: Networking, CXO, Hardware, Microsoft, Windows

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

98 comments
Log in or register to join the discussion
  • DNS Client?

    bull crap. I always disable this service and have had no problems typing on URL. I see no reason to have that and many other services on.
    znetlol
    • You only need DNS if

      you are not connected to a DNS server????
      kd5auq
      • Interesting list...

        ... I think it is wise to write down or make note of any changes you make to enabled and disabled services. If you have a list to check than disabling printer spoolers are no issue.
        Information_z
    • ZNETLOL IS RIGHT

      @znetlol There is no problem disabling this service. It can pick up garbage from the network, in the case of an environment I am working in, a virus outbreak is poisoning dns cache on client systems and breaking name resolution. This is a rational stop-gap procedure. Also the nature of the process as described here is completely incorrect.
      John Casaretto
  • Leave them alone.

    Unless you have a specific reason for disabling a service you should leave them alone. Given today's computing power you're highly unlikely to gain any noticable performance increase or memory decrease.

    Security is a practical reason but given the built in firewall access to services should be controlled there.

    So why leave it alone? I think the following from the Printer Services sums it up:

    [i]While that's technically true, there's really no point in doing so; after all, if you ever do decide to get a printer, you'll need to remember to re-enable the service, and you might end up frustrating yourself.[/i]

    Disabling services has probably caused many people more grief than benefit.

    And "Patch Tuesday" is the second Tuesday of the month, not the first.
    ye
    • That's the sort of thinking that leads to 80 processes at idle.

      "Hey, the processing power's there. While we're at it, why don't we put in an app to automatically start iTunes, QuickTime, and Adobe Reader so that a user can view a PDF or listen to a song with only a three-second wait instead of four seconds, or an app that allows them to change their volume on the screen instead of with the volume knob on the side of their laptop..."

      And some people wonder why their brand-new system only runs marginally faster than their old P4...
      jrf2027@...
      • I said nothing of applications. My post specifically focused on...

        ...services.
        ye
        • If I don't have a printer...

          ...hooked up to my machine, then there's no reason print spooler should be running in the background. It's a waste of resources.

          I turned mine off a couple of years ago and never looked back
          Wintel BSOD
          • No printer either

            The topic ".. you should never disable" is not right.

            a. I dont have a printer and dont work in Word a lot so this service can be disabled without a problem.

            b. I check for updates myself regularly so this one is not needed also (unless..)

            abbos@...
    • Dont agree

      If you didnt disable some services you system would be full of running services after all installations you have made.

      I put all to manual except the ones really needed by the system. Created a batch file for it so i can stop and start all services when needed.

      True that nowaday systems have enough power to handle all but why should you let your machine run with tons of running services. Not needed and especially not when running heavy games.
      abbos@...
    • I disagree

      Doesn't matter how fast a computer gets, it easily becomes very bogged down with TSRs or pointless crap on your taskbar. Computing power is a finite resource and Windows notoriously mishandles memory anyway.
      rball@...
  • You guys are pitiful. DNS client

    Only deals with cacheing. This below is from XP's description of the DNS client. This is why bloggers suck as journalists. You are a joke and never do your homework.

    The DNS Client service (dnscache) caches Domain Name System (DNS) names and registers the full computer name for this computer. If the service is stopped, DNS names will continue to be resolved. However, the results of DNS name queries will not be cached and the computer's name will not be registered. If the service is disabled, any services that explicitly depend on it will fail to start.
    bjbrock
    • Not conducive to credibility

      I know that ZDnet is all about 'infomercials' and taking money off people to write "opinion pieces" which are nothing short of advertising copy, but many visitors to the site won't know that. Look at the authoritive way in which completely incorrect information is dished out:

      "If you stop this service, you will disable your computer?s ability to resolve names to IP addresses, basically rendering Web browsing all but impossible"

      Ooooh! Scary! Well, it would be, if it was correct. ZDnet "Technical" reporting at its finest.
      whisperycat
      • What do you expect from a Mac fanboi?

        Rarely are the ever right about Windows. Yet they continue writing/posting about it anyway.
        ye
        • Perhaps like [i]any[/i] kind of fanboi?

          Yourself included...
          UsernameRequired
          • I provide accurate and reliable information.

            And I'm not a fanboi.
            ye
          • Really? Since when?

            And yes, it could easily be concluded that you are a Microsoft fanbois.
            zkiwi
          • Everytime I post. Though I'm not surprised you can't...

            ...recognize it. Then you couldn't claim ignorance of all things Microsoft.
            ye
          • He got you, ye

            You can't weasel your way out of that one.
            Wintel BSOD
          • ODFO

            You arrogant sod. They whole confidence in your limited knowledge is
            tiresome. If you only know one system, and rubbish everything else
            based on your own conjecture, you are by very definition a fanboi, you
            are an arrogant one to boot. SSShhhh...
            UsernameRequired