If VirtualBox is misbehaving — broken network adapters, missing drivers, or mysterious E_FAIL errors — sometimes a clean reinstall is the only cure. Here’s the definitive step-by-step guide to wiping every trace of VirtualBox from Windows 11 and starting fresh.
⚠️ Before You Start — Protect Your VMs
Your Virtual Machines are completely safe during this process. VMs are just files on disk (.vbox, .vdi, .vmdk) and are never touched by uninstalling VirtualBox. That said, document what you have first:
“C:\Program Files\Oracle\VirtualBox\VBoxManage.exe” list vms
Screenshot or copy the output to just validate that they exist after reinstalling.
🗑️ Phase 1 — Uninstall VirtualBox
Open an Admin CMD and run:
wmic product where "name like 'Oracle VirtualBox%'" call uninstall
Wait for completion, then verify the folder is gone:
dir "C:\Program Files\Oracle\VirtualBox" 2>nul
You should get File Not Found. If the folder still exists, manually delete it.
🧹 Phase 2 — Deep Clean the Registry
The standard uninstaller leaves orphaned registry keys that will break your next install if not removed. Run each of these in Admin CMD:
reg delete “HKLM\SYSTEM\CurrentControlSet\Services\VBoxNetLwf” /f 2>nul
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\VBoxNetAdp" /f 2>nul
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\VBoxSup" /f 2>nul
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\VBoxSDS" /f 2>nul
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\oracle_vboxnetlwf" /f 2>nul
reg delete "HKLM\SYSTEM\CurrentControlSet\Control\Network\{4d36e974-e325-11ce-bfc1-08002be10318}\{7AF6B074-048D-4444-BFCE-1ECC8BC5CB76}" /f 2>nul
reg delete "HKLM\SYSTEM\CurrentControlSet\Control\Network\{4d36e974-e325-11ce-bfc1-08002be10318}\VBoxNetLwf" /f 2>nul
reg delete "HKLM\SYSTEM\CurrentControlSet\Control\Network\{4d36e975-e325-11ce-bfc1-08002be10318}\VBoxNetLwf" /f 2>nul
reg delete "HKLM\SOFTWARE\Oracle\VirtualBox" /f 2>nul
💡 Tip: The 2>nul at the end suppresses “key not found” errors — perfectly safe to run even if some keys don’t exist.
🚗 Phase 3 — Remove Leftover Driver Files
Orphaned .sys driver files can cause reinstall failures. Remove them:
del /f "C:\Windows\system32\drivers\VBoxNetLwf.sys" 2>nul
del /f "C:\Windows\system32\drivers\VBoxNetAdp.sys" 2>nul
del /f "C:\Windows\system32\drivers\VBoxNetAdp6.sys" 2>nul
del /f "C:\Windows\system32\drivers\VBoxSup.sys" 2>nul
Then remove any leftover OEM INF driver packages:
pnputil /enum-drivers | findstr /i "vbox"
For each oemXX.inf listed, delete it:
pnputil /delete-driver oem56.inf /force 2>nul
pnputil /delete-driver oem77.inf /force 2>nul
Replace oem56 and oem77 with whatever numbers appear on your system.
🌐 Phase 4 — Remove VirtualBox Network Adapters
Open Device Manager:
devmgmt.msc
Under Network Adapters, right-click and uninstall each of these if present:
- VirtualBox Host-Only Ethernet Adapter
- VirtualBox Host-Only Ethernet Adapter #2
- VirtualBox Host-Only Ethernet Adapter #3
- (any other VirtualBox adapters)
✅ Check “Delete the driver software for this device” when uninstalling each one.
🔄 Phase 5 — Reboot (Full Shutdown, Not Restart)
Windows Fast Startup can preserve driver state in memory. Force a full cold boot:
shutdown /s /t 0
Power the machine back on. Do not use Restart — use full Shutdown + Power On.
✅ Phase 6 — Verify the Environment is Clean
After reboot, confirm nothing VirtualBox-related remains:
pnputil /enum-drivers | findstr /i "vbox"
netcfg -q oracle_VBoxNetLwf
netcfg -q VBoxNetLwf
reg query "HKLM\SYSTEM\CurrentControlSet\Services\VBoxNetLwf" 2>nul
reg query "HKLM\SYSTEM\CurrentControlSet\Control\Network\{4d36e974-e325-11ce-bfc1-08002be10318}" /s | findstr /i "vbox"
ipconfig /all | findstr /i "VirtualBox"
All of these should return empty or error. If any VirtualBox entries still appear, go back and remove them before proceeding.
📦 Phase 7 — Fresh Install of VirtualBox
Download the latest installer from virtualbox.org/wiki/Downloads.
Right-click the installer → Run as Administrator.
During installation:
- ✅ Accept all default component selections
- ✅ Allow the network driver installation when prompted
- ✅ Do NOT cancel or skip any driver installation dialogs
- ✅ Install the matching Extension Pack afterward
⚠️ Windows 11 25H2 Note: VirtualBox 7.2.x has a known issue where the network filter driver registers as oracle_VBoxNetLwf instead of VBoxNetLwf. If Host-Only adapters fail after install, run this in Admin CMD:netcfg -l "C:\Program Files\Oracle\VirtualBox\drivers\network\netlwf\VBoxNetLwf.inf" -c s -i oracle_VBoxNetLwf
🧪 Phase 8 — Verify the Installation
pnputil /enum-drivers | findstr /i "vbox"
netcfg -q oracle_VBoxNetLwf
sc query VBoxNetLwf
sc query VBoxSDS
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" hostonlyif create
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list hostonlyifs
If hostonlyif create succeeds — you’re done! Open VirtualBox, you should find your VMs already there, otherwise re-register your VMs via Machine → Add, and fire them up.
🔁 Quick Reference Checklist
| Phase | Action | Status |
| 1 | Uninstall VirtualBox via wmic | ☐ |
| 2 | Clean registry keys | ☐ |
| 3 | Remove driver files + OEM INFs | ☐ |
| 4 | Remove network adapters in Device Manager | ☐ |
| 5 | Full shutdown + cold boot | ☐ |
| 6 | Verify clean environment | ☐ |
| 7 | Fresh install as Administrator | ☐ |
| 8 | Verify + create host-only adapter | ☐ |