Hyper-V Integration Services installation problem
You need to install Hyper-V Integration Services (VMGuest driver) into guest machine in order to enjoy the feature of Hyper-V. Here is the basic troubleshooting procedure.
During the installation of Hyper-V Integration Services, you might get the follwong error:
An error has occurred: Internal Error
You would not be able to proceed further no matter how many times you restart the server. Below are the steps to diagnose the source of the problem:
1. Check the log file in %Windir%\vmguestsetup.log of the guest machine. Below is the sample:
| Hyper-V Integration Services Installer version 6.1.7600.16385 MUI file loaded Parsing command line… Command line parsing complete Application Directory = E:\support\x86 ServicingMode = 0 ##### START: VERIFY SYSTEM ENVIRONMENT OS Version = 5.2 OS SP Level = 2 OS Platform ID = 2 OS Product Type = 3 Edition ID = 0x0 Processor Arch = 0 Processor Count = 1 System Language = en-us (ENU) Windows Dir = C:\WINDOWS System Dir = C:\WINDOWS\system32 Drivers Dir = C:\WINDOWS\system32\drivers System MUI Dir = C:\WINDOWS\system32\en-us Drivers MUI Dir = C:\WINDOWS\system32\drivers\en-us ##### END: VERIFY SYSTEM ENVIRONMENT – Exit code = 0x0 Starting the restart dialog killer thread RestartDialogCaption = System Settings Change Restart dialog handler ready Creating progress dialog Dialog created ProgressMessage = 49413 Creating worker thread Worker thread created ##### START: UPDATE HAL Waiting for worker thread HAL found at C:\WINDOWS\inf\hal.inf ##### END: UPDATE HAL – Error code = 0x0 ##### START: INSTALL KMDF About to load DLL E:\support\x86\WdfCoInstaller01007.dll About to call preinstall Preinstall failed with error 0000F0DA ##### END: INSTALL KMDF – Error code = 0xF0DA Detected worker thread exit Worker thread error code = 0000F0DA Exit code = 0xEA60 |
2. Check the wdf log file in %Windir%\wdf01007Inst.log in the guest machine. Below is the sample
| [Wdf01007Inst.log] 0.750: ================================================================================ 0.750: 2010/11/25 16:03:16.578 (local) 0.750: d:\9b7f85558a86c9988c6b5615\update\update.exe (version 6.3.4.1) 1.250: Hotfix started with following command line: /quiet /o /ER 1.312: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2 1.375: C:\WINDOWS\system32\DRIVERS\wdf01000.sys is Not Present 1.375: First Condition in Prerequisite.FilecheckOrOp.Section Succeeded 1.375: Condition succeeded for section Prerequisite.FilecheckOrOp.Section in Line 1 of PreRequisite 3.703: InstallInfCatalogFile: Installing d:\9b7f85558a86c9988c6b5615\update\Wdf01007.cat as _000000_.cat… 3.703: VerifyTargetFileSize: Unable to verify size as Source = NULL for file c:\windows\_000000_.cat 3.765: InstallCatalogFile: InstallCatalog failed for c:\windows\_000000_.cat; error=0xfffffae7. 3.765: InstallInfCatalogFile: Installation failed; error=0x00000002. 3.765: IsInfFileTrusted: ValidateSingleFileSignature Failed: STR_FAILED_INF_INTEGRITY 3.765: Wdf01007 Setup encountered an error: Setup could not verify the integrity of the file Update.inf. Make sure the Cryptographic service is running on this computer. 3.875: DeleteCatalogFile _000000_.cat failed with ERROR -1305 3.875: CleanupTrustedInfFile: GetFileAttributes for C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem29.cat failed: 0x2 3.875: Setup could not verify the integrity of the file Update.inf. Make sure the Cryptographic service is running on this computer. 3.875: Update.exe extended error code = 0xf0da |
Solution:
In the above sample, it seem like the Cryptographic service is having problem. Below are the steps I perform:
1. Check the Cryptographic service startup status – Started
2. It seem like the log/database corruption exists in the %Systemroot%\System32\catroot2 that cause the Cryptograhic problem. Here is the detail steps:
To rename the Catroot2 folder, follow these steps:
|