VirtualBox Host-Only Adapter Missing? Quick Fix (2025)

Quick Answer

Open VirtualBox, go to File > Host Network Manager. If the adapter is missing, click Create. If it's grayed out, run C:\Program Files\Oracle\VirtualBox\VBoxNetAdp.exe -install as admin. That's it 90% of the time.

The Host-Only Adapter is a virtual network card your host uses to talk to VMs. It's not a physical thing. Windows updates — especially the big 22H2 and 23H2 ones — often kill the driver for this adapter. I've seen it happen after a driver update too, like when Intel or Realtek updates your real network card. The driver gets removed, and the adapter vanishes from both VirtualBox and your Network Connections panel.

First, check if the adapter is really gone. Open Control Panel > Network and Sharing Center > Change adapter settings. Look for something named "VirtualBox Host-Only Ethernet Adapter." If it's there, you just need to enable it. If not, follow the steps below.

Step-by-Step Fix

Open Host Network Manager in VirtualBox: File > Host Network Manager.
Click Create. This tries to install the driver and create a new adapter. If it works, you'll see an adapter appear with an IP like 192.168.56.1.
If Create is grayed out or does nothing, close VirtualBox completely. Then open Command Prompt as Administrator (right-click Start > Terminal (Admin)).
Run this command:
```
"C:\Program Files\Oracle\VirtualBox\VBoxNetAdp.exe" -install
```
Make sure the path matches your VirtualBox install location. For 32-bit systems, it's C:\Program Files (x86)\Oracle\VirtualBox\.
You should see a message like Driver installed successfully. Open Network Connections again: the adapter should now appear.
Back in VirtualBox Host Network Manager, click Create again — it should work now. Set a static IP like 192.168.56.1/24 if you need one.

If the command fails with "access denied," you didn't run as admin. If it says "file not found," check your VirtualBox install path. Some folks install it to a custom folder like D:\VirtualBox\ — adjust the path accordingly.

Alternative Fixes (If the Main One Fails)

Reinstall VirtualBox Network Driver

Open Device Manager (right-click Start > Device Manager). Look under Network adapters for "VirtualBox Host-Only Ethernet Adapter." If you see it with a yellow exclamation, right-click it and select Uninstall device. Then, in VirtualBox Host Network Manager, click Create again. This forces a fresh driver install.

Repair VirtualBox Installation

Go to Settings > Apps > Installed apps, find Oracle VM VirtualBox, click the three dots, and choose Modify. In the installer, select Repair. This restores all missing drivers without losing your VMs.

Manual Driver Installation via INF File

If nothing works, the driver INF file might be corrupted. Navigate to:

C:\Program Files\Oracle\VirtualBox\drivers\network\netadp\

Right-click VBoxNetAdp.inf and select Install. You'll need admin rights. Then go back to Host Network Manager and Create the adapter.

Prevention Tip for Next Time

Windows updates love to remove this driver. To stop that, you can pause driver updates. Go to Settings > Windows Update > Advanced options, and under Pause updates, select Pause for 5 weeks. But I don't recommend this for long — security patches matter. Instead, after a big Windows update, just run the VBoxNetAdp.exe install command as a habit. Takes 10 seconds.

Another pro tip: use a Bridged Adapter instead of Host-Only if you don't need isolated networking. Bridged adapters are more resilient to driver issues because they piggyback on your physical network card.

Still Broken?

If you've tried all of this and the adapter still won't show, you might have a corrupted VirtualBox install. Uninstall it completely (this won't touch your VMs — they're in %USERPROFILE%\VirtualBox VMs\), reboot, and reinstall the latest version from oracle.com. I've seen this fix tough cases where the Windows registry entry for the adapter was messed up beyond repair.

One last thing: if you're on Windows 11 24H2, there's a known issue with VirtualBox 7.0.x and Host-Only adapters. Upgrade to VirtualBox 7.1 or later — Oracle fixed it there. Check your version in Help > About VirtualBox.

Hope this saves you the hour I lost the first time. You're not alone — this bug has been around since VirtualBox 5.0. The fix hasn't changed much, and it works.