Why Windows 2008 driver installation failed and how to fix it

Hopefully this will help your friends to successfully install drivers that use a variety of devices in a Windows Server 2008 system Environment!

　　Find out why the installation failed

In general, when we place the driver installation disc of the target device correctly on the physical optical drive of the Windows Server 2008 system, the system can automatically eject the Driver Installation wizard window and start installing the driver for the target device, because there is often a name in the root directory of the driver installation disc called " Autorun.ini ", when you open the file with a text-editing program such as Notepad, we see a command code that contains" Open=setup.exe "or" open=install.exe ", which means that the command code is actually run automatically" Setup.exe "program or" Install.exe "program.

Similarly, when we use the manual method to install the target device driver, often is to open the root of the driver installation CD window, then find the "setup.exe" program or "Install.exe" program, and double-click them with the mouse to open the Device Driver Installation wizard window, Follow the wizard prompts to start the driver installation of the target device step-by.

Obviously, the Windows system needs to perform a "setup.exe" or "Install.exe" program, regardless of whether the driver for the device is installed in an automated or manual manner. However, in a Windows Server 2008 system environment, to successfully run executables such as "Setup.exe", "Install.exe", you must first pass the compatibility test for Windows Server 2008 systems if Windows The Server 2008 system also has the user Account Control feature enabled, that is, when the UAC feature is enabled, it must also be controlled by the UAC feature, and if one of the levels does not pass, then "Setup.exe", "Install.exe" Executable cannot be executed successfully, the Driver Installation wizard window of the target device will naturally not appear, and we will not be able to successfully install the driver for the target device.

　　Coping with installation failures Puzzle Board

From the above description, it is not difficult to see, in the Windows Server 2008 system environment can not successfully use the original capable device, mainly when the device driver is installed, the target driver cannot successfully through the Windows Server 2008 System level certification, these newly added level certifications are also designed to protect the operational security of Windows Server 2008 systems. After finding out why the driver installation failed, we were able to take targeted steps to get around the Windows Server 2008 system's level certification to get the driver installed successfully.

1. Remove the level limit

Since the drivers for the device are subject to compatibility restrictions or UAC control restrictions in the Windows Server 2008 system environment, we can set up the Windows Server 2008 system manually before installing the device driver. To have all of the various level restrictions that have been enabled have been canceled, here is the specific setup step:

First log on to the Windows Server 2008 System desktop as a system administrator, click Start/Run, enter the string command "msconfig" in the popup system run text box, and click Enter to open the Windows Server 2008 Utility Configuration window of the system;

Next, in the Utility Configuration window, click the Tools tab, open the Option Settings page shown in 1, find the "Disable UAC" option, and click the "Start" button under this option, so that we can install the device driver in the Windows Server 2008 system later, The User Account Control Prompt window does not appear automatically on the system screen, then the UAC control level is successfully canceled;

We will then need to cancel the compatibility level limit, and when we do this, we can put the target device's driver installation disc correctly in the physical optical drive of the Windows Server 2008 system, and then open the root window of the driver installation CD and find a similar "setup.exe" , "Install.exe" and other executables, and right-click the target file, from the Pop-up shortcut menu to execute the "Properties" command, open the target executable file's property Settings dialog box, click the "Compatibility" tab of the Settings dialog box, open the Label Settings page 2, on the Settings page " Compatibility mode settings, check the "Run this program in compatibility Mode" option, select the "Windows XP (Service Pack2)" option or other related options from the drop-down list of the corresponding options, and below, we also need to set the "privilege level" setting in the tab Settings page shown in Figure 2. Select the "Run this program as an administrator" option, and then click the OK button to save the above settings, so that the driver for the target device is successfully installed in the Windows Server 2008 system.

2. Bypassing the level limit

Because the various level limits of the system work when running executables in a Windows Server 2008 system environment, in order to bypass the system level limit, we can try to use the INF file to complete the installation of the device driver.

Generally speaking, the driver files of the device are often saved in the "driver" subdirectory under the root of the drive disc, so we can open the root window of the drive CD directly by hand, then go to the "Driver" subdirectory window, Most of the INF files found are valid device driver files. If using the manual method cannot find a valid INF file from the drive CD, it is likely that the device's driver file is hidden in the drive CD in a compressed package, for example, hidden in the cab, ZIP, RAR and other compressed package, at this time we may wish to use professional decompression tools in turn Open these compressed package files to find the driver files for your device. If the driver for the device was previously installed, even if the installation was unsuccessful, the driver installation file for the device might have been released and saved to a specific temporary folder on the system. In general, we can directly in the Windows Server 2008 System's command-line work window, execute string command "set Temp", you can quickly open the system-specific temporary folder window, carefully in this folder window search device driver file, You might be able to find a valid INF file.

Once a valid device driver INF file is found, we can now attempt to reinstall the driver for the target device by manually adding the hardware device, in which case we can click Start/settings in turn on the Windows Server 2008 system desktop. Control Panel command, in the pop-up System Control Panel window, double-click on the "Hardware and sound" icon, then click "Device Manager" option in the pop-up Device Manager window, clicking on the "Action"/"Add Outdated Hardware" command, open the Hardware Device Add Wizard dialog box, select each one according to the wizard prompt. "Install the hardware (advanced) I manually select from the list" option, the "Show All Devices" option, when the 3 Wizard Setup window appears, we can click the "Install from disk" button, and the file selected after Select the INF file that we found in the driver installation CD and then follow the onscreen prompts to complete the remaining installation.

However, if the device driver cannot be successfully installed on a Windows Server 2008 system through the method above, it is likely that the driver for the specified device is not suitable for installation in a Windows Server 2008 system environment. At this point we can try to search the web for a newer version of the driver that is compatible with Windows Server 2008, and then reinstall it by following the steps above, believing that we will probably be able to successfully install the driver for the target device to Windows Server 2008 in the system.

　　Device-Driven Installation summary

Of course, some device drivers are lucky enough to be installed in a Windows Server 2008 system, but we still cannot guarantee that the corresponding driver will work stably in the future because Windows Server 2008 systems often require digital signature authentication of the drivers installed into them, and device drivers that are not digitally authenticated may later affect

The operating stability of the Windows Server 2008 system. In order to ensure that the system can operate stably, we should try to use the device driver which has already passed the digital signature authentication, if we need to install the device driver without digital signature authentication because of the work, we should also remember these unstable drivers. When you have a digitally signed device driver on hand, you must replace it with the new device driver in a timely manner. In fact, in the Windows Server 2008 system environment, we can use the verifier command to quickly see which devices in the corresponding system are not digitally signed authentication of the driver, in this operation, we can click the Windows Server 2008 the start/Run command in the System desktop, enter the verifier command in the system Run box that pops up, click Enter to open the Driver Verification Manager window, select the Create standard setting option in the Manager window, click the Next button, and then select Select the unsigned drivers automatically option, click the Next button, and then follow the onscreen prompts to complete the other actions. During the validation process, the Windows Server 2008 system will force the Windows Server 2008 system to digitally sign if it sees a device driver that has not been digitally signed for authentication on the corresponding computer.

Why Windows 2008 driver installation failed and how to fix it