VMware ESXi and vSphere Cluster Management

Remove Virtual Hardware from a VMware vSphere Virtual Machine

Learn how to remove a virtual network adapter from a VMware vSphere VM, verify the change, avoid connectivity loss, and understand device-specific cautions.

A virtual machine (VM) is a software-defined computer running on ESXi or another hypervisor. Its configuration includes virtual hardware: devices such as processors, memory, virtual disks, network adapters, controllers, CD/DVD drives, USB controllers, and passthrough hardware.

This lesson explains how to remove a virtual device through the vSphere Client, using a virtual Ethernet adapter as the primary example. Removal deletes the device from the VM configuration. It is different from disconnecting a device or moving it to another port group.

Prerequisites and permissions

Access to the vSphere Client or the applicable vSphere web interface.
The target VM must be visible in the vSphere inventory, the hierarchical list of datacenters, clusters, hosts, folders, and VMs.
Permission to modify the VM's hardware configuration, typically through the permissions assigned to your vSphere role.
Knowledge of the VM power-state requirements for the selected device. Some hardware supports hot removal, meaning it can be removed while the VM remains powered on; other devices require the VM to be powered off.
Basic knowledge of virtual switches, port groups, VM power states, and guest operating system network configuration.

Before changing a production VM, use an approved maintenance window when possible. Confirm that another management path, such as the vSphere console, is available in case network access is lost.

Remove an unused secondary virtual NIC

A virtual network adapter, or virtual NIC, connects a VM to a virtual network through a port group. A port group is a virtual-switch attachment point used by VM network adapters.

1. Identify the correct adapter

Find the VM in the vSphere inventory.
Determine which adapter is no longer needed. Compare the adapter's vSphere label, MAC address, connected port group, and connection status with the guest operating system's interface details.
Check whether the adapter provides management, application, backup, monitoring, storage, or other required traffic.
Record the adapter's MAC address, port group, guest IP address, routes, DNS usage, firewall bindings, and application dependencies before removing it.

Do not rely only on labels such as Network adapter 1 or Network adapter 2. Guest interface names and vSphere hardware labels may not correspond clearly, especially after previous hardware changes.

2. Open the VM hardware configuration

Select the target VM from the inventory.
Open the VM actions or context menu and choose the command that opens Edit Settings. The exact menu wording can vary between vSphere Client versions.
In the settings workflow, open the Virtual Hardware area or tab. This view lists the VM's configured virtual devices.

3. Select and remove the adapter

Locate the network adapter that matches the identity you documented.
Select that adapter in the virtual hardware list.
Use the interface control to remove the selected device. In many vSphere Client versions, this is a remove, delete, or X control associated with the hardware row.
Review the pending configuration change. Make sure only the intended adapter is marked for removal.
Choose the control that applies, confirms, or saves the updated settings.

If vSphere requires the VM to be powered off, shut down the guest operating system in the normal way, confirm the VM is powered off, and repeat the edit-settings workflow. Do not force a power operation unless your operational procedure permits it.

4. Verify the result

Reopen or refresh the VM's hardware settings.
Confirm that the removed adapter no longer appears in the virtual hardware list.
Confirm that the intended remaining adapter is still present and connected to the correct port group.
Test the VM's required network connectivity.
Inside the guest operating system, check for obsolete interface configuration, IP addresses, routes, DNS registration, firewall rules, and service bindings associated with the removed adapter.
Update monitoring, documentation, configuration management, and security records if they referenced the old adapter.

The expected result is that the unwanted adapter no longer exists in the VM configuration while the required network access remains available.

Removal, disconnection, and reconfiguration compared

Action	What changes in vSphere	Effect on guest connectivity	Typical use case	Reversal method
Remove	The virtual NIC is deleted from the VM hardware configuration.	The guest loses that device and any connectivity that depended on it.	Decommissioning an unused or legacy network connection.	Add a new adapter and restore the required guest configuration.
Disconnect	The NIC remains configured, but its connection is disabled or unplugged.	Connectivity through that NIC stops temporarily; device configuration remains.	Testing, temporary isolation, or emergency containment.	Reconnect the configured NIC.
Change port group	The NIC remains, but its virtual network attachment changes.	The guest may reach a different network and may require new addressing or policy.	Moving a VM between VLANs or network segments.	Select the original port group and correct guest settings.

