Windows 2008 R2 virtual machine fails to boot after guest customization

Products

• VMware
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Cannot import a Windows Server 2008 R2 virtual machine, that was converted from physical to virtual, into Lab Manager
• Importing a Windows Server 2008 R2 virtual machine, that was converted from physical to virtual, into Lab Manager fails
• After deploying the template, the Windows 2008 virtual machine boots properly for the first time, but after guest customization, it reboots and then fails to load
• You see the error:
  
  Windows Boot Manager
  Windows failed to start. A recent hardware or software change might be the cause.
  File: \Windows\system32\DRIVERS\iaStoreV.sys
  Status: 0xc0000221
  Info: Windows failed to load because of a critical system driver is missing, or corrupt.

Environment

VMware vCenter Lab Manager 4.0.x
VMware ESX Server 3.5.x

Resolution

This issue occurs if the correct operating system version is not selected.

To resolve this issue, perform these steps within Lab Manager:

1. Undeploy and delete the configuration.
2. Goto VM Templates and locate the Windows Server 2008 template.
3. Hover over the virtual machine name and click Properties.
4. In the Guest OS section, ensure that the correct operating system version is selected. In this case, ensure that Microsoft Windows Server 2008 R2 (64-bit) is selected.
5. Click Update.
6. Redeploy the configuration and test.

Additional Information

For more information on converting a virtual machine from physical to virtual, see Best practices for using and troubleshooting VMware Converter (1004588).

For more information on removing non-present devices within a Windows operarting system Device Manager, see the Microsoft Knowledge Base article 269155.