How to Remove Ghost Adapters After VMware to KVM Migration

Ghost adapters left behind by physical-to-virtual (P2V) or hypervisor migrations can cause network conflicts in Windows VMs. This issue is especially relevant now as many organizations migrate from VMware to KVM-based hypervisors like Proxmox due to Broadcom’s changes.

Steps to Remove Ghost Adapters in Windows

1. Open Command Prompt as Administrator

• Press `Win + X` and select Command Prompt (Admin).

2. Enable Non-Present Device Visibility

set devmgr_show_nonpresent_devices=1

3. Open Device Manager

devmgr.msc

4. View Hidden Devices

• Go to View > Show Hidden Devices.

5. Locate and Remove Ghost Adapters

• Expand Network adapters.
• Greyed-out entries are ghost adapters. Right-click and select Uninstall.

6. Rescan for Hardware Changes

• Click Action > Scan for hardware changes to refresh the list.

7. Repeat Until Clean

• Ensure all ghost adapters are removed.

You Should Know:

Additional Cleanup Commands

• Check Network Adapter Registry Entries (PowerShell):

  Get-ChildItem "HKLM:\SYSTEM\CurrentControlSet\Control\Network{4D36E972-E325-11CE-BFC1-08002BE10318}" | ForEach-Object { Get-ItemProperty $_.PSPath }
  

• Remove Stale NIC Registry Keys (Regedit):

• Navigate to:

  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network{4D36E972-E325-11CE-BFC1-08002BE10318}
  

• Delete subkeys with names matching old adapters.

• Reset TCP/IP Stack (Command Prompt):

  netsh int ip reset
  netsh winsock reset
  

Linux Equivalent (For KVM Hosts)

• List network interfaces:

  ip link show
  

• Remove unused virtual interfaces:

  virsh net-list --all
  virsh net-undefine <network_name>
  

Prevent Ghost Adapters in Future Migrations

• Always uninstall VMware Tools before conversion.
• Switch from static IP to DHCP before migration.
• Use Proxmox’s official migration tool or Scale Computing’s SC//Migrate for smoother transitions.

Helpful Resources

• Windows OS Hub: Removing Ghost Adapters
• Interworks: VMware to KVM Migration
• VMware to Proxmox Conversion Guide
• Scale Computing Migration Toolkit

What Undercode Say

Ghost adapters are a legacy nuisance, but proper cleanup ensures smooth post-migration networking. Always audit registry entries and device manager after hypervisor changes. For Linux-based KVM hosts, leverage `virsh` and `ip` commands for network management. Automation with scripts can reduce manual errors—consider PowerShell or Bash for bulk operations.

Expected Output:

A Windows/Linux hybrid environment free of ghost adapters, with network configurations correctly migrated to the new hypervisor.

References:

Reported By: Charlescrampton Ghost – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅

Join Our Cyber World:

💬 Whatsapp | 💬 Telegram