1. The TechNet article "Application and Service Tools" provides a list of tools useful for troubleshooting applications and services, and information concerning them.
2. The article [Q316434] discusses the issues that can occur because of an incompatible or corrupted program and how to perform advanced clean-boot troubleshooting to determine whether the problem is:
? affiliated with the core operating system
? with a program that is loading in the Windows environment.
3. The TechNet article "Using Service Tools to Diagnose and Resolve Startup Issues" discusses three tools that can help troubleshoot services. The System Configuration Utility (Msconfig), Services snap-in (Services.msc), and SC (Sc.exe) - a command-line tool that displays information about running services.
4. "Determining Which Services and Processes to Temporarily Disable" is the question which this TechNet article may help you with. It describes and discussing methods for determining which services and processes to temporarily disable that varies from one computer to the next.
5. "Services" (click to see an example screenshot) are programs that run when the computer is booted and continue to run as they aid system functionality. You will find many services loaded and are simply not needed which take up memory space and CPU time. Circumventing those unneeded services will free up system resources and speed up overall computer operation.
a. Click Start, Run type services.msc and then press Enter.
b. The Services applet will load listing services currently in session/use. What you have to consider/decide is which service(s) is/are not right for you -- good luck.
6. The article [Q830071] warns that the following problems can occur if the Remote Procedure Call Service is disabled and provides the steps to troubleshoot the issue(s):
? You cannot move icons on the desktop
? You cannot view event log entries
? You can open the Services Microsoft Management Console (MMC), but you cannot see any services listed.
7. To configure how a service is started:
a. Open Services and right-click the service to configure, and then click Properties.
Note: Read and understand the information "Default settings for services."
b. On the General tab, in the Startup type box, click either Automatic (that is, they start automatically when the system starts or when the service is called for the first time), Manual, or Disabled.
c. To specify the user account that the service can use to log on, click the Log On tab, and then do one of the following:
(1) To specify that the service uses the LocalSystem account, click Local System account.
(2) To specify that the service uses the LocalService account, click This account, and then type NT AUTHORITY\LocalService.
(3) To specify that the service uses the NetworkService account, click This account, and then type NT AUTHORITY\NetworkService.
(4) To specify another account, click This account, click Browse, and then specify a user account in the Select User dialog box.
(5) When finished, click OK. Type the password for the user account in the Password box, also in the Confirm password box, and then click OK.
8. Missing Autoplay tab and CD's Don't Autoplay: Since registered components on a system is invoked using the Shell Hardware Detection service and also because non-volume handlers are invoked through it, this service cannot be deactivated. If it is, a user may find they have no access to or can they use either Volume-based or Non-volume-based devices.
a. The primary purpose of Autoplay is to provide a software response to hardware actions initiated by the user on a machine. This feature remained roughly the same from Win95 though W2K and WinME because up until recently there have been very few new scenarios with regard to user-initiated hardware events that could trigger a useful Autoplay action. But lately, with the spread of digital multimedia content (music, graphics, and video) and of the many devices to generate or consume that content, many new scenarios are begging for expansion. In addition to refining the existing Autorun.INF mechanism, audio CD Autoplays, and DVD video Autoplay, support has been added to handle digital music (WMA/MP3), graphics, video, CD burning, video cameras, and other hardware devices.
b. If you've installed software from a CD, you've used an Autorun.INF which the majority of the setup CDs use. The typical user scenario is: a CD is inserted into the CD drive, the setup program runs automatically, and the user simply follows the on-screen instructions generated by the setup software. The Autorun.INF file sample section follows the typical format similar to the following where the first line contains the self-executing Exe file which also contains the text string for an icon. In addition, there could also be values of UseAutoPlay (when present, it will take precedence over the open and ShellExecute values and is intended primarily for use with multimedia content for which Autoplay support was added to Windows XP), label (used to represent the associated drive in the Windows shell), and ShellExecute (works with file associations to run the application associated with the specified file):
c. When determining what actions to suggest or perform in response to an event, Autoplay on WinXP considers the event in conjunction with the various programs registered on a computer. In contrast before, it would always statically run the same application pointed to in the Autorun.INF file, or play an Audio CD or DVD movie using the respective default application. Now, two categories of events are handled:
(1) Volume-based device events are events that affect devices that appear as volumes -- that is, all disk drives accessible via Windows file system APIs. This includes CD drives, removable disk drives, hard disk drives, removable media readers, and mass storage devices. Basically, if it shows up under My Computer with a drive letter, it's a volume-based device.
(2) Non-volume-based devices include, well, everything else. Specific examples of these devices include digital video cameras and portable music players that do not expose their content as a file system supported by WinXP. This does not mean that all video cameras and portable music players are non-volume devices. For example, newer digital cameras and portable music players that use the USB Mass Storage stack are treated as volume devices since they appear to the system as volumes. Digital camera devices which are non-volume devices get special treatment from Windows. Even though they are non-volume devices, they are handled by the Windows Image Acquisition (WIA) component for backward compatibility reasons.
9. Interestiing reading:
a. "Black Viper's Windows XP Services Configurations."
b. "Windows XP Tweaking Guide - VIA/Arena."