Fix VM Cable Unplugged Error on VMware/Hyper-V

This Error Makes You Think the Hardware Is Dead — But It Usually Isn't

I know seeing "Network cable unplugged" in your VM is annoying. It feels like the virtual world broke. I've been there. But 90% of the time, it's a simple setting on the virtual switch or the adapter itself. Let's fix it fast.

The Most Common Fix: Virtual Switch Mismatch

On VMware (vSphere 7 or 8) and Hyper-V (Windows Server 2019/2022), the VM's network adapter needs to be connected to a virtual switch that has a real network adapter attached. If you switch the VM to a broken or empty switch, you get that cable unplugged icon.

For VMware:

1. Shut down the VM (not just restart — full power off).
2. Right-click the VM, go to Edit Settings.
3. Find the network adapter (e.g., VMXNET3).
4. Check the Network label — it must point to a valid port group on a virtual switch that has an uplink (physical NIC).
5. If it says "-- Not Connected --" or a disconnected port group, change it to one that works.
6. Power the VM back on.

For Hyper-V:

1. Open Hyper-V Manager.
2. Right-click your VM, choose Settings.
3. Under Network Adapter, check Virtual switch dropdown.
4. If it's set to "Not connected" or a switch that has no physical NIC bound, select the right one (e.g., External Switch with your host's NIC).
5. Click OK and start the VM.

Why This Works

The VM's virtual NIC needs a path to the real world. The virtual switch acts like a bridge. If the switch has no uplink, the VM thinks the cable is unplugged. It's not a hardware failure — it's a configuration disconnect. After you reconnect it to the right switch, the OS sees the link again.

Less Common Variations

Sometimes the fix isn't the switch. Here are other things I've seen cause this:

1. Driver or Integration Services Issue

On VMware, old VMXNET3 drivers in the guest OS can trigger this. Update VMware Tools in the guest (even if Windows says it's fine). On Hyper-V, make sure Linux Integration Services are installed if you're running a Linux VM. I've seen Ubuntu 20.04 show cable unplugged until I updated the kernel.

2. VLAN ID Mismatch

If your virtual switch has a VLAN ID set (e.g., 100) but the VM's adapter doesn't match, the connection drops. Go to the VM settings, find the adapter, and set the same VLAN ID. On Hyper-V, you can set it under Advanced Features. On VMware, it's in the port group settings.

3. MAC Address Conflict

If two VMs on the same network share the same MAC address (static MAC), one will show cable unplugged. Check the VM's adapter settings — use Generate MAC address instead of a static one. I once spent an hour on this because someone copied a VM template.

4. VM Power State Fluke

On Hyper-V, if you boot a VM too fast after creating it, the network adapter might not initialize. Shut it down, wait 10 seconds, then start it again. That's fixed it for me on Windows Server 2022.

How to Prevent This

• Always check the virtual switch after changing host network settings. If you remove a physical NIC from a switch, VMs on that switch will see cable unplugged.
• Keep VMware Tools or Integration Services up to date. I update those every 3 months. Old drivers cause weird NIC issues.
• Use static MAC sparingly. Let the hypervisor assign them automatically unless you have a real reason (like license servers).
• Test with ping after every change. Don't rely on the icon alone. I've seen the icon show connected but traffic fails.

If none of this works, run ipconfig /all (Windows) or ip a (Linux) inside the VM. If the adapter shows no IP but the host says connected, it's a DHCP or static IP problem — not cable unplugged. That's a different article.