VMware Workstation Player course

Understanding Virtual Machine UUIDs in VMware Workstation Player

Learn what a VMware Workstation Player VM UUID is, how it is assigned, where it appears, and how move versus copy choices affect it.

A VMware Workstation Player virtual machine has a Universal Unique Identifier (UUID). This identifier helps distinguish one virtual machine from another, especially when virtual machines are copied, moved, inventoried, or managed by external software.

The UUID is part of the VM's virtual hardware and firmware identity. It is not the same as a guest account name, computer hostname, IP address, MAC address, or virtual disk identifier.

For background, see the virtual machine files overview and virtual machine fundamentals.

What a VMware virtual machine UUID means

A UUID is a value intended to identify one particular VM. VMware presents it as part of the virtual system's firmware information, allowing the guest operating system and inventory tools to read it.

The UUID can be used by software that needs a stable machine identity. Examples include asset inventory, monitoring, licensing, activation, security, and network-management systems. However, it is only one part of VM identity. Applications may also use a hostname, MAC address, disk information, operating-system identifiers, or their own registration data.

• UUID: identifies the virtual machine's firmware-level system identity.
• Hostname: names the guest operating system on a network.
• IP address: identifies a network address that can change.
• MAC address: identifies a virtual network adapter.
• Virtual disk identifier: relates to a virtual disk rather than the whole VM.

When VMware assigns the UUID

VMware generates the VM UUID during the initial power-on process. That first startup is important because Workstation Player can assess whether the VM is being opened from its expected location or whether its files appear to have been duplicated or relocated.

When a VM directory is opened from a different location, Workstation Player may display a prompt asking whether the VM was moved or copied. This choice determines whether VMware preserves the existing identity or creates a new one.

How the UUID reaches the guest

The UUID is exposed through SMBIOS, the System Management BIOS data structures used to report firmware-level system inventory. DMI, or Desktop Management Interface, is commonly mentioned alongside SMBIOS because operating systems and utilities use these related inventory mechanisms to retrieve hardware and firmware information.

Inside a guest, a firmware inventory utility can query the SMBIOS system or product UUID. The reported field may be labeled System UUID, Product UUID, or simply UUID. Read the field description carefully: an inventory program can display several identifiers at once.

UUID persistence during normal use

A VM normally retains its UUID when it remains the same VM in the same location. Routine operations such as powering off, restarting, ordinary guest use, and taking or reverting snapshots do not ordinarily mean that the VM has become a new instance.

File operations require more care. Copying or relocating a VM directory can cause Workstation Player to ask how the files should be treated. Always power off the VM before copying or relocating its files so that configuration and virtual disk state are consistent.

Move versus copy

Choose moved when the original VM was relocated and no independent second instance is intended. VMware preserves the VM's existing identity, helping systems that recognize it by its firmware UUID continue to see it as the same machine.

Choose copied when the files are being used to create an independent VM. VMware treats the result as a new instance and assigns a distinct UUID. This allows the original and duplicate to coexist without intentionally sharing the same machine identity.

What happens after choosing copied

A copied VM receives a new UUID so it can be managed as a separate virtual machine. This is useful for creating test systems from a golden VM or running an original and a lab clone at the same time.

UUID regeneration can affect software that registers or licenses a machine by hardware identity. Inventory records, activation state, monitoring enrollment, security agents, and network-management systems may see the copied VM as a different computer. A new UUID does not automatically change every other identity: review the guest hostname, network configuration, application IDs, and other cloned values as well.

What happens after choosing moved

Moving means that the same VM files were relocated, not duplicated. Selecting moved preserves the existing UUID and supports continuity for systems that identify the VM through SMBIOS information.

Use this option when, for example, a powered-off VM is transferred from one local disk to another and the old directory will no longer be used as a second running VM.

Finding the UUID from inside a guest

Linux

Many Linux distributions expose the SMBIOS product UUID through the DMI filesystem:

cat /sys/class/dmi/id/product_uuid

If the DMI filesystem is unavailable or you need a utility-based method, use dmidecode with root privileges:

sudo dmidecode -s system-uuid

The output should be compared with the system or product UUID shown by another trusted inventory method. Access permissions, guest configuration, and distribution differences can affect availability.

Windows

On current Windows systems, CIM can query the virtual SMBIOS product information:

Get-CimInstance Win32_ComputerSystemProduct | Select-Object -ExpandProperty UUID

The older WMIC command may also work on systems that still provide it:

wmic csproduct get UUID

WMIC is deprecated on newer Windows versions, so prefer the CIM command when possible. Graphical firmware inventory tools such as SiSoftware Sandra, smbios2, and FirmwareTablesView are additional examples. In their output, identify the value labeled System UUID or Product UUID, rather than confusing it with a BIOS serial number, disk serial number, or network adapter address.

Ways to retrieve a guest VM UUID

UUID-related entries in the .vmx file

The .vmx file is the VMware virtual machine configuration file. VMware may record UUID-related information there, including advanced fields such as:

uuid.bios = "..."
uuid.location = "..."

uuid.bios is associated with the BIOS/SMBIOS-visible machine UUID. uuid.location is associated with location identity information used by VMware when assessing a VM's files and location.

Common identifiers compared

Troubleshooting UUID problems

The move/copy prompt appears

VMware detected that the VM files are being opened from a location different from the expected one. Determine whether the original VM was relocated or whether a usable second copy exists. Select moved for a true relocation and copied for an independent duplicate.

A copied VM has the same UUID as the original

It may not have gone through the copied workflow, or UUID-related configuration data may have been preserved manually. Power off the duplicate and avoid running both instances. Review the copy process and use VMware-supported identity regeneration rather than blindly editing UUID fields.

The guest utility shows no UUID or an unexpected value

The utility may not read SMBIOS correctly, access may require administrator or root privileges, or the guest may expose the value differently. Try another SMBIOS-aware utility and confirm that you queried the system or product UUID, not a serial number or another hardware field.

Licensing or inventory sees a different machine

This is expected when selecting copied generates a new VM UUID. Update the external inventory or licensing record for the new VM. If continuity was intended, use the original VM after a true relocation and select moved.

Two VMs conflict in a networked lab

The VMs may share duplicated identity data because of an improper file-level clone. Ensure the duplicate is treated as copied, then also review hostnames, network settings, application-specific IDs, and other identifiers. A distinct UUID alone does not guarantee that every identity conflict is resolved.

Recommended operating procedure

1. Power off the VM completely before copying or relocating its directory.
2. Record the current guest-visible UUID if an external system depends on it.
3. Move the directory only when you are relocating the same VM.
4. Copy the directory only when you are creating an independent VM.
5. Open the VM in Workstation Player and answer the move/copy prompt accurately.
6. Power on the VM and verify the UUID from inside the guest.
7. Record the new value after duplication, migration, or restoration and update dependent inventory or licensing systems.

For related file-handling concepts, see virtual disks explained and configuring a VM to keep the same UUID.

Scope and limitations

A VM UUID is a useful and often stable identity component, but it is not a universal guarantee of compatibility. VMware, the guest operating system, licensing software, and management platforms may each use additional identifiers.

Guest-visible results also depend on the guest OS and the utility used to query SMBIOS. If a value is important to an external system, verify it with an appropriate guest-side tool and record it before and after a move, copy, restore, or migration.