14 DAY TRIAL // Driver installation issues represent an inherent result in the evolution of the code in Windows Vista in comparison with Windows XP. The fact of the matter is that the modifications introduced to Windows Vista affect the driver for approximately all device classes. Microsoft argued that all changes were implemented for the sake of security and reliability and that driver issues are a necessary trade-off.
A common issue with driver installation failures is associated directly with the driver package which lacks nonsystem driver files. "All driver files that are referenced in the INF must be in the package. Driver files-except those that are part of the operating system-must be imported into the driver store before the package can be installed. All nonsystem driver files that the INF references must be in the driver package. If not, the driver files are not successfully imported into the driver store and installation fails," informed Microsoft.
Additionally, there are problems concerning the installation of class installers and co-installers. According to Microsoft, there are two general sources of deployment failures. Some problems are related to the device installations that occur in an interactive system context. Windows Vista requires class installers and co-installers not to display a user interface with the exception of the finish-install action. Also, Windows Vista no longer attempts a client-side install in a scenario where the system-based install would return an error code. Microsoft revealed that its latest operating system no longer supports client-side installs.
Last but not least, user intervention is decisive in the success of a driver installation in the context of the user Account Control. Drivers that use finish-install actions will fail to deploy if the user does not allow for the elevation of privileges.