Operational cautions

Do not remove the adapter carrying the only management connection, remote-access path, application traffic, or required monitoring traffic.
For a production VM, record current network settings and obtain the appropriate change approval before removing hardware.
Confirm that services have been migrated from a legacy VLAN or port group before removing its adapter.
Check static IP addressing, routes, DNS registration, firewall rules, NIC teaming, load-balancing configuration, licensing bindings, monitoring agents, and application interface bindings.
Some guest operating systems retain configuration for a removed interface. Clean up obsolete settings only after confirming that the interface is no longer needed.
Removal from vSphere does not automatically remove every corresponding guest operating system configuration or external network policy.

Example: decommission a legacy network connection

List the services using the legacy network and migrate them to the approved replacement network.
Confirm the migration with application owners and verify that monitoring and firewall policies are correct.
Match the legacy adapter using its MAC address and port group, rather than relying on its display order.
Open Edit Settings, select Virtual Hardware, choose the legacy network adapter, and use the remove control.
Save the configuration and verify that the adapter is absent.
Use guest console access if necessary to remove obsolete IP, route, DNS, or firewall configuration.
Update network diagrams, inventory records, monitoring, and change documentation.

Applying the workflow to other virtual devices

The general workflow is similar for other removable virtual hardware: select the VM, open Edit Settings, locate the virtual hardware list, select the device, use the remove control, and apply the change. However, removal behavior and power-state requirements vary by device.

Device type	Typical removal risk	Power-state considerations	Validation after change
Virtual network adapter	Loss of management or application connectivity; stale guest network configuration.	Some configurations support hot removal; verify support for the VM and device.	Check the hardware list, guest interfaces, routes, services, and reachability.
Virtual disk	Data loss or application failure if the wrong disk is removed.	Requirements vary by controller, disk, VM compatibility, and operation.	Match the disk carefully, verify guest storage and applications, and confirm whether storage data was preserved or intentionally deleted.
CD/DVD drive	Usually low risk, but installation or recovery workflows may depend on it.	Often removable while powered on, subject to configuration and platform support.	Confirm the expected media and device state are no longer present.
USB controller	Attached USB devices and dependent applications may stop working.	Power-state and passthrough requirements can apply.	Check dependent devices and guest applications.
Passthrough hardware	Loss of access to specialized physical hardware or assigned resources.	Frequently subject to strict power-state and host compatibility requirements.	Check host assignments, VM hardware, and the application using the device.

Troubleshooting

The remove control is unavailable or the settings cannot be saved

Review your vSphere permissions. You may be able to view the VM but lack permission to modify its configuration.
Check the VM power state and the selected device's hot-removal support.
Look for an active task, policy, snapshot operation, backup job, or other process that prevents configuration changes.
Retry after conflicting tasks complete or during an approved maintenance window.
Confirm that the VM hardware compatibility level and the ESXi host support the requested operation.

The wrong adapter may be removed

Multiple NICs may have similar labels or identical-looking connection settings.
Guest interface names may not map directly to vSphere adapter numbers.
Match the adapter by MAC address, port group, guest interface details, and documented purpose.
If the mapping remains uncertain, stop and obtain confirmation before changing the VM.

The VM loses network connectivity after removal

The removed adapter may have carried the active management or workload connection.
The guest may still depend on the removed NIC's IP address, default route, DNS registration, firewall binding, or application interface.
Use the vSphere console or another approved access path to inspect guest networking.
Restore or add an appropriate adapter if required, then correct guest IP configuration, routes, firewall rules, and service bindings.
Verify the port group and connection state of the remaining adapter.

Exam-relevant notes

Remove deletes a virtual device from the VM configuration; disconnect leaves the device configured but not connected.
A virtual NIC connects to a port group, not directly to a physical cable.
Hot removal means supported hardware can be removed while the VM is powered on; it is not a universal capability.
The correct adapter should be identified with evidence such as its MAC address, port group, and guest interface mapping.
Removing virtual hardware and deleting the underlying data are separate operations, especially for virtual disks.

For a concise operational sequence, select the VM in inventory, open Edit Settings, open Virtual Hardware, select the unwanted adapter, choose the remove control, save the change, and verify both the vSphere hardware list and guest connectivity.