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

Learn how to safely attach an existing VMDK virtual hard disk to VMware Player, choose a compatible controller, validate the disk, and troubleshoot common problems.

VMware Player is a desktop virtualization application used to configure and run virtual machines. A virtual machine is a software-defined computer with virtual hardware and a guest operating system. Its virtual hard disk is a file-based representation of a disk used by that guest.

This guide explains how to attach an existing VMware virtual disk file to a virtual machine that is already present in VMware Player. The disk can be added as a secondary data disk, used to recover files, or attached to a replacement virtual machine as a possible system disk.

What Attaching an Existing Disk Does

Attaching an existing disk connects a previously created virtual disk to a virtual machine configuration. VMware Player does not automatically copy, convert, merge, repair, or restore the disk when you select it.

The usual disk format is VMDK, VMware's virtual disk file format. A VMDK may be a single file, or it may be a small disk descriptor file that describes the disk and references one or more disk extent files containing the actual data.

An additional data disk can provide access to documents or application data.
A damaged or nonbooting virtual machine's disk can be attached to a separate recovery machine.
A system disk can be attached to a replacement virtual machine, although boot compatibility is not guaranteed.

The operation changes the virtual machine's hardware configuration. It does not change the contents of the selected disk unless the guest operating system later writes to it.

Prerequisites and Safety Checks

Confirm that VMware Player is installed and that the target virtual machine appears in the Player library.
Power off the target virtual machine. A shutdown from inside the guest is preferable to suspending it.
Locate the existing disk, normally a file ending in .vmdk.
If the disk is split, keep the descriptor and every referenced extent file together. Do not select or move only one extent file.
Make a backup or separate copy of important disk files before changing the configuration.
Ensure the disk is not attached to or actively used by another powered-on virtual machine.
Confirm that the host has enough free storage and that your account has permission to read and, when required, write to the disk location.

Open the Target Hardware Settings

Select the intended virtual machine in the VMware Player library.
Open the virtual machine management menu.
Choose Player > Manage > Virtual Machine Settings.
Open the Hardware tab. This tab lists the virtual devices assigned to the machine and is where a new disk device is added.

Add a Hard Disk with the New Hardware Wizard

In the Hardware tab, select Add.
In the New Hardware wizard, select Hard Disk, then continue.
When VMware Player asks how to provide the disk, choose the option to use an existing virtual disk. Do not choose the option to create a new disk or to use a physical disk.
If VMware asks for a controller or disk type, select a compatible option before browsing for the file.
Select Browse, locate the existing VMDK, and select it.
When both a descriptor and data files are visible, select the small descriptor VMDK. The descriptor references the extent files.
Finish the wizard.
Review the Hardware list. Confirm that the newly added hard disk appears with the expected capacity and controller before closing the settings window.

Hardware tab > Add > Hard Disk > compatible controller or disk type > Use an existing virtual disk > Browse > select the descriptor .vmdk > Finish

Virtual Disk Attachment Choices

Choice	When to use it	Result
Create a new virtual disk	The virtual machine needs empty storage.	VMware creates a new virtual disk file with the selected size and provisioning settings.
Use an existing virtual disk	You need to reuse, move, recover, or attach a previously created VMDK.	The selected virtual disk is added to the virtual machine configuration; its files are not automatically copied or repaired.
Use a physical disk, if available	A supported setup requires direct access to a host physical disk.	The virtual machine is configured to access physical storage, which has different safety and permission concerns.

Choose a Compatible Controller

A disk controller is the virtual interface through which the guest operating system accesses a virtual disk. VMware Player may ask for a disk type or controller before attaching the file.

Match the existing disk's expected controller type where possible, especially when the disk should boot an operating system. Controller availability depends on the VMware Player version, virtual hardware compatibility, and the guest operating system.

Controller type	Typical use	Compatibility considerations
SCSI	Common for modern guest systems and additional virtual disks.	The guest must have a suitable SCSI driver. Match the source configuration for a boot disk when possible.
SATA	Common general-purpose virtual storage that emulates Serial ATA hardware.	Usually supported by newer guests, but the guest's storage drivers and firmware still matter.
IDE	Older or legacy guest operating systems.	Useful for compatibility with older systems, but it may not match a disk configured for another controller.
NVMe	High-performance virtual storage when available.	Requires suitable virtual hardware and guest operating-system support. An older guest may not boot or detect the disk.

For a data disk, a controller change may still require a guest rescan or driver. For a boot disk, a controller mismatch can prevent the operating system from starting even when the VMDK itself is healthy.

Start and Validate the Virtual Machine

Save the hardware settings and close the settings window.
Power on the virtual machine.
Inside the guest operating system, check whether the expected disk and partitions are visible.
For a secondary disk, use the guest's disk-management tools to bring it online, initialize it only when appropriate, mount it, or assign a drive letter.
Open several expected files or folders to verify that the correct disk was attached.

