Add an Existing Virtual Hard Disk to a VMware Workstation Player Virtual Machine

Learn how to attach an existing VMDK virtual disk to VMware Workstation Player, verify it in the guest OS, protect disk data, and troubleshoot visibility problems.

An existing virtual hard disk is a previously created, file-backed disk that VMware Workstation Player can present to a virtual machine as additional storage. VMware virtual disks commonly use the VMDK format.

You might attach an existing disk to recover files from an older virtual machine, reuse a data disk in a new VM, or inspect a disk without importing the entire original VM. This procedure attaches only the virtual disk; it does not import the original virtual machine, its settings, installed applications, or snapshots.

The guest operating system must support the disk's partition table and filesystem before you can use its contents. A guest may detect the virtual device but still be unable to mount its volumes or open its files.

For background, see Virtual Disks Explained and Virtual Machine Files Overview.

Before attaching the disk

Shut down the target VM. Do not attach hardware while the VM is running or suspended. A complete guest shutdown is safer than suspending the VM.
Identify the correct disk file. The usual file to select is a .vmdk file. Confirm that it belongs to the data disk you intend to use, not merely the system disk of another VM.
Make a backup. Copy the disk and its related files before changing attachments, especially if it contains important or irreplaceable data. Keep the copy consistent and do not alter the original while copying it.
Check exclusive use. Make sure no powered-on VM is attached to or writing to the disk. A writable disk must not normally be used by multiple active VMs at the same time.
Check controller compatibility. The target VM needs a suitable virtual disk controller and interface, such as IDE, SCSI, SATA, or NVMe where supported. The selected interface must be supported by both VMware and the guest operating system.

Existing virtual disk attachment workflow

Stage	Action in VMware Workstation Player	Expected Result	Important Caution
Prepare	Power off the target VM and locate the existing VMDK.	The VM is not using the disk, and the correct disk set is available.	Back up the disk and avoid selecting a disk that another running VM is writing.
Open settings	Select the VM, then open `Player > Manage > Virtual Machine Settings`.	The VM settings window opens on the Hardware tab.	Use the intended destination VM, not the VM that originally owned the disk.
Add hardware	Select Add, choose Hard Disk, and continue.	The New Hardware Wizard starts the disk-attachment workflow.	Choose an interface compatible with the disk and guest OS.
Select disk	Choose Use an existing virtual disk, browse to the VMDK descriptor, and finish.	The disk appears in the VM hardware list.	Keep split-disk and snapshot files together.
Verify	Save the configuration, boot the VM, and inspect the guest OS storage tools.	The device and, if supported, its volume are available to the guest.	Device detection, volume mounting, and file access are separate steps.

Open the target VM hardware settings

In the VMware Workstation Player library, select the virtual machine that should receive the disk.
Confirm that the VM is powered off. If it is suspended, shut it down instead.
Open Player > Manage > Virtual Machine Settings. In some versions, the equivalent management command is available from the VM's context menu.
Open the Hardware tab. This list shows the virtual devices currently configured for the VM.

Add a hard disk through the New Hardware Wizard

Select Add to launch the New Hardware Wizard.
Choose Hard Disk as the hardware type and continue.
When VMware asks for the virtual disk type or controller interface, select an option appropriate for the target guest OS and the disk. IDE, SCSI, SATA, and NVMe are different virtual interfaces; a guest may require a suitable driver before it can use one.
Choose the option to use an existing virtual disk rather than create a new blank disk.

A disk controller is the virtual hardware connection between the guest OS and a virtual disk. Matching the original interface is often a sensible choice, but compatibility with the target guest OS is more important than preserving a particular interface when the disk is used as secondary storage.

Choose and attach the existing VMDK

Use Browse to locate the existing disk.
Select the main or descriptor .vmdk file for the disk. Do not select an individual extent file from a split disk.
Continue through the wizard and select Finish.
Check the Hardware list in Virtual Machine Settings. The newly attached hard disk should be listed with its controller and capacity.
Save the VM configuration changes by selecting OK or the equivalent confirmation command.

If VMware asks whether the disk was copied or moved, answer according to what you actually did and consider the effect on virtual machine identity and disk references. Do not rename or move related disk files casually.

Understand VMDK file components

A VMDK may be a single file, or it may consist of a small descriptor file plus one or more data or extent files. The descriptor describes the virtual disk and points VMware to the data that stores its sectors.

Component	Typical Naming Pattern	Purpose	Selection Guidance
Descriptor VMDK	`disk.vmdk`, often relatively small	Describes the disk geometry, format, and associated extents.	Select this main VMDK in the existing-disk browser when the disk is split or uses separate extents.
Monolithic data VMDK	`disk.vmdk`, often large	Contains both disk description information and virtual disk data in one file.	Select it when it is the complete standalone disk.
Split extents	Names commonly include numbered segments or extent indicators	Store portions of a virtual disk across multiple files.	Keep every associated extent with the descriptor. Do not select or move only one segment.
Snapshot delta	Names commonly include snapshot or numbered delta indicators	Stores changes made after a snapshot and depends on a parent disk.	Do not attach an isolated delta file as a standalone disk. Preserve the complete snapshot chain.

A snapshot chain is the relationship between a base disk and one or more delta disks. Every required parent and child file must remain available in its expected location. Copying only one file from a snapshot-based VM can make the disk unusable or present an incomplete state.

Start the VM and use the disk in the guest

