VMware ESXi and vSphere Cluster Management

Move a Virtual Machine in VMware Workstation Player

Learn how to move a VMware Workstation Player virtual machine to another folder, drive, or host, then open and validate it safely.

A virtual machine (VM) is a software-defined computer. Its guest operating system, applications, and data are stored in a collection of files rather than in one application window. Moving a VM means relocating that complete set of files and then opening the VM from its new location.

This guide covers moving a VM to another folder or drive on the same host, transferring it to another physical host, and opening it successfully in VMware Workstation Player.

What Moving a Virtual Machine Means

The host system is the physical computer and operating system running VMware Workstation Player. The guest operating system is the operating system running inside the VM.

A VM is normally represented by a VM directory containing its configuration, virtual disks, logs, snapshots, and other supporting files. The VM directory is the folder intended to contain the VM's primary files. When those files are preserved together, VM portability is primarily file-based: you can transfer the directory and open its configuration file on a compatible host.

Same-host move: The VM is relocated to another folder, disk, or partition on the same physical computer.
Cross-host move: The VM directory is transferred to another physical computer and opened there with VMware Workstation Player.

Moving is different from creating a new VM. A move preserves the existing guest operating system, virtual disks, applications, and data. The destination still needs suitable VMware software and compatible host hardware.

Supported Move Scenarios

Scenario	Supported Approach	Key Consideration
Same host, new folder or drive	Copy the complete VM directory to the new local path and open its `.vmx` file.	Confirm that every required file is included and that the destination has enough storage.
Different host computer	Power off the VM, transfer the complete consolidated directory, and open the `.vmx` file on the destination.	Check destination hardware, VMware Workstation Player compatibility, and network changes.
Different host operating system	Transfer the VM files between compatible host platforms and open the configuration in Player.	The guest and virtual hardware must remain compatible with the destination host and Player installation.
32-bit host to 64-bit host	This direction is supported when the VM and Player requirements are met.	The destination must support the guest and VM's required capabilities.
64-bit VM to 32-bit host	Possible only when the 32-bit host has a supported 64-bit processor and meets the VM requirements.	Review the host's processor capability and architecture before transferring the files.

Check Compatibility Before the Move

Host hardware can affect how a VM operates after migration. A substantially different destination host may expose differences in processor capability, device support, or virtualization features. Review the destination before copying a large VM.

Confirm that VMware Workstation Player is installed on the destination and is suitable for the VM.
Check that the destination host's processor architecture and capabilities meet the guest operating system and virtual hardware requirements.
Verify that the guest operating system remains supported by the destination's VMware environment.
Check that the VM's virtual hardware settings are compatible with the destination host.
Ensure the destination has enough free storage for virtual disks, snapshots, configuration files, and supporting files.

A 32-bit host can impose architecture constraints. Moving from a 32-bit host to a 64-bit host is supported. Moving a 64-bit VM to a 32-bit host requires that the destination have a supported 64-bit processor and satisfy the VM's other requirements; otherwise the VM may not start or may not operate correctly.

Identify Every File That Belongs to the VM

Do not assume that the visible VM entry in Player represents a single file. A typical VM directory may contain:

The .vmx configuration file, which describes the VM's virtual hardware and settings.
Virtual disk files, which store the guest operating system and its data.
Snapshot-related files, when snapshots exist.
Log files and other supporting files.
Files associated with the VM's configured working directory.

The working directory is a location that may be configured separately from the main VM directory. It can contain required VM files. If the working directory is outside the main directory, copying only the main directory can produce an incomplete VM.

Before relocation, locate externally stored files and consolidate them into the VM directory. Then update the VM configuration so its working-directory setting points to the consolidated location. After consolidation, verify that the VM's configuration, virtual disks, snapshots, and other required files are all available under the directory you will transfer.

Item	Purpose	Risk if Omitted
`.vmx` configuration file	Stores the VM configuration and is selected to open the VM in Player.	Player cannot open the VM through its normal configuration-file workflow.
Virtual disk files	Store the guest operating system and guest data.	The VM may fail to boot or report that a disk is missing.
Snapshot-related files when present	Store snapshot state and related disk data.	The VM can lose snapshot state or fail to access its current disk chain.
Working-directory files	Provide files referenced from a separately configured working location.	The configuration may reference files that were not transferred.
Any externally located VM-related files	Complete the VM's file set.	Opening or starting the VM may fail because paths no longer exist.

Prepare the VM for Relocation

Shut down the guest operating system normally.
Confirm that VMware Workstation Player shows the VM as fully powered off, not running or suspended.
Check that active virtual disk, snapshot, and configuration files are no longer being modified.
Locate the VM directory and identify any files stored outside it.
Consolidate external working-directory contents into the VM directory, then update the working-directory setting to use the consolidated location.
Check available storage at the destination.
Use a copy-first approach. Keep the original VM unchanged until the destination copy has been opened and tested.

Copy the Complete VM Directory

