Skip to main content

Hypervisor service does not start automatically in Windows Server 2008 after deploying a Syspreped image

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.
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.
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.

Comments

Popular posts from this blog

SQL Azure Error - 40544

If the size of your database reaches its MAXSIZE you will receive an error code 40544. You cannot insert or update data, or create new objects (such as tables, stored procedures, views, and functions).To fix this issue either increase your database size or delete data. For increasing/decreasing SQL Azure database size, you can use this command on the Master database. Alter DATABASE database_name MODIFY (MAXSIZE = {1|5|10|20|30… 150}GB); example: ALTER DATABASE sampleDB MODIFY (MAXSIZE = 5gb);

Hardware DEP (Data Execution Prevention), NX, XD & EVP

A processor can be instructed to designate regions of memory as non-executable. This means that the memory can be used to store reference data to be read and written, but that the processor cannot treat the contents of the memory as program code to be directly executed. Intel calls this capability in their newer processors XD for “eXecute Disable” and AMD refers to it as NX for “No eXecute.” AMD's marketing materials also sometimes refer to this capability by the term EVP for Enhanced Virus Protection.
As a hardware capability of modern processors this addition is important, but its use depends entirely upon support from the operating system. So when Microsoft introduced support for this into their operating systems, they termed it Hardware DEP for Data Execution Prevention. Support for hardware DEP was introduced into the 32-bit versions of Windows XP with Service Pack 2, into Windows 2003 Server with Service Pack 1, and has always been present in Windows Vista. Hardware DEP does …