You are receiving this because you were mentioned. Maybe Microsoft wanna be another Apple on their exclusivity for their own platform.
UNINSTALL VIRTUALBOX INSTALL
I'll add this to the thread: technical issues aside, how about the fact that restricting any sort of 3rd party install like this feels super anti-competitive? Why is it, from a customer service perspective, that competing apps/platforms (eg Vbox and VMware) will function just fine when installed together -but- installing Hyper-V locks me to that one particular solution? Especially with all of the antitrust stuff going on in the US today and MS's own history with the FTC.Ĭ'mon guys, you can do way better than this. Subject: Re: WSL2 breaks VirtualBox 6.1 ( #798) Downgrading to WSL 1 does not really work for me either, due to various compatibility and performance issues.įrom: Nguyen Nguyen Anh Monday, August 16, 2021, 06:24 So unfortunately, despite all the great advantages of WSL 2, it is not to a viable solution, because I often need to run VirtualBoxes and every time deinstalling the "Virtual Machine Platform" and rebooting the computer before I can do this is just too cumbersome. What I find particularly problematic is that there is no official statement of Microsoft or Oracle that they recognize the issue and are working on it, I cannot find any dedicated tickets for this on either side. Other people are reporting similar problems with WSL 2 and VirtualBox, e.g. So it looks like that WSL 2 currently cannot coexist with VirtualBox, at least not with the current version 6.1.12 which I am using. The problem manifests itself in very slow performance, core dumps and screen staying black after booting e.g.
Installing "Windows Hypervisor Platform" as mentioned by did not change anything for me. If you want to use WSL 2, you need to install the "Virtual Machine Platform" feature - but as soon as you do that, VirtualBox does not work properly any more. This is a duplicate of #536, but that issue is closed and I see no way to reopen it.
Worse yet, the only way I could manage to get VB working again was to restore to before installation of WSL2 and reinstall ("Repair") VirtualBox. This happens despite the VM being configured to use HyperV and with HyperV enabled in Windows Features.
UNINSTALL VIRTUALBOX WINDOWS 10
Running Windows 10 version 2004 and VirtualBox 6.1, enabling WSL2 causes Ubuntu/VB to boot to a blank rectangular screen with rapidly blinking cursor.
UNINSTALL VIRTUALBOX ANDROID
This lets applications use the Hyper-V architecture for their emulation such as the Google Android Emulator, and VirtualBox 6 and above which are both now compatible with Hyper-V.
0 kommentar(er)
