Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

After you deploy a Sysprep prepared image, the Hypervisor layer service does not start automatically in Windows Server 2008


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that has Windows Server 2008 installed together with the Hyper-V role.
  • You run Sysprep on the computer to prepare the installation for image capture.
  • You deploy the captured image.
In this scenario, the Hypervisor layer service does not start automatically.

↑ Back to the top


Cause

This issue occurs because there is no Sysprep provider for Hyper-V. Therefore, the HypervisorLaunchType BCD entry is removed from the Boot Configuration Data (BCD) file when you run Sysprep.

↑ Back to the top


Workaround

To work around this issue, you must use the Bcdedit tool to add the missing entry to the BCD file. To do this, follow these steps:
  1. On the computer where you deployed the image, open a command prompt.
  2. At the command prompt, move to the following directory:
    %Windir%\System32
  3. Type the following command, and then press ENTER:
    Bcdedit /set {current} hypervisorlaunchtype auto
  4. Restart the computer.

↑ Back to the top


References

For more information about the Hyper-V technology, visit the following Microsoft TechNet Web site:

↑ Back to the top


Keywords: kbexpertiseadvanced, kbprb, kbtshoot, kbhyperv, kbsyspreptool, kbdeployment, kb, kbentirenet

↑ Back to the top

Article Info
Article ID : 954356
Revision : 1
Created on : 1/7/2017
Published on : 11/22/2010
Exists online : False
Views : 308