Knowledge Base

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

Tips for repairing the VMDK file for a crashed Workstation or GSX Server guest on a Windows host (2016)


My guest operating system crashed and now won't start. Is there a way I can repair the disk descriptor file (.vmdk) so that the guest boots again and I can rescue my data?


Note: This article applies only to the product versions listed. For Workstation 7.x, see Repairing a virtual disk in Fusion 3.1 and Workstation 7.1 (1023856).

The information in this article is for advanced users or system administrators only.

Warning: If the VMDK file (.vmdk) for your guest operating system is corrupted, we cannot guarantee that you can repair the file and rescue your data. Your safest course of action is to call VMware Technical Support for help. If you decide to try to rescue the file yourself, we offer some tips for you here.

When you power on a virtual machine after it has crashed, Workstation and GSX Server attempt a basic repair during the startup process. The VMware software checks the disks and fixes inconsistencies found on the them.

If there are severe errors in the .vmdk file, Workstation or GSX Server cannot mount the disk. When your .vmdk file is in this state, you should:

  1. Consider restoring the file from your backup.
  2. If you don't have a backup or cannot restore the backup for some reason, try installing the VMware diskmount utility on your host machine. For instructions, see Downloading and Using the VMware Diskmount Utility below.
  3. If you succeed in mounting the .vmdk file, copy the data to a new virtual disk as soon as possible.

For more information about this topic, and for a link to a virtual disk driver that may also help you if the VMware diskmount utility does not, see the user solutions area of the VMTN Discussion Forums at

Downloading and Using the VMware Diskmount Utility

Download the VMware diskmount utility to your Windows host from . Be sure to read the EULA carefully before using this utility, as VMware will not provide any support services under this agreement. For additional information see

A newer version of the diskmount utility for both Windows and Linux is available in the Virtual Disk Development Kit:

Make the corrupted .vmdk file available to the Windows machine and try to mount the disk. To do this:

  1. Install the driver using the installer.
  2. Change to the directory where you installed the driver.
  3. Run the two following commands:
    1. vmware-mount /p

      This command shows the partitions and volumes within the .vmdk file. Determine which partition to mount. In the following example, this partition appears as N.

    2. vmware-mount /v:N R: diskfile.vmdk

      Substitute N with the partition determined in the previous step. Replace diskfile.vmdk with the name of your .vmdk file.

      The partition may be a local or a network drive. Accessing the.vmdk file through a local drive is the safest action. In this situation, the disk is mounted as drive R.

Additional Information:
For translated versions of this article, see:

Additional Information

For translated versions of this article, see:


corrupt-virtual-disk  how-to  virtual-disks


2016; urlz

Update History

03/25/2011 - Added link to modern version of this article.

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.


  • 20 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)
  • 20 Ratings