Article ID: 954356 - Last Review: November 22, 2010 - Revision: 1.1

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.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

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:
http://technet2.microsoft.com/windowsserver2008/en/servermanager/virtualization.mspx (http://technet2.microsoft.com/windowsserver2008/en/servermanager/virtualization.mspx)
Back to the top
APPLIES TO
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
Back to the top
Keywords: 
kbhyperv kbdeployment kbsyspreptool kbtshoot kbprb kbexpertiseadvanced KB954356
Back to the top