VMware ESXi and vSphere Cluster Management

Move a Virtual Machine in VMware Player

Learn how to move a VMware Player virtual machine between folders, drives, and computers, then open, boot, and verify it safely.

What Moving a Virtual Machine Means

A virtual machine (VM) is a software-defined computer that runs a guest operating system under a hypervisor. The physical computer and its operating system are the host system.

In VMware Player, a VM is usually a collection of related files stored in one VM directory. The directory commonly contains the VM configuration, virtual disks, snapshot data, logs, and runtime state files. Moving a VM means relocating this complete collection rather than creating a new VM and reinstalling the guest.

There are two common types of move:

  • Same-host relocation: Move the VM from one folder or drive to another on the same computer.
  • Host-to-host transfer: Copy the VM files to another computer and open them with VMware Player there.

The .vmx file is the VMware virtual machine configuration file. It describes the VM's virtual hardware and points to its virtual disks and other files. This is the file you select when opening the moved VM in VMware Player.

When a VM Can Be Moved

A powered-off VM can generally be moved between folders, storage drives, and computers as long as the destination can run VMware Player and provide compatible resources. A VM can also move between hosts with different operating systems if VMware Player supports the destination host and the guest operating system is supported by the VM configuration.

Virtual hardware hides many differences between physical computers, but it does not remove every compatibility concern. The guest operating system and installed applications may react to different CPU features, memory capacity, graphics behavior, network adapters, USB devices, shared folders, or removable-device mappings.

Pre-Move Compatibility Checks

Check the destination before transferring files. The following checklist helps prevent an incomplete move or a VM that cannot start.

Check — Why it matters — What to verify

Host operating system support — VMware Player and its drivers must run on the destination — Confirm the destination host operating system is supported.

VMware Player availability — The destination needs software that can open the existing configuration — Install or verify VMware Player before opening the VM.

CPU architecture and 64-bit support — A 32-bit host can transfer a VM to a 64-bit host, but a 64-bit VM requires a destination capable of 64-bit virtualization — Check host architecture and guest requirements.

Hardware virtualization support — Some guests and VMware configurations require CPU virtualization features — Review the destination CPU and firmware settings.

Available memory — VMware Player must be able to allocate the VM's configured RAM while leaving enough for the host — Check physical RAM and reduce the VM allocation if necessary.

Free disk space — Virtual disks, snapshots, and temporary files can require substantial space — Allow room for the complete VM and future guest growth.

Networking and MAC-dependent services — The virtual adapter may receive a different MAC address — Check DHCP reservations, firewall rules, network allowlists, and license systems tied to network identity.

A VM transferred from a 32-bit host to a 64-bit host is not inherently a problem. The reverse direction may fail if the destination cannot provide the architecture or virtualization features required by the guest. Confirm CPU support, firmware virtualization settings, available memory, and the VM's configured hardware before copying.

Identify Every File That Belongs to the VM

Start with the VM directory, but do not assume it contains everything. The directory is intended to hold the configuration, disks, and related files, while VMware Player can also use a separate working directory. A working directory is a location for runtime or temporary VM files that may differ from the main VM directory.

File or location — Purpose — Must be included or reviewed — Risk if omitted

VM configuration (.vmx) — Defines virtual hardware and file references — Include it and use it to open the VM — VMware Player cannot load the existing VM definition.

Virtual disk files — Contain the guest's virtual hard-drive data — Include every disk file and every segment of a split disk — The guest may report a missing disk or fail to boot.

Snapshot-related files — Store snapshot disk chains and related metadata — Include them when snapshots exist; do not copy only the base disk — The snapshot chain may be broken or data may appear missing.

Saved or suspended state files — Store runtime state for resuming instead of booting — Review and resolve the state before transport — The VM may resume incorrectly or contain inconsistent state.

Working-directory files outside the VM folder — Hold runtime or temporary files referenced by the VM — Locate and consolidate them or update the setting — The copied configuration may reference files left on the source host.

Logs and temporary files — Record runtime activity and may support diagnosis — Logs are optional in many moves, but review unusual external files — Troubleshooting information or required runtime data may be absent.

Search the VM configuration and VMware settings for references to locations outside the normal folder. Pay particular attention to virtual disks, snapshot chains, removable devices, and the configured working-directory location. Do not assume that a file is unnecessary merely because it is not in the main folder.

Prepare the VM for Relocation

  1. Open the guest operating system and shut it down normally.
  2. Wait until VMware Player shows the VM as completely powered off.
  3. Resolve or discard a suspended state appropriately. A suspend state is saved runtime data that lets the VM resume rather than perform a full boot. It must remain consistent with the disk files.
  4. Close VMware Player or otherwise ensure the VM is not using its files.
  5. Make a backup, or keep the original folder untouched until the destination copy has been tested.

Do not copy a running or suspended VM as though it were an ordinary folder. Disk writes may still be in progress, and the saved state may not match the virtual disks. This can create inconsistent disks, a broken snapshot chain, or an incorrect resume operation.

Consolidate an External Working Directory

If the VM uses a working directory outside its primary location, consolidate it before the main transfer. First locate the external working-directory content. With the VM fully powered off, place the required working files in the VM directory or another single folder that will travel with the VM.

Then change the VM's virtual machine working-directory location in the VMware configuration area so it points to the consolidated location. Recheck the configuration for references to the old path. The goal is for the VM's disks, snapshots, state files, and required working files to be available from the destination copy without depending on the original host.

Copy or Move the VM Files

Copy the complete VM folder from the source to the destination. Copy-first is safer than deleting the source immediately because it gives you a rollback copy while the new VM is being verified.

For example, to relocate a VM on a Windows computer:

