WinXP common system service introduction (1)

Windows XP has a lot of services, many of which are rarely used by ordinary users. Turning off unwanted services saves more system resources and makes the computer run more smoothly. This is very effective on low-profile machines.

If you don't have some of the services mentioned below in your system, don't worry, because some services will only appear in certain states or after installing some hardware and software.

How to Manage Configuration System Services

To properly manage and configure system services, be sure to ensure that you have the appropriate permissions, otherwise some settings cannot be changed. So the most convenient way is to log in with the user in the Administrator group. It is necessary to back up the current state before changing the settings of the service. Once an error occurs, it can be restored to the normal state immediately. Here to introduce the method of directly backing up the service related content in the registry, select "Start → Run", enter "regedit" and press Enter to open the Registry Editor, expand the registry selected "HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Service", click The menu "File" → "Export" will export and save the contents of the registry under this branch into a REG file. If you want to restore the system service to the original state, just double-click this file to import the registry.

If you have backed up the default settings for the service, you can now try changing the service. Those who are familiar with Win98 know that "msconfig" is an important tool for configuring system resources when Win98 starts. In WinXP, considering the user's habits of the previous series of operating systems, this tool disappeared in Win2000 has been retained, so many friends who upgraded from Win98 to WinXP still habitually use it to configure the system. However, this is not desirable for the management configuration of system services. Using "msconfig" can really close and start the background service of the system, but only in the mechanical decision to start or shut down the service, and can not set the three types of system services complete. More importantly, since the basic comment of the system service is not seen in "msconfig", it is easy to cause configuration management service errors in this case. In particular, there are some basic services necessary for the system to boot, such as Remote Procedure Call. The special service management configuration tool Services.msc cannot be closed. Instead, it can be closed with "msconfig", so it is easy to start the system. Mistakes. Therefore, it is better to use the service configuration management tool Services.msc that comes with WinXP to manage the service.

Adjustment method: Enter Services.msc in "Start → Run" and press Enter. In the service configuration tool window, double-click on any service to open the properties panel of the service. Make adjustment management here, start, close or simply disable the service according to your needs by changing the startup type of the service.

Switch to the "General" page of the properties panel of the specific service, "Service Name" refers to the "short name" of the service, and is also the name displayed in the registry, "Display Name" refers to the service configuration The display name of each service in the panel, "Description" is a simple explanation for this service, and the "executable path" is better understood. The next step is the more important "startup type", which is the core of the entire service configuration management. For any service, there are usually 3 different startup types: Automatic, Manual, and Disabled. You can change the startup type of the service as you choose from the drop-down menu. These three types of startup have their own meaning and role.

Automatic (automatic): This service starts with WinXP start with, will extend the time needed to start, some services must be set to automatic, such as Remote Procedure Call (RPC). Due to the influence of dependencies or their nature, other services must also be set to automatic. It is best not to touch such a service, otherwise the system will not work properly.

Manual (Manual): If a service is set to manual, you can run it when needed. Most services are like this, which saves a lot of system resources and speeds up startup time.

Disabled (prohibited): This service is no longer running, even if the system is a must. This setting is generally useful when it comes to improving security. If you suspect that a strange service will pose a security risk to your system, you can try to stop it and see if the system can still run normally. If everything is normal, you can directly disable it. If you need this service in the future, you must first set the startup type to automatic or manual before starting it.

finally "service status", referring to the current state of the service is started or shut down, usually using the "start" following "closed", "pause" and instantly change the status of the service button, but There are two situations where these buttons are grayed out. In one case, the service is set to Disabled, in which case the service can only be used if it is set automatically or manually and "apply". The other case is the basic service that we mentioned above for system startup, such as Remote Procedure Call. Its startup type is set to be automatic and unchangeable. Naturally, the buttons that change the service status are not available.

switch to the "Dependencies" page service properties panel. Some services do not run separately and must rely on (ie, depend on) other services. Before stopping or disabling a service, be sure to look at the dependencies of the service. If there are other services that need to be started, you cannot stop it. For example, in the figure, the Messenger service depends on the other four services to run, so stopping or disabling any of them will prevent the Messenger service from running properly. Another example is the Application Layer Gateway Service. If you turn it off, the Internet Connection Firewall/Internet Connection Sharing that depends on it will not work. So before we turn off a service, it is an essential step to find out its dependencies.