VMware ESXi and vSphere Cluster Management

Remove a Virtual Hard Disk from a VMware Player Virtual Machine

Learn how to detach a virtual hard disk in VMware Player without deleting its VMDK file, including safety checks, verification, recovery, and troubleshooting.

Removing a virtual hard disk from a VMware Player virtual machine means detaching the disk from that virtual machine's hardware configuration. It does not normally delete the virtual disk file from the host computer.

This distinction is important when you want to remove an obsolete data disk, reuse a disk in another virtual machine, or make its contents available through a supported mapping or mounting workflow.

Detach versus delete

A virtual hard disk is a file-backed storage device presented to the guest operating system as a hard drive. VMware commonly stores this device using the VMDK format. A VMDK can contain virtual disk data and configuration metadata.

The host system is the physical computer running VMware Player. The guest operating system is the operating system inside the virtual machine.

Action	Effect on virtual machine configuration	Effect on VMDK files	Typical use case
Detach or remove	Disconnects the selected disk from one virtual machine	Normally leaves the files in their existing host location	Remove an unused disk or prepare it for reuse
Delete	May leave the configuration without the disk	Permanently removes files or data from host storage	Discard a disk that is no longer needed

In other words, removing a disk from the VMware Player configuration is not the same as deleting a disk file. The retained VMDK can generally be added to the same virtual machine later or attached to another compatible virtual machine.

When to remove a virtual hard disk

Remove an obsolete secondary disk that is no longer used by the guest.
Detach a data disk before attaching it to a different virtual machine.
Prepare the disk for supported mapping or mounting outside the original virtual machine.
Simplify the virtual hardware configuration before migration, testing, or reconfiguration.

For example, a temporary project may have used a secondary data disk. When the project ends, you can detach that disk while preserving its VMDK as an archive or reusable data source. You can later add the existing disk to another virtual machine instead of creating a new empty disk.

Preparation and safety checks

Removing the wrong disk can make a guest unbootable or cause applications to lose access to data. Identify the target carefully before changing the configuration.

Check	Why it matters	How to confirm
Virtual machine identity	Prevents changing the hardware of the wrong machine	Select the intended machine in the VMware Player virtual machine library
Disk capacity	Multiple disks may have similar names	Compare the capacity shown in the hardware settings with the disk used by the guest
Host file location	Confirms which VMDK will remain available	Review the disk path in the settings or virtual machine configuration
Controller assignment	Helps distinguish disks and matters when reattaching them	Record the controller and device assignment shown in the hardware list
Guest role	The boot disk or an application disk may be required	Use the guest's disk-management tools and configuration to identify the operating-system and data volumes
Backup	Protects important data if the wrong change is made	Back up important virtual disk files before editing hardware settings

Shut down the guest operating system normally before changing virtual hardware. Do not make this change while the virtual machine is running. Also ensure it is not suspended, locked, or being used by another VMware session or management tool.

Remove the disk in VMware Player

Start VMware Player and locate the target virtual machine in the virtual machine library.
Select the virtual machine, but do not start it.
Open the management menu and choose Player > Manage > Virtual Machine Settings. Menu wording can vary slightly by VMware Player version.
In the hardware device list, select the virtual hard disk you intend to detach. Check its capacity, location, controller, and guest role one more time.
Choose Remove. This removes the disk's connection from the selected virtual machine configuration.
Review the updated device list. Confirm that the intended disk is absent and that required disks, such as the boot disk, remain present.
Save the change by closing or applying the settings dialog, depending on the controls shown by your version of VMware Player.
Start the virtual machine if needed and verify that the guest no longer detects the detached disk.

The standard VMware Player removal workflow does not require command-line commands. The important action is selecting the correct disk entry before using Remove.

What remains after removal

The VMDK file normally remains on the host storage location where it was already stored. Removing the device does not automatically relocate, rename, or display the file in a new location.

