Event ID 20003 — Service Installation

Applies To: Windows Server 2008 R2

When you attach a new piece of hardware to your computer, Windows attempts to detect the device type and install a device driver so that Windows can communicate with and control the device.  Sometimes the device driver is accompanied by a service that must run in order for the device and device driver to function properly.

Event Details

Resolve

Examine Status Code Reported in Event

When a service is installed as part of the installation of a device driver, Windows records the service installation attempt as an Event ID 20003 message in the System event log. The message provides the service name of the service being installed and the error code with which the service install process exits.

Services that install successfully log a 20003 event with a status code of 0. Other status codes indicate that the service installation failed for the reason indicated by the status code. To determine the root cause of this condition, examine the status code reported at the end of the event message text. The status code is displayed in decimal (some references quote these values in hexadecimal) and corresponds to Win32 and SetupAPI error codes. Click the link in the list below that corresponds to your status code:

• 0 (0x00000000) Installation successful
• 2 (0x00000002) File Not Found
• 2147942402 (0x80070002) File Not Found
• 2147942403 (0x80070003) Path Not Found
• 2147942405 (0x80070005) Access Denied
• 2148467251 (0x800F0233) Invalid Target
• 2150105198 (0x8028006E) Invalid Source Path
• 1459 (0x000005B3) Requires Interactive Windowstation
• 1460 (0x000005B4) Timeout
• 3758096948 (0xE0000234) Non-native Driver
• 3758096966 (0xE0000246) Device Installer Not Ready
• 3758096919 (0xE0000217) Bad Service Install Section
• 3758096921 (0xE0000219) No Associated Service

For a complete list of Win32 error codes, see https://go.microsoft.com/fwlink/?LinkID=82270 on the Microsoft Web site. A list of SetupAPI error codes can be found in the SetupAPI.h file that is included with the Windows Driver Kit. For more information, see "DDK-Windows Driver Development Kit" at https://go.microsoft.com/fwlink/?LinkId=59546 on the Microsoft Web site.

0 (0x00000000) Installation successful

Cause

The device driver installed successfully.

Solution

There is no error condition reported. No action is required.

2 (0x00000002) File not found

Cause

Windows did not find one or more files for the service in the device driver package, as referenced in the .inf file. This error can occur:

• If the complete device driver package is not copied from the vendor-provided media to the folder location used for installation by the computer.
• If the original .inf file was edited to customize the installation, then there likely is an error in referencing one or more of the required files.

Solution

• Ensure that the complete device driver package is copied to the the folder location used for installatation by the computer.
• If you customize the .inf file, then ensure that all references to files in the .inf file point to the correct folders containing the device driver package files.

2147942402 (0x80070002) File Not Found

Cause

Windows did not find one or more files for the service in the device driver package, as referenced in the .inf file. This error can occur:

• If the complete device driver package is not copied from the vendor-provided media to the folder location used for installation by the computer.
• If the original .inf file was edited to customize the installation, then there likely is an error in referencing one or more of the required files.

Solution

• Ensure that the complete device driver package is copied to the the folder location used for installatation by the computer.
• If you customize the .inf file, then ensure that all references to files in the .inf file point to the correct folders containing the device driver package files.

2147942403 (0x80070003) Path Not Found

Cause

Windows did not find one of the folders referenced in the .inf file. This error can occur:

• If the complete device driver package is not copied from the vendor-provided media to the folder location used for installation by the computers.
• If the original .inf file was edited to customize the installation, then there likely is an error in referencing one or more of the required folders.

Solution

• Ensure that the complete device driver package is copied to the folder location used for installatation by the computer.
• If you customize the .inf file, then ensure that all references to folders in the .inf file point to the correct folders containing the device driver package files.

2147942405 (0x80070005) Access Denied

Cause

File or folder permissions prevented Windows from either reading files from the source location or writing them to the installation destination.

Solution