If the disk is intended to boot the guest operating system, review the virtual machine's boot order and firmware mode. The source system may use BIOS while the replacement uses UEFI, or the reverse. The guest may also lack a driver for the selected controller. Validate the disk as a secondary disk first when data recovery is the main goal.

Practical Examples

Attach an Old Data Disk

An old VMDK contains documents from a retired virtual machine. Power off a current compatible virtual machine, add a Hard Disk device, choose the existing-disk option, and browse to the old descriptor VMDK. After startup, use the guest operating system's disk tools to mount the additional disk or assign it a drive letter, then copy the needed files.

Recover Data from a Nonbooting Machine

A virtual machine no longer starts, but its VMDK files are intact. Attach the complete disk set to a separate compatible recovery virtual machine as a secondary disk. This lets you access files without trying to boot the damaged system disk.

Move a Boot Disk to a Replacement Machine

Create or configure a replacement virtual machine and attach the existing system VMDK. Select a controller compatible with the source environment, then verify firmware and boot settings. Boot failure can result from a different controller, firmware mode, boot order, missing guest drivers, or an incomplete system disk.

Disk Sharing and Dependency Safety

Do not attach a normal virtual disk read-write to multiple running virtual machines. Each guest may cache filesystem metadata and write different changes, causing filesystem corruption and inconsistent data.

Use the disk with only one active virtual machine at a time unless you are intentionally using a supported shared-disk design. If corruption is suspected, stop writing to the disk and restore from a backup where possible.

A snapshot records a point-in-time virtual machine disk state and can introduce dependent delta disk files. A linked clone is a virtual machine or disk arrangement that depends on parent disk data. Attaching only one child or delta file without its parent can fail or expose an incomplete disk. Keep parent disks, delta disks, descriptors, and snapshot metadata together until the dependency chain is understood.

Common Problems and Compatibility Checks

VMware Player primarily attaches VMware-compatible VMDK disks. Other formats may need conversion before use. An encrypted, locked, missing-parent, corrupted, or incomplete disk may not attach successfully even when its filename ends in .vmdk.

Symptom	Likely cause	Recommended check or resolution
Disk cannot be selected	The file is not a supported VMDK, permissions prevent access, or the selected file is an extent rather than a descriptor.	Confirm the format, check permissions, restore the complete file set, and select the descriptor VMDK when applicable.
Disk reports missing files	A split disk was moved incompletely, or parent, extent, delta, or snapshot dependencies are absent.	Restore all files and preserve their original relative folder structure. Do not rename or delete dependencies until they are understood.
Virtual machine will not boot after attachment	The controller, firmware mode, boot order, or guest storage driver differs from the source environment.	Match the source controller where possible, review firmware and boot settings, and attach the disk as a secondary disk to validate its contents.
Disk is locked	Another virtual machine is using it, a previous process is still active, or an abnormal shutdown left lock files.	Shut down all possible users, check running VMware processes and permissions, and investigate lock files carefully. Do not remove a lock while a valid process may still be using the disk.
Guest does not show the new disk	The device was not added, the guest has not rescanned storage, the disk is offline or unmounted, or the controller driver is missing.	Confirm the disk appears in the VMware Hardware list, rescan storage in the guest, check disk-management tools, and verify controller compatibility.

Attaching a Disk Versus Other Disk Actions

Attach an existing disk: Adds a previously created disk file to a virtual machine.
Create a new disk: Produces new empty virtual storage.
Compact a disk: Reclaims eligible unused host space from a thin-provisioned disk. A thin provisioned disk grows on the host as data is written instead of allocating its full configured size immediately. Compacting is not the same as attaching.
Remove a disk device: Removes the disk from the virtual machine configuration. Depending on the dialog choice, the host disk files can remain for later reattachment or be deleted. Removing the device without deleting files preserves the disk.

When moving a virtual machine or its disk, keep the related configuration and dependency files together. For disk-specific maintenance, see configure a virtual hard disk, compact a virtual hard disk, and remove a virtual hard disk.

Final Verification Checklist

The target virtual machine was powered off before editing hardware.
The complete VMDK file set, including descriptor, extent, parent, and snapshot dependencies, is available.
A backup or copy of important files exists.
The disk is not concurrently attached read-write elsewhere.
The selected controller matches the source or is supported by the guest.
The new disk appears in the VMware Hardware list before startup.
The guest operating system detects the disk without formatting or overwriting it unnecessarily.
Expected partitions and files are visible and readable.

For background, review what a virtual disk is, virtual machine files, and what a virtual machine is. If the goal is to create empty storage instead, use add a new virtual hard disk.