A Practical Guide for 2025: VMware change VMDK File location

For the various servers like VMware ESX Server, VMware GSX Server 3.x and 2.5, VMware Player, VMware ACE, etc VMware has created a virtual disk format called VMDK. We all know that a virtual hard disk is an imitation of the physical hard disk. Similarly, a VMDK is also an imitation of a physical hard disk. The more efficient the VMDK file is the more efficiently the host OS will perform. But many times users feel the requirement to VMware change VMDK file location. So, today in this guide we will discuss the various reasons why users come in a situation to change the VMDK file location and the methods to do this. 

Reasons to VMware change VMDK file location

You must know that we can change the location of the VMDK file on the same host computer. Also, the VM can be shifted to another operating system. So, let’s start discussing the reasons for this movement.

• If you are looking to clone the VM.
• If the user wants to take a backup of a virtual machine.
• Troubleshooting problems that emerge high disk-space use.
• To move a VM disk using a single VMware product to an unlike platform using a different VMware Product.

Now, it will be clear to you why the user is required to change the location of VMDK files. Now let’s discuss the method of how you can perform this movement. 

Method to Change VMDK file location

Before moving the VMDK files to a different location or host there are certain points that must be followed. So, let’s have a look at the prerequisites for this method. 

Before relocating VMDK files, consider the following prerequisites:

• Understand UUID Generation: Familiarize yourself with how VMware Workstation generates UUIDs for moved VMs. A UUID (Universally Unique Identifier) is a 128-bit number used to uniquely identify objects or entities on the internet.
• Assess Potential Impacts:
  • Guest OS Compatibility: Moving a virtual machine to a host system with significantly different hardware may cause the guest OS to malfunction.
  • Processor Allocation: VMware Workstation 7.x and later versions support up to eight-way virtual symmetric multiprocessing (SMP) on multiprocessor host systems. You can assign up to eight virtual processors to VMs running on hosts with at least two logical processors. If you assign two processors to a VM on a uniprocessor host system, a warning will appear. You can ignore this warning, but ensure the VM is moved to a host with at least two logical processors before powering it on.
  • 32-bit and 64-bit hosts: You can move a VM from a 32-bit host to a 64-bit host, but not vice versa, unless the 32-bit host supports a 64-bit processor.
• Linked Clones: If moving a linked clone or its parent VM, ensure the clone can access the parent VM. VMware Workstation must locate the original VM; otherwise, it cannot power on a linked clone.

So, after following all the prerequisites let’s start discussing the method for this movement.

Steps to Move the VMDK File:

1. Verify VM File Locations: Ensure all VM files are stored within the VM’s directory, as some files might reside elsewhere.
2. Shut Down the VM: Properly shut down the guest operating system and power off the VM.
3. Copy VM Files: Transfer the VM files to the desired new location.
   • If Moving Within the Same Host:
     • Remove the VM from the library.
     • Navigate to File > Open, and browse to the VM’s configuration file in its new location.
   • If Moving to a Different Host:
     • On the new host, open VMware Workstation.
     • Navigate to File > Open, and browse to the VM’s configuration file.
4. Confirm VM Functionality: Once the VM operates correctly in the new location, delete the original VM files to free up space.

So, hopefully, after performing this method, your problem of VMware changing the VMDK file location would be solved. But, in case if you are unable to get the job done or looking for an easy solution for this you can use a VMDK recovery tool that will help you out. The tool is crafted using the lasted algorithms that will enable you to do this task in an automated manner. 

Final Verdict

So, we can conclude that this guide will solve your problem regarding VMware change VMDK file location. I have provided an easy DIY method for recovering from this problem. I hope, this blog will help you out.