The disk can usually be reattached to the same virtual machine.
The disk can usually be attached to another compatible virtual machine.
The disk may be made accessible through supported VMware or host-side disk mapping and mounting tools.

Preserve the detached file if you plan to reuse it. Keep related VMDK components together when the virtual disk uses multiple files, and avoid modifying or formatting the disk merely because it is no longer listed in the original virtual machine.

Verify the removal

Open the virtual machine's hardware settings again and confirm that the disk is absent from the device list.
Boot the guest and use its disk-management or storage tools to confirm that the detached disk is no longer listed.
Locate the retained VMDK on the host if it will be reused. Record its path and preserve it from accidental deletion.
Check guest configuration files, mount points, drive-letter assignments, services, scheduled tasks, and applications for references to the removed disk.

A disk can be absent from the guest while its VMDK still occupies host storage. Check both sides: the virtual hardware configuration and the host file location.

Reattach a removed disk

If the VMDK was retained, recovery normally involves adding an existing virtual disk, not creating a new empty disk.

Power off the virtual machine.
Open Virtual Machine Settings from the VMware Player management menu.
Use the control for adding hardware and choose the option for an existing virtual hard disk, when available.
Select the correct retained VMDK file.
Review the controller and device assignment, then save the settings.
Boot the guest and check its disk-management tools for the restored volume.

Controller compatibility and guest operating-system expectations can affect recognition. A reattached disk may require a storage rescan, a drive-letter assignment, or a mount-point configuration. Do not initialize or format an existing data disk simply because the guest does not immediately show its volume.

Examples

Reuse a data disk in another virtual machine

Detach the secondary data disk from a retired test machine, retain its VMDK, and add that existing disk to another compatible machine. The original machine no longer presents the disk, but the file remains available for reuse.

Remove an unused temporary disk

A virtual machine may have an extra disk for a temporary project. After confirming that applications no longer depend on it, remove it from the hardware list and retain the VMDK as a separate archive copy.

Correct an accidental removal

If the wrong non-boot disk was removed, do not create a replacement empty disk. Add the original retained VMDK back through the virtual machine settings and verify its controller assignment.

Prepare a disk for external access

Detach the disk before using a supported mapping or mounting workflow. This prevents the original virtual machine from continuing to present the disk while another tool or environment accesses it.

Troubleshooting

The wrong disk might be removed

Multiple disks may have similar names or capacities. Compare capacity, host file location, controller assignment, and the disk's role in the guest before selecting Remove. Back up the relevant VMDK files first.

The virtual machine no longer boots

The detached disk may have been the boot disk or a disk required during startup. Reattach the original retained VMDK rather than creating a new disk. Then verify the boot order and controller configuration.

The detached disk cannot be found on the host

Removal normally leaves the file in its existing location; it does not display or relocate it automatically. Check the virtual machine's storage directory and the disk path shown in its settings or configuration. If the file is missing, check backups and host storage before making further changes.

The disk is not visible in another virtual machine

First confirm that the VMDK is present in the new machine's hardware settings. Then rescan storage in the guest and inspect its disk-management tools. Controller compatibility, partition state, drive-letter assignment, or mount-point configuration may prevent immediate access. Do not initialize or format an existing data disk until its contents and partition state are understood.

The Remove option is unavailable

The virtual machine may be running, suspended, locked, or currently controlled by another session or tool. Shut down the guest, close active sessions, and reopen the virtual machine settings. Make sure the machine is fully powered off rather than suspended.

Exam-relevant notes

Remove detaches a virtual disk from a virtual machine configuration.
Delete removes files or data from host storage; it is a different and potentially destructive action.
A VMDK can remain on the host after its device entry is removed.
Always identify the boot disk and required data disks before changing virtual hardware.
Power off the guest before removing or adding virtual hardware.
To recover a retained disk, add it as an existing virtual disk rather than creating a new empty disk.

For the related workflow, see remove a virtual hard disk.