Host-only Network Adapter conflict with WSL2

[gbuday]

I installed VirtualBox Version 6.1.18 r142142 (Qt5.6.2) onto my Windows 10 box. It worked seamlessly.

Then I installed WSL2 and some guest Linuxes onto it. For that, I installed the October 2020 latest version of Windows 10.

Now, when I try to run a VirtualBox VM, I get

Failed to open/create the internal network
'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter'
(VERR_INTNET_FLT_IF_NOT_FOUND).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I re-installed VirtualBox and also the Host-only Network Adapter to no avail.

What should I do?

[scottgus1]

I think you can go to the network adapters in the Windows host OS and disable/enable the Host Only adapter shown there.

FWIW WSL2 enables Hyper-V, which can cause trouble for Virtualbox, see HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[gbuday]

But can I run WSL2 without the Hypervisor?

In other words: am I not able to run VirtualBox and WSL2 simultaneously?

[BillG]

At the moment, no. The devs are working on a way to achieve this, but it is far from perfect!