The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.
In beta testing for the Microsoft Windows Vista operating system, the Windows development teams are observing driver installation failures as reported to Microsoft through Windows Error Reporting. The error reports are revealing many driver packages that are not compatible with Windows Vista.
Important: Verify that your driver packages are compatible with Windows Vista. In particular, check for the common errors that are listed in this paper, which can be identified by entries in the Setupapi.dev.log files.
Download the paper for details about the Setupapi log entries and the related erroneous INF file entries for the following issues:
80070002: ERROR_FILE_NOT_FOUNDSolution: Make sure the all files that are specified in the INF file are included on the driver package, and delete any INF file entries that specify nonexistent files.
80070003: ERROR_PATH_NOT_FOUNDSolution: Ensure that all tag-file references specify existing paths and are stated in the correct format: Winxp.dll = 1, WinXP\correctpath.
80070005: ERROR_ACCESS_DENIEDSolution: Ensure that the driver package has appropriate ACLs set for the path and all files.
800F0233: SPAPI_E_INVALID_TARGETSolution: Ensure that the tag-file reference in [SourceDisksNames] is correct, including subdirectory references. Do not use an absolute path.
8028006E: CMIeInfInvalidSourcePathSolution: Ensure that the subdir value that is specified in [SourceDisksFiles] correctly lists a subdirectory in the root of the driver package.
00000002: ERROR_FILE_NOT_FOUNDSolution: Ensure that all files that are referenced in the INF file or in the co installer are present in the driver package.
000005B3: ERROR_REQUIRES_INTERACTIVE_WINDOWSTATIONSolution: Solve the root cause problem that requires an interactive window station.
000005B4: ERROR_TIMEOUTSolution: Plug and Play times out if device installation takes more than 5 minutes. The root cause of this failure varies.
E0000217: SPAPI_E_BAD_SERVICE_INSTALLSECTSolution: Ensure that all description of the AddService directive in the Services section (such as DDInstall.Services section) is correct, and ensure that the binary file that is described in the AddService directive is present on the system.
E0000219: SPAPI_E_NO_ASSOCIATED_SERVICESolution: Ensure that all description of the AddService directive in the Services section (such as DDInstall.Services section) in the INF file is correct.
E0000234: ERROR_DRIVER_NONNATIVESolution: Ensure that the service binary is compatible with the platform (such as NTAMD64) on which your machine is running.
E0000246: ERROR_DEVICE_INSTALLER_NOT_READYSolution: This error is exposed intentionally by a class installer or a co installer when some components on which the class installer or a co installer depends do not run.
