Configure a VMware Workstation Player Virtual Machine to Retain Its UUID

Learn how to set uuid.action = "keep" in a VMware Workstation Player VMX file to preserve a VM identity after moving or copying its files.

A VMware Workstation Player virtual machine can be configured to retain its existing UUID when its files are moved or copied. This is useful when a relocated VM must continue to be recognized as the same machine.

This procedure edits the VM's plain-text VMX file. A VMX file is the VMware virtual machine configuration file, usually named after the VM with a .vmx extension.

What a Virtual Machine UUID Does

UUID means Universally Unique Identifier. VMware uses this value to distinguish one virtual machine from another. The VM's identity information is stored in its configuration, including the VMX file.

Identity continuity can matter when you restore a VM to another disk, relocate it to a different folder, or move it to another host computer. Preserving the UUID helps VMware and dependent software treat the relocated VM as the established machine rather than as a newly created instance.

A retained UUID does not turn two simultaneous copies into safely independent machines. If two copies use the same identity, inventory systems, licensing systems, network services, or management tools may see a conflict.

How Move-or-Copy Detection Normally Works

When Workstation Player notices that a VM appears to have been moved or copied, it can display a startup question asking you to identify the operation.

Selecting Moved is intended for relocation without creating a separate machine identity. VMware normally preserves the existing identity.
Selecting Copied is intended for creating another VM. VMware normally generates a new identity for the copy.

The configuration property uuid.action controls this behavior. Setting it to keep instructs VMware to retain the existing UUID, even when the VM files are moved or copied. It also suppresses the initial moved-or-copied decision prompt.

Situation	UUID behavior	Startup prompt behavior	Recommended use
VM moved normally	The existing identity is intended to remain in use.	Player may ask whether the VM was moved or copied.	Relocating a VM without creating another active instance.
VM copied normally	A new identity is normally assigned when the copy is identified as a copy.	Player may ask the user to identify the operation.	Creating a distinct VM for a lab, test, or separate workload.
VM configured with `uuid.action = "keep"`	The existing UUID is retained.	The moved-or-copied decision prompt is suppressed.	Relocating or restoring a VM when identity continuity is intentional.

When UUID Retention Is Appropriate

Use UUID retention when the relocated VM is meant to replace or continue the original machine. Examples include:

Moving a VM to another folder or storage device.
Restoring a VM folder to another host or disk location.
Recovering the original VM from a backup and preserving its established identity.

Do not use the same retained UUID for two copies that will be operated and managed as separate machines. For a simultaneous lab clone, allow VMware to assign a new identity or use the normal cloning process.

Safety Checks Before Editing the VMX File

The VM must be powered off before you edit its configuration. Powered off means the guest has been shut down; it is not running or suspended.

Power state	Safe to edit VMX	Required action
Powered off	Yes	Close Player if practical, back up the VMX file, and then edit it.
Running	No	Shut down the guest operating system and confirm that Player reports the VM as powered off.
Suspended	No	Resume and shut down the guest completely, or discard the suspended state as appropriate before editing.

Shut down the guest operating system normally.
Confirm that the VM is powered off rather than suspended.
Locate the folder containing the VM files.
Identify the configuration file named after the VM, such as ExampleVM.vmx. Do not confuse it with a virtual disk file such as a .vmdk file.
Make a backup copy of the VMX file before changing it.

Configure VMware Player to Keep the Same UUID

Power off the virtual machine completely.
Open the VM's folder in the host operating system's file manager.
Make a backup of the VM's .vmx file.
Open the correct VMX file in a plain-text editor. Avoid a word processor or an editor that adds formatting.
Add the following property on its own line, preferably at the end of the file:

uuid.action = "keep"

Save the file without changing its filename, extension, or text format. Ensure the file does not become something like ExampleVM.vmx.txt.
Start the same virtual machine in Workstation Player.
Verify that Player does not display the moved-or-copied question during startup.

The setting preserves the VM's existing identity; it does not create a new identity for a duplicate. Treat any second copy with the same UUID as the same logical machine until its identity is deliberately changed.

Practical Examples

Relocating a VM to another storage device

After shutting down the VM, move its complete folder to the new storage location, add uuid.action = "keep" to the VMX file, and launch the VM from that location. The existing UUID remains associated with the relocated machine, and Player does not ask you to classify the operation at startup.

Restoring a VM to another host or disk

If the restored VM is intended to continue the original workload, retain its UUID. This helps preserve continuity for systems that identify the machine through VMware's virtual hardware identity.

Creating a lab clone

If the original VM and its clone will run at the same time, do not configure both to keep the same UUID. Use normal copy detection and identify the duplicate as a copy, or otherwise create a distinct clone identity.

Troubleshooting

The move-or-copy prompt still appears

Confirm that you edited the VMX file used by the VM you are launching, not a similarly named file in another folder.
Confirm that the VM was fully shut down before editing.
Check that the property is spelled exactly as uuid.action = "keep" and appears on a separate line.
Verify that the editor did not add an extra extension such as .txt.
Close and reopen Player if it still has the VM configuration loaded from before the edit.

The virtual machine will not start

Review the new line for malformed syntax or incorrect quotation marks.
Restore the backup VMX file and reapply only the intended property.
Ensure that no unrelated VMX properties were removed or modified.

Two virtual machines appear to have the same identity

Determine whether the machines are duplicate copies running simultaneously.
Remove the keep behavior from the clone or allow VMware to assign the clone a new identity.
Review dependent network, inventory, licensing, and management systems for duplicate-identity effects.

Reversing UUID Retention

To restore normal VMware handling for future move-or-copy detection, power off the VM and remove or change the uuid.action setting in the VMX file. Handle UUID-related entries carefully, and do not delete unrelated VMX properties.

After saving the change, start the VM and observe the next move-or-copy decision. For a duplicate that must become an independent machine, identify it as a copy when Player asks, rather than retaining the original UUID.

Key Points

The UUID identifies a particular VMware virtual machine.
The relevant configuration is the VM's plain-text file ending in .vmx.
Edit only while the VM is powered off, and back up the VMX file first.
uuid.action = "keep" preserves the existing UUID and suppresses the move-or-copy prompt.
Retaining a UUID is suitable for relocation or intentional continuity, not for two independently managed active clones.