Windows 11: Compatibility issues with Virtualbox fixed

Windows[German]Since the release of Windows 11, there has been a compatibility problem with the virtualization software Virtualbox that prevented its use. Microsoft has now announced that this problem has been solved "externally". The developers, who now belong to Oracle, seem to have found the problem and corrected it. This means that Virtualbox can be used under Windows 11.


Virtualbox compatibility issues

I had pointed out the issue in the blog post Windows 11: Known issues (October 5, 2021). Using Virtualbox together with Hyper-V was not possible in Windows 11. This was because Microsoft and Oracle had identified a compatibility issue between VirtualBox and Windows 11 when Hyper-V or Windows Hypervisor is installed.

As a result, virtual machines (VMs) might not start and an error would be displayed. Microsoft had imposed a compatibility lock that prevented these devices from installing Windows 11 or offering the OS as an upgrade on such Windows 10 machines. It was said at the time: Oracle is working on a solution and is expected to release a compatible version of VirtualBox in October 2021.

Oracle has documented the status of the conflict between Virtualbox and Hyper-V in ticket 20536 No VM will start on Windows 11 host. There it says in the meantime "fixed in 6.1.28". I had addressed the release of the version in the German blog post VirtualBox 6.1.28 freigegeben and also mentioned the fix for Windows 11 compatibility. But there was reader feedback there that Virtualbox 6.1.28 also did not make Hyper-V compatible on Windows 11. It then somehow didn't work out with the October 2021 fix for a compatible version of VirtualBox.

However, Windows 11 users who wanted to use Virtualbox could uninstall the Hyper-V server as a workaround. Then there was no conflict anymore. On the other hand, uninstalling Virtualbox caused Microsoft to lift the Windows 11 upgrade lockout for compatible machines. The machines should then have been offered Windows 11.

This officially only affected Windows 11 21H2 Pro, Enterprise or Education, as the Home edition does not offer Hyper-V. However, there are guides like here to install Hyper-V Server for Windows 11 Home as well. 

Microsoft confirms: Virtualbox now compatible

I had seen it hours ago on various websites (e.g. Bleeping Computer) that the problem was reported as fixed. Microsoft had added the entry Compatibility issues have been found between Oracle VirtualBox and Windows 11 on March 11, 2022 in the Windows 11 status section in the resolved issues section.  


Behobene Windows 11 Probleme

The section with fixed problems on Windows 11 now states:

Oracle has resolved this issue in VirtualBox 6.1.28 and later. To remove the safeguard hold on your device, you will need to update to VirtualBox 6.1.28 or later. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 11, version 21H2 is offered.

If there is still a warning when upgrading to Windows 11 before Virtualbox, but this product was not knowingly installed, then there may be an application running on the machine that uses Virtualbox virtualization technology – writes Microsoft. Then this application must also be updated to be able to upgrade from Windows 10 to Windows 11 or use this application.

Similar articles:
Windows 11: These features disappear
Windows 11: No TPM required?
Windows 11: Rollout is the starting October 5, 2021
Windows 11: Hardware requirements
Windows 11 officially released
Windows 11: Known issues (October 5, 2021)
Windows 11: Microsoft enforces TPM 2.0 on virtual machines
Windows 11 officially released
Windows 11 IoT Enterprise only with 36 months support
AMD warns: CPUs run up to 15% slower with Windows 11
Windows 11: Most hardware don't fulfill the minimum requirements, Microsoft reveals by-passing trick
Windows 11: File Explorer has a Memory Leak
Windows 11 also floods folders with empty TMP directory garbage
Windows 11 and the slow Explorer
Windows 11: Performance issues with NVMe-SSDs?
Windows 11: Microsoft fixes NVMe SSD Performance Issue
Windows 11: Microsoft fixes issues rendering colors correctly
Windows 11 upgrade for compatible devices in final availability phase (Jan. 2022)
Windows 11 may bricks MSSQL server instances; no longer executable
Windows 11: Does "Microsoft Family Safety" work for you?
Windows 11 Insider Preview Build 22557 brings Start Menu Folders
Windows 11: Internet connection and Microsoft account becomes mandatory during setup
Windows 11: A/B test shows watermark on unsupported systems
Windows 10 20H2: January 2022 Updates breaks AGPM-Server
Microsoft confirms wipe issue on resetting Windows 10/11 (20H2 – 21H2)
Windows 11: Fix for Explorer crash when opening Win+X menu in build 22563
Windows 11: Microsoft wants your credit card data
Windows 11: BSODs in battery mode with Lenovo Thinkpad L590?
Still wipe issues when resetting Windows 10 (20H2 – 21H2) and Windows 11

Cookies helps to fund this blog: Cookie settings

This entry was posted in issue, Virtualization, Windows and tagged , , , . Bookmark the permalink.

5 Responses to Windows 11: Compatibility issues with Virtualbox fixed

  1. Ethan says:

    I am tired of complaining that my os does not work, I became the true definition of insanity. Instead of whining like a b-i-cth, I chose to fix the problem, Hyper-V disabled, system still crashes after launching a virtual machine, reinstalled virtualbox, still crashes computer system, my last choice was to go back to Windows 10. Windows 11 has become trash. Y'all want to fix the problem, remove the issue. It turns out Virtualbox wasn't the issue, Windows 11 was.

  2. Ian says:

    I am on Win11 with VBox 6.1.36 – With Hyper-V disabled my VMs run, with Hyper-V enabled my RHEL VM got a kernel panic… Turned off Hyper-V again and all is well…
    I have no plans to turn Hyper-V on again…

    • Marc says:

      I turned off hyper-v in "Turn Windows features on or off" and PowerShell commands "bcdedit /set hypervisorlaunchtype off" and "DISM /Online /Disable-Feature:Microsoft-Hyper-V" yet virtualbox rhel VM's still kernel panic.

  3. John Jenkins says:

    I cannot start Windows 98 in VB on my Windows 11 PC but get the error code:
    Not in hypervisor partition (HPV=0) (VEER_NEM_NOT_AVAILABLE)

    VT-X is disabled in BIOS for all CPU Modes

    Where do I go from here please? I do so want to play my Might & Magic 6, 7, 8, and 9.

    • guenni says:

      It says "VT-X is disabled in BIOS for all CPU Modes" – so check how to enable in BIOS/UEFI.

Leave a Reply

Your email address will not be published. Required fields are marked *