VBoxManage will not start VM after Windows 11 Insider update

[davidm77]

This is similar to a number of topics, including viewtopic.php?t=104355

I am running VirtualBox 6.1.50 (after updating from 6.1.44 in an attempt to fix this problem). I am running Windows 11 Insider Preview (not by choice). A few days ago it updated automatically (sometimes I hate MS) to Canary Build 26058. I use vagrant for provisioning, but after it tries to start the VM and I get an error. The same error is received if I attempt to start using the command:

Code: Select all

vboxmanage startvm ec2fa5a0-74ef-4959-b0c0-b30d750f4fea --type headless

The console error is:

Code: Select all

vboxmanage.exe: error: The virtual machine 'XXXXXXXXXX Server Vagrant 22.04a' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\ZZZZZ\VirtualBox VMs\XXXXXXXXXX Server Vagrant 22.04a\Logs\VBoxHardening.log'
vboxmanage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

The VBoxHardening.log is attached.

VBoxHardening.log

(40.31 KiB) Downloaded 15 times

The operative part of this log is at the end:

Code: Select all

1210.457c: Error -5607 in supR3HardNtChildPurify! (enmWhat=5)
1210.457c: supHardenedWinVerifyProcess failed with Unknown Status -5607 (0xffffea19): ntdll.dll: SizeOfImage (0x24f000) isn't close enough to the mapping size (0x252000)

This is obviously due to the ntdll.dll file which was installed during the Windows 11 OS update.

How do I fix this?

More info:
1. BTW, I can start VM from within the Oracle VM VirtualBox Manager, and then SSH into the VM as usual, but this adds more steps to the process which are not optimal. I need to do this independent of the GUI.
Regards.
2. To confirm it was the update to Canary Build 26058 that caused the problem, I reverted the OS to Canary Build 23619. After restarting the vboxmanage command worked perfectly as it had in the past.