Window 10 crash using Virtualbox VM (solved)

I have had the same issue, being on insider dev release.

However, depending on the computers I had there were some inconsitencies.

After some investigations, I finally noticed the following:

• using the latest test build of virtualbox seems to work so far (and thus need to disable secure boot in a UEFI bios)
• on the current latest release version of virtualbox (6.1.14), if I had actually WSL2 (+ docker desktop) enabled on my physical, my virtualbox images worked pretty fine. I did not investigate further, but potentially having the WSL2 pre-reqs may help mitigate the issue.

#C

This is a known problem on builds since Build 20201.1000.  See blog:

https://blogs.windows.com/windows-insider/2020/09/23/announcing-windows-10-insider-preview-build-20221/

I have a system I am keeping on Build 20201.1000 so I can run my VirtualBox VM.  This problem may end up being fixed by Oracle in VirtualBox.  There is a test version of VirtualBox that claims to have a fix, but this test version will not run on a system with secure boot enabled in a UEFI BIOS.  I would suggest reading the blog for future builds to determine when and how problem is fixed.

Thank a lot Larry, 

                                that works for me, I'm not using secure boot.

Thanks for the suggestion.

Best, Claudio

508/5000

Hello everyone, for a few days, after the latest updates of windows 10 insidere program vers. 2004 build 20221.1000, I started having serious problems when I start every Virtualbox Virtual Machine. Windows 10 crashes and a screen appears with the restart warning and the following reference:

UNEXPECTED KERNEL MODE TRAP.

The same problem occurs on two personal computers with the same version and build of windows 10.

Thank you for the solution you want to report to me.

Best regards.

C.

Please file feedback in Feedback Hug and share the link.

-Eddie