Copy the entire verified VM folder, including the .vmx file, all virtual disk files, snapshot-related files, and other required supporting files. Preserve the folder structure and file names during the transfer.

For example, a powered-off Ubuntu VM might be stored on the source host at:

C:\VMs\Ubuntu 16

Copy the complete folder to a destination such as:

E:\VMs\Ubuntu 16

The destination can be another local drive or partition, removable storage, a network transfer target, or a folder on another host. The transfer method is less important than ensuring that every required file arrives intact and retains the expected relative paths.

For a move to another computer, transfer the consolidated directory after powering off the VM on the source host. Do not delete the source copy yet.

Open the Relocated VM in VMware Workstation Player

Launch VMware Workstation Player on the destination host.
Select File > Open.
Browse to the VM's new directory.
Select the VM's .vmx configuration file. For example:

E:\VMs\Ubuntu 16\<VM-name>.vmx

The .vmx file is the VMware virtual machine configuration file used to register and open the VM in Player. Selecting a disk file instead of the .vmx file does not open the complete VM configuration.

Validate the Move

After opening the VM from its destination path, power it on and test it before retiring the source copy.

Confirm that the guest operating system starts normally.
Verify that the expected virtual disks are present and accessible.
Check guest devices and important applications.
Test network connectivity from the guest.
Confirm that any environment-specific network policies or services still work.
Verify that you opened the destination .vmx path rather than the original VM.

Keep the source copy until validation is complete. Once the destination has passed testing, decide whether to retain the source as a backup or remove it according to your storage and backup policy.

Network Identity Changes After Moving

When VMware Workstation Player treats a VM as moved, it generates a new MAC address for each virtual network adapter. A MAC address is the hardware identifier assigned to a virtual network adapter.

This change can affect systems that identify a device by MAC address, including:

DHCP reservations.
Firewall rules and network access controls.
Switch or wireless access policies.
Licensing systems tied to a network adapter identifier.
Guest network configuration that expects the previous adapter identity.

After the move, inspect the guest's network adapter and test connectivity. If the environment uses MAC-based settings, update the relevant DHCP reservation, firewall rule, access control, licensing record, or guest configuration.

Pre-Move Checklist

Check	Why It Matters	What to Verify
VM is powered off	Prevents files from changing while they are copied.	The guest is shut down and Player shows the VM as fully powered off.
All required files are in or consolidated into the VM directory	Prevents missing disks, snapshots, or supporting files.	Review the VM directory and any configured working directory.
Destination has sufficient storage	Virtual disks and related files can be large.	Check free space for the complete VM directory and future growth.
Destination host compatibility	Hardware and architecture differences can affect operation.	Review processor capability, guest requirements, and virtual hardware compatibility.
VMware Workstation Player available on destination	The destination needs suitable software to open the VM.	Install and verify a compatible Player version.
Network dependencies based on MAC address identified	The VM's virtual adapters may receive new MAC addresses.	Record DHCP, firewall, access-control, licensing, and guest network dependencies.

Troubleshooting

The VM Does Not Open After the Folder Is Copied

Use File > Open and select the destination folder's .vmx file.
Compare the source and destination contents to find missing configuration, disk, snapshot, or supporting files.
Check whether the VM configuration still references files outside the transferred directory.
Consolidate externally stored working-directory files into the VM directory and update the working-directory setting before copying again.

The VM Cannot Find Its Virtual Disk

Verify that every virtual disk file and related disk component was copied together.
Check whether the disk was stored outside the main VM directory.
Confirm that the configuration's referenced location matches the new consolidated path.

The VM Starts but Behaves Incorrectly on the New Host

Review significant differences between the source and destination host hardware.
Check host architecture and processor capability.
Confirm that the destination supports the VM's required 64-bit capabilities where applicable.
Review guest operating system and virtual hardware requirements.

Network Access Changes After Relocation

Check the guest's virtual adapter and network connection.
Remember that Player assigned new MAC addresses to the VM's virtual adapters.
Update DHCP reservations, firewall rules, network access controls, licensing records, or other MAC-based settings as needed.

The Original VM and Moved Copy Cause Confusion

Verify the path of the .vmx file you opened.
Use clear source and destination folder names while testing.
Keep the original only as a fallback until the destination copy has been validated, then apply your normal backup or cleanup policy.

Key Exam Notes

A VM is a collection of files, not just a Player entry or a single disk file.
The .vmx file is the configuration file selected to open the VM in VMware Workstation Player.
Virtual disks store the guest operating system and its data.
A separately configured working directory can contain required files and must be consolidated or transferred correctly.
Power off the VM before copying; do not move a running or suspended VM.
Copy first, test the destination, and retain the source until validation is complete.
A moved VM receives new MAC addresses for its virtual network adapters, so MAC-dependent network settings may need updates.
Host hardware, operating system, architecture, and processor capabilities determine whether the destination can run the VM correctly.

For related storage and transfer tasks, continue with moving a virtual machine.