Resolving Windows 2008 driver installation failure
I hope that these contents can help friends successfully install drivers for various devices in Windows Server 2008 system environment!
Finding installation failure reasons < Br> Generally speaking, when we correctly put the driver installation CD of the target device into the physical CD-ROM drive of Windows Server 2008 system, the system can automatically pop up the driver installation wizard window and start to install the driver of the target device, because the driver There is often a file named "Autorun.ini" in the root directory of the installation CD. When we open the file with a text editor such as Notepad, we will see that it contains “open=setup.exe” or &ldquo ;open=install.exe” Such a command code, the meaning of the command code is actually 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 "install.exe" Programs, and double-click them with the mouse to 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.
It is obvious that Windows systems need to execute the "setup.exe" program or the "install.exe" program, whether it is an automated method or a manual method to install the device driver. 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.
Responding 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 when installing the device driver. 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. Cancel the level limit
Since the device driver is subject to compatibility restrictions or UAC control restrictions in the Windows Server 2008 system environment, we can manually set up Windows Server 2008 before installing the device driver. The system, so that all the various level restrictions that have been enabled are canceled, the following is the specific setup steps:
First log in as the system administrator into the Windows Server 2008 system desktop, click “ start & rdquo; /& ldquo; 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;
second in the utility configuration window Click the “Tools” tab to open the option settings page shown in Figure 1, and find the “Disable UAC” option, and click the “Start” button next to the option, so that we will be in the future. When installing a device driver on a Windows Server 2008 system, the user account does not automatically appear on the system screen. Control the prompt window, then the UAC control level is successfully canceled;
Then we also need to cancel the compatibility level limit; in this setting operation, we can first install the target device driver CD Properly placed in the physical CD-ROM drive of the Windows Server 2008 system, then open the root directory window of the driver installation CD, find executable files like "setup.exe", "install.exe", and right-click In 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 “Compatibility” tab of the settings dialog box to open as shown in Figure 2. On the label setting page, in the “Compatibility Mode” setting item of the setting page, select the “Run this program in compatibility mode” option, and select “Windows XP (Service Pack 2)” from the drop-down list of the corresponding option. Options or other related options; below, we also need to set the "privilege level" setting on the label settings page shown in Figure 2. At the item, select "Run this program as administrator" option, and finally click the "OK" button to save the above settings, so that the target device driver can successfully run on Windows Server. Successfully installed in the 2008 system.
2. Bypassing the level limit
Because the executable file is run in the Windows Server 2008 system environment, the system's various level restrictions will work. In order to bypass the system level limit, we can try Use the inf file to complete the device driver installation.
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 directly open the root directory window of the driver CD by manual method, and then enter “ldquo; Driver” subdirectory window, 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 you find a valid device driver inf file, we can now try to reinstall the target device driver by manually adding the hardware device. In this installation operation, we can in turn in Windows Server 2008. In the system desktop, click the “Start”/“Settings"&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& Click the “Device Manager” option, and click ““Operation”/“Add Obsolete Hardware” in the pop-up Device Manager window to open the Hardware Device Add Wizard dialog box and select one by one according to the wizard prompts. “Install the hardware (advanced)” option that I manually select from the list, “Show all devices” option, when the wizard setting window shown in Figure 3 appears on the screen, we can click on “ld”; From the disk installation & rdquo; button, in the file selection dialog that appears later, we will look for it from the driver installation CD The inf file that comes out is selected and added, then follow the prompts on the screen to complete the remaining installation operations.
However, if the device driver cannot be successfully installed into the Windows Server 2008 system through the above method, it is likely that the driver of the specified device is not suitable for installation in the Windows Server 2008 system environment. At this point we can try to search the Internet for a new version of the driver compatible with Windows Server 2008 system, and then follow the above steps to reinstall, I believe that we can successfully install the target device driver to Windows. In the Server 2008 system.
Device Driver Installation Summary
Of course, some device drivers are lucky enough to be installed on Windows Server 2008, but we still can't guarantee that the corresponding drivers will work stably in the future, because Windows Server 2008 often Drivers installed into it need to be digitally signed and certified. Device drivers that are not digitally signed may affect the operational stability of the Windows Server 2008 system. In order to ensure that the system can run stably, we should try to use device drivers that have been digitally signed. If we need to install equipment drivers that are not digitally signed and certified due to work, we should also drive these unstable drivers. The program remembers that when you have a digitally signed device driver in hand, you must replace it with a new device driver. In fact, in the Windows Server 2008 system environment, we can use the Verifier command to quickly check which devices in the corresponding system have not been digitally signed. In doing so, we can click Windows Server 2008 system. In the desktop, click the Start & rdquo; /& ldquo; Run & rdquo; command, enter the Verifier command in the pop-up system run box, click the Enter key to open the Driver Verification Manager window; select “ in the Manager window Create the standard settings & rdquo; option, and click the "Next" button, then select the "Automatically select unsigned driver" option, then click the "Next" button, then follow the on-screen prompts Other operations. During the verification process, if the Windows Server 2008 system sees a device driver with no digital signature authentication in the corresponding computer, the Windows Server 2008 system will force digital signature.