Boot the target virtual machine after saving the hardware configuration.
Open the guest OS file manager and look for a newly available volume. Some operating systems detect and mount a supported volume automatically.
If no new volume appears in the file browser, open the guest OS disk-management utility and inspect the storage devices, partitions, and volumes.
If the device is present but offline, bring it online only after confirming that it is the intended disk.
If a supported volume has no drive letter or mount point, assign one or mount it using the guest OS's normal storage tools.
Read several expected files before editing or moving data.

These are distinct states:

Device detected: the guest sees the virtual storage device.
Partition recognized: the guest understands the disk layout.
Volume online: the guest has made the volume available for management.
Volume assigned or mounted: the filesystem is connected to a drive letter or directory.
Files accessible: applications can read the contents.

A partition is a logical section of a disk. A filesystem organizes files inside a volume. To mount a filesystem means to make it available for normal access by the operating system.

Practical examples

Attach a data disk from an older VM

Power off the destination VM and back up the older VM's data-disk files.
Open the destination VM's settings, select Add, and choose Hard Disk.
Choose Use an existing virtual disk and select the old data disk's VMDK.
Finish the wizard, confirm the disk appears in the Hardware list, and save the settings.
Boot the destination guest and verify that the expected data volume mounts correctly before copying or changing files.

Attach a split VMDK correctly

Locate the small descriptor VMDK and all of its associated extent files.
Select the descriptor file in VMware's file-selection dialog.
Keep the descriptor and every extent in the expected folder structure. Do not rename or move only part of the disk set.
Start the VM and confirm that VMware resolves the complete disk.

Use a disk created for a different guest OS

The target guest may detect the device but fail to recognize its partition format or filesystem. Inspect it with the guest's disk-management tools without formatting it. If necessary, use an operating system or recovery environment that supports the original filesystem and encryption method.

Compatibility and data safety

Filesystem support: Windows, Linux, and other guest systems support different filesystems. A detected disk is not necessarily a readable disk.
Partition format: The guest must understand the disk's partition layout, such as a format used by the original operating system.
Encryption: BitLocker, LUKS, and other encryption systems require their keys, passwords, or recovery information.
Controller drivers: The guest may need a driver for the chosen virtual controller. Changing the interface unnecessarily can prevent boot or disk detection.
Permissions: The VMware process and host user must be able to read and, when required, write the disk files. External storage must remain connected and available.
Shared writable access: Do not attach the same writable disk to multiple powered-on VMs. Independent guest filesystems can corrupt one another unless a storage and clustering design explicitly supports shared access.
Snapshots: Preserve all parent and child files in a snapshot chain. An isolated delta disk is not normally a complete disk.

Disk visibility troubleshooting

Symptom	Likely Cause	Where to Check	Recommended Action
The VMDK cannot be selected or VMware says it is unavailable.	The wrong VMDK was selected, split extents are missing, or the path is inaccessible.	Host folder, disk-file permissions, and external-drive connection.	Find the primary descriptor VMDK, restore all related files, and verify access to the complete disk set.
The VM starts, but the added disk is absent from the guest.	The configuration was not saved, or the controller or driver is unsupported.	VMware Hardware list and the guest OS disk-management utility.	Confirm the disk is listed in VMware, then check controller compatibility and required guest drivers.
The disk is detected, but no volume appears in the file browser.	The disk is offline, has no mounted volume, or uses an unsupported partition or filesystem.	Guest OS disk-management utility.	Inspect the disk without formatting; bring it online or mount a supported volume only after confirming its identity.
The disk appears, but files cannot be opened.	Unsupported filesystem, encryption, or filesystem damage.	Guest filesystem and encryption tools, plus the original VM's operating system details.	Use a compatible OS or utility, provide required keys, and work from a copy before repair attempts.
VMware reports a lock or says the disk is already in use.	Another VM is using the disk, or a previous session left a stale lock.	Running VMs and host processes that access the disk.	Shut down every VM using the disk. Investigate stale locks only after confirming that no active process is using it.
The disk fails after being copied from a snapshot-based VM.	Parent or delta files are missing, or the chain references changed paths.	Original VM folder, backup, and snapshot-related disk references.	Restore a complete consistent chain. Do not attach an isolated delta as a standalone disk.

Verify the result

Open Virtual Machine Settings while the VM is powered off and confirm the added disk remains in the Hardware list.
Boot the guest and confirm that its disk-management tool detects the expected device and capacity.
Confirm that the intended volume is online and mounted or assigned appropriately.
Read representative files and check that their names, sizes, and contents are correct.
Do not begin repairs, permission changes, or filesystem conversions until you have a backup or working copy.

Remove the disk without deleting its files

When the disk is no longer needed by the VM, power off the VM and open Player > Manage > Virtual Machine Settings. On the Hardware tab, select the added hard disk and choose Remove. Confirm the option that removes the disk from the virtual machine configuration rather than deleting the disk files.

Removing the device from the VM does not make the VMDK a blank disk and does not erase its data when the non-deleting removal option is selected. Keep the complete VMDK set in place if you may attach it again. For a related task, see Removing A Virtual Hard Disk.

Exam-relevant notes

An existing virtual disk is attached to a VM; it is not the same as importing an entire VM.
The normal selection for a split VMDK is its descriptor file, with all extent files kept together.
A powered-on VM should not share a writable disk with another VM unless an appropriate shared-storage and guest-clustering design is in use.
Seeing a disk device does not prove that its filesystem is mounted or that its files are accessible.
To preserve the original disk, remove it from the VM configuration without deleting its files.

For related storage tasks, see Adding A New Virtual Hard Disk and the VMware Workstation Player Course.