• If you share service installation packages to client computers from a folder or network share, then ensure that users have read permissions to the appropriate folder location.
• By default, only members of the Administrators group have permission to install services due to the security applied to the folders where services are normally installed, and to the registry entries that must be modified to make a service active.

2148467251 (0x800F0233) Invalid Target

Cause

This error is usually the result of incorrectly editing the .inf file that controls the installation of the service. If you did not edit the .inf file, then contact the vendor of the device for an updated device driver package.

Solution

Ensure that the tag-file value that is specified in the [SourceDisksNames] section of the .inf file is correct, including subfolder references. Use only relative paths, not absolute paths such as c:\folder1\... that might not exist on the client computer.

2150105198 (0x8028006E) Invalid Source Path

Cause

This error is usually the result of incorrectly editing the .inf file that controls the installation of the service. If you did not edit the .inf file, then contact the vendor of the device for an updated device driver package.

Solution

Ensure that the subdir value that is specified in the [SourceDisksFiles] section of the .inf file correctly lists a subfolder in the top-most folder of the device driver package.

1459 (0x000005B3) Requires Interactive Windowstation

Cause

The installation was started in a non-interactive context, such as when a user is not currently logged on to the computer. If the service installation package requires the user to answer any dialog box prompts, then it will fail if started in a non-interactive session. Most service installation packages can be started by using a parameter that specifies an answer file, or by using a command-line parameter that indicates a "silent" install.

Solution

Refer to the documentation provided by the vendor who provided the service installation package for options to make the package work in a non-interactive manner. If the service installation pacakge cannot be made to work non-interactively, then it must be installed by a user logged on to the computer in order to answer the prompts displayed by the installer.

1460 (0x000005B4) Timeout

Cause

Plug and Play times out if service installation takes more than five minutes.

Solution

Investigate any performance issues on the computer that might delay installation processes to the point where they take longer than five minutes. Close other applications, or install the service immediately after restarting the computer so that maximum resources are available and there is minimum competition with other processes.

3758096948 (0xE0000234) Non-native Driver

Cause

The service installation package you are attempting to install is for a different and incompatible type of processor than the one installed on the computer (such as x86 versus x64).

Solution

Ensure that the service installation package is compatible with the processor type in your computer.

To determine the processor type in your computer

1. Click Start, type msinfo32 in the Start Search text box, and then press ENTER.
2. In the left-hand pane, click System Summary at the top of the tree.
3. In the details pane, look at the item System Type.

3758096966 (0xE0000246) Device Installer Not Ready

Cause

A class installer or a co-installer for a service cannot run because a component on which it depends did not run.

Solution

• If you have not modified the device driver package yourself, contact the manufacturer of the device or the driver package to obtain an updated driver package.
• If you customized the device driver package for your deployment, see the Windows Driver Kit at https://go.microsoft.com/fwlink/?LinkId=59546 on the Microsoft Web site.

3758096919 (0xE0000217) Bad Service Install Section

Cause

This error is usually the result of incorrectly editing the .inf file that controls the installation of the service. If you did not edit the .inf file, then contact the vendor of the device for an updated device driver package.

Solution

• If you have not modified the installation package yourself, then contact the manufacturer of the device or the driver package to obtain an updated driver package.
• If you have customized the .inf file, ensure that all instances of the AddService directive in the [Services] section are correct, and then ensure that the binary file that is described in the AddService directive is present on the system.

3758096921 (0xE0000219) No Associated Service

Cause

This error is usually the result of incorrectly editing the .inf file. If you did not edit the .inf file, then contact the vendor of the device for an updated device driver package.

Solution

• If you have not modified the device driver package yourself, contact the manufacturer of the device or the driver package to obtain an updated driver package.
• If you customized the device driver package for your deployment, see the Windows Driver Kit at https://go.microsoft.com/fwlink/?LinkId=59546 on the Microsoft Web site.

Verify

After the installation is completed, examine the event log for a new Event ID 20003 message for the same service.

If the new event has a status code of 0, it indicates a successful installation.

Related Management Information

Service Installation

Core Operating System