Win2008 install driver is not a troublesome master

Users who use win2008 system will find such a problem, in the win2008 system environment, to successfully install the device program is not so easy, always encounter This or another problem causes the driver installation to fail. What is the cause of this? How to solve it?

Finding the reason for the installation failure

Generally, when we target the device After the driver installation CD is correctly placed in the physical CD-ROM drive of the Windows Server 2008 system, the system can automatically pop up the driver installation wizard window to start the driver of the target device. This is because there is often a name in the root directory of the driver installation CD. “Autorun.ini” file, when opening the file with a text editor such as Notepad, we will see the command code including "ld=;open=setup.exe” or “open=install.exe” The meaning of the command code is to automatically run the "setup.exe" program or "install." Exe” program.

Similarly, when we use the manual method to install the driver of the target device, it is often first to open the root directory window of the driver installation CD, and then find the "setup.exe" program or "ld"; .exe & rdquo; program, and double-click them with the mouse, open the device driver wizard window of the device, and then follow the wizard prompts to start the driver installation of the target device step by step.

Obviously, Windows systems need to execute the "setup.exe" program or the "install.exe" program regardless of whether the device is installed automatically or manually. However, in the Windows Server 2008 system environment, in order to successfully run executable files such as "setup.exe", "install.exe", you must first pass the compatibility test of Windows Server 2008 system, if Windows Server 2008 When the user account control function is enabled, that is, when the UAC function is enabled, it must also be controlled by the UAC function. If one of the levels does not pass, then “setup.exe”, “setup.exe”, ““install.exe” The executable file of the class can not be successfully executed, then the driver installation wizard window of the target device will naturally not appear, and of course we can not successfully install the driver of the target device.

Response to the installation failure puzzle

From the above description, we can easily see that the reason why the original normal device can not be used smoothly in the Windows Server 2008 system environment, mainly in the installation When the device driver is used, the target driver cannot successfully pass the level authentication of the Windows Server 2008 system. These newly added level certificates are actually set to protect the operational security of the Windows Server 2008 system. After finding the specific reasons for the failure of the driver installation, we can take targeted measures to try to bypass the level certification of the Windows Server 2008 system, so as to achieve the purpose of successfully installing the driver.

1. Cancellation of Level Limits

Since the driver of the device is subject to compatibility restrictions or UAC control restrictions in the Windows Server 2008 system environment, we can use the device driver before installing it. Manually set up the Windows Server 2008 system, so that all the various level restrictions that have been enabled are canceled. The following are the specific setup steps:

First log in as the system administrator to enter the Windows Server 2008 system desktop, click “Start”/“Run” command, enter the string command "msconfig" in the pop-up system run text box, click the Enter key to open the Windows Server 2008 system utility configuration window;

Next, click the “Tools” tab in the utility configuration window to open the option settings page shown in Figure 1, and find the “Disable UAC” option and click “&” under the option. ;start & rdquo; button, so when we install device drivers in Windows Server 2008 system, the system Would not have User Account Control prompt window automatically appears on the screen, the UAC control level was successfully removed;

Then we also need to remove barriers compatibility restrictions; during this setting operation When we can correctly put the driver installation CD of the target device into the physical CD-ROM drive of Windows Server 2008 system, then open the root directory window of the driver installation CD, and find something like “setup.exe”, “install.exe”. Such as the executable file, and right-click the target file, execute the "Properties" command from the pop-up shortcut menu to open the property setting dialog box of the target executable file; click the "Settings dialog box" Sexuality & rdquo; tab, open the label settings page shown in Figure 2, in the settings page of the "Compatibility Mode" setting, select "Run this program in compatibility mode" option, while pulling down from the corresponding option Check the "Windows XP (Service Pack 2)" option or other related options in the list; below, we also need Figure 2 On the tab settings page, click the “Privilege Level” setting item, select the “Run this program as administrator” option, and finally click the “OK” button to save the above settings. The target device driver can be successfully installed on the Windows Server 2008 system.

2. bypass the checkpoint restrictions

Due to run an executable file in the Windows Server 2008 system environment, the various levels of the system will work restrictions, in order to bypass the system Level restrictions, 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 directory of the driver CD, so we can manually open the root directory window of the driver CD manually. Go to the "driver" subdirectory window and the inf file found from it is mostly a valid device driver file. If you can't find a valid inf file from the driver CD using the manual method, it is likely that the device's driver file is hidden in a compressed package of the driver CD, for example, hidden in CAB, ZIP, RAR and other compression packages. Now, we may wish to use the professional decompression tool to open these zip files in turn to find the driver files of the device. If we have previously installed the device driver, even if the installation operation is not successful, the device driver installation file may have been released to a specific temporary folder in the system. In general, we can directly open the system-specific temporary folder window by executing the string command “set temp” in the command line working window of the Windows Server 2008 system, and carefully search in this folder window. The driver file of the device may find a valid inf file.

Once we find a valid device driver inf file, we can now try to reinstall the driver of the target device by manually adding the hardware device. In this installation operation, we can In the Windows Server 2008 system desktop, click the “Start”/“Settings>;&&quoquo;Control Panel” command, in the pop-up system control panel window, double-click the "Hardware and Sound" in the window. Icon, then click on the “Device Manager” option. In the pop-up Device Manager window, click the “Operate” button to open the Hardware Device Add Wizard dialog box. Prompt to select one by one; install the hardware (advanced) option selected by the manual from the list, < display all devices" option, when the wizard setting window shown in Figure 3 appears on the screen, we can click on it. The "Install from Disk" button, in the file selection dialog that appears later, we will install the light from the driver before Find out inf file is selected and joined in, then follow on-screen prompts in order to complete the remaining installation operations on it.

However, when if the above method does not yet make the device driver to successfully install Windows Server 2008 systems, it is likely to be the driver for the specified device is not suitable for the system environment in Windows Server 2008 Under the installation, at this time we can try to search the Internet for a new version of the driver compatible with the Windows Server 2008 system, and then follow the above steps to re-install, I believe that we can successfully target the driver of the target device. Installed into the Windows Server 2008 system.

The win2008 system will often perform digital signature verification on the drivers installed. This is to better enable the system to run stably. If some device drivers that do not pass digital signature authentication will still have an impact. I hope that Xiaowen can help users of win2008 system.