Source:      C:\VMs\Ubuntu\
Destination: E:\VMs\Ubuntu\
  1. With the VM powered off, locate C:\VMs\Ubuntu.
  2. Copy the entire Ubuntu folder to E:\VMs\Ubuntu.
  3. Confirm that the destination contains the .vmx file, all virtual disk segments, snapshot files when present, and any consolidated working files.
  4. For a different computer, transfer the complete folder using external storage or a network copy.

Do not move only the .vmx file. Do not move only one virtual-disk segment. A split virtual disk is a set of related files, and omitting one segment makes the virtual disk unavailable. Likewise, snapshot files and externally stored components must be transferred or consolidated.

Open the Moved VM in VMware Player

  1. Launch VMware Player on the destination host.
  2. Choose File > Open.
  3. Browse to the relocated VM folder.
  4. Select the VM configuration file, such as Ubuntu.vmx.
  5. Open the file and allow VMware Player to load the existing VM definition.

Opening the .vmx file loads or registers the existing virtual machine. It does not create a new empty VM and does not require reinstalling the guest operating system.

First Startup and Verification

Power on the VM at its new location and test it before removing the source copy.

Step — Action — Expected result — Validation

Inventory files — Identify the VM folder, configuration, disks, snapshots, and external references — All required components are known — Compare the source layout with the destination.

Power off VM — Shut down the guest completely — No running or suspended state is being copied — VMware Player reports a powered-off VM.

Consolidate external files — Move working-directory files into the transfer set and update the setting — Required files are not left behind — Check paths in the VM configuration.

Copy VM folder — Copy the complete folder to the new drive or host — The destination contains the full VM — Check disk segments, snapshot files, and file sizes.

Open .vmx on destination — Use File > Open and select the configuration file — VMware Player loads the existing VM — Confirm the displayed hardware and storage settings.

Boot and test — Power on the VM — The guest starts from its virtual disk — Test disk access, networking, applications, and expected devices.

Retire source copy — Delete or archive the original only after testing — The destination is the verified working copy — Confirm it no longer depends on the old path or host.

Verify that the guest boots, its virtual disks are available, networking works, and the expected memory, processor, storage, display, USB, and shared-folder settings are present. On a substantially different host, review the VM settings and guest configuration after the first boot.

Virtual Network Adapter MAC Address Behavior

A MAC address is the hardware-style identifier assigned to a network adapter. VMware Player may assign a new MAC address when a VM is moved. This is normal, but services that identify the VM by MAC address may behave differently.

  • DHCP may assign a different IP address.
  • A static DHCP reservation may no longer match.
  • Firewalls, switches, or network allowlists may reject the new adapter identity.
  • Software licenses tied to a network identity may require reactivation or review.
  • The guest operating system may detect a new network adapter and create a new connection profile.

After the move, inspect the VMware virtual network adapter, renew or update the guest network configuration, and adjust DHCP reservations, firewall rules, access controls, or licensing systems as needed. Do not assume that the VM will retain the same network identity on every host.

Host-Hardware Differences After a Move

Virtual hardware abstracts many host differences, but the destination still affects the VM. Review the following areas:

  • Network drivers and profiles: The guest may detect a changed adapter or create a new network connection.
  • Display behavior: Different graphics hardware, monitor arrangements, or VMware settings can change resolution and acceleration behavior.
  • USB passthrough: Device mappings may not exist on the destination or may point to different physical devices.
  • CPU feature exposure: Differences in processor capabilities can affect some guest software or operating systems.
  • Shared folders and removable devices: Host paths and device mappings may no longer be valid.

Confirm that the destination has enough resources for the configured VM. If the guest behaves differently, first review VMware Player hardware settings, memory allocation, virtual networking, display settings, USB mappings, and shared-folder paths.

Troubleshooting Common Move Problems

VMware Player Cannot Open the Moved VM

Make sure you selected the correct .vmx file rather than a disk or log file. If the file is correct, compare the source and destination folders. An incomplete copy or a configuration reference to an old path can prevent loading. Restore missing virtual disks, snapshot files, or externally stored working files.

Missing Virtual Disk or Snapshot Component

Copy every segment of a split virtual disk and every file in the snapshot chain. A referenced file may have remained outside the VM directory. Recover it from the source and preserve a backup before changing configuration references.

The VM Does Not Boot or Resumes Incorrectly

The VM may have been copied while running or suspended, leaving state files inconsistent with the disks. Return to a clean powered-off state when possible and transfer a known-good backup. Keep the source until the destination passes startup testing.

The Guest Has No Network Access

Check whether the virtual adapter received a new MAC address. Also check the destination's virtual-network settings, DHCP behavior, guest firewall, static IP configuration, and network allowlists. Update reservations and access rules when they depend on the old MAC address.

A 64-Bit Guest Fails on the Destination

Verify that the destination CPU and host operating system support 64-bit virtualization. Check whether required virtualization support is enabled in system firmware. If the destination cannot provide the required capabilities, use a compatible host.

The VM Behaves Differently on the New Computer

Differences in available resources, graphics, networking, USB devices, shared folders, or CPU features can change guest behavior. Review VMware Player settings, provide sufficient memory and disk access, and reconnect or reconfigure host-dependent devices.

Exam-Relevant Notes

  • A VM is normally a collection of files, not a single file.
  • The .vmx file is the configuration file opened by VMware Player.
  • Always power off the guest completely before copying its files.
  • Copy the complete VM folder, including split disk segments and snapshot-related files.
  • Check for a working directory outside the VM folder.
  • A move can result in a new virtual network adapter MAC address.
  • A source copy should be retained until the destination boots and passes functional tests.

For a safe move, inventory the files, shut down the guest, consolidate external working files, copy the complete folder, open the relocated .vmx file with File > Open, test the guest, and only then retire the original.