Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Cloned Windows 2008 R2 virtual machine fails to boot with the error: autochk program not found - skipping AUTOCHECK (2004505)

Symptoms

After cloning a Windows 2008 R2 SP1 virtual machine, you experience these issues:

  • You are unable to boot the cloned virtual machine
  • The new virtual machine fails and gets into a reboot loop
  • You see the error:

    autochk program not found - skipping AUTOCHECK

  • If you disable automatic restart, you see the error:

    STOP: c000021a {Fatal System Error

    The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000003a (0x00000000 0x00000000).
    The System has been shut down.

Cause

 This issue may occur if the System Partition created during the installation of Windows Server 2008 is assigned a default drive letter.

Resolution

This issue is resolved in ESX/ESXi 4.1 Update 2 and ESXi 5.0 Update 1. For more information, see the Resolved Issues section of the release notes:
This is still a known issue affecting ESXi 5.1.

To workaround this issue on previous versions of ESX/ESXi 4.1 and ESXi 5.x:
  1. Power down the source virtual machine.
  2. Backup the .vmx file of the source virtual machine.
  3. Change the value of the disk.EnableUUID parameter to False. For more information, see Tips for editing a .vmx file (1714).
  4. Save the changes made to the .vmx file.
  5. Clone the virtual machine again.
If these steps do not resolve the issue, try this alternate workaround:
  1. Power down the source virtual machine.
  2. Boot the virtual machine using the Windows Server 2008 R2 .iso file.
  3. In the Installation Wizard, select Repair your Computer. For more information, see the Microsoft Knowledge Base article 2261423.

    Note: The preceding link was correct as of August 18, 2011. If you find the link is broken, provide feedback and a VMware employee will update the link.

  4. Select Command Prompt.
  5. Run these commands in the specified order:

    diskpart
    list volume
    select volume 1
    attributes volume
    attributes volume clear nodefaultdriveletter

  6. Restart the virtual machine after removing the mounted .iso file.
  7. Clone the virtual machine again.
Note: If you cannot power down the source virtual machine, you can apply this alternate procedure on the resulting cloned virtual machine as well. 

Tags

boot-vm-fails  boot-cloned-vm-fails

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 30 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 30 Ratings
Actions
KB: