VirtualBox VM crash on start

[PSSD1]

I've tried multiple OSes, reinstalling VirtualBox multiple times, and checking if Virtualization is enabled in my bios. I'm running Windows 11 Pro with an AMD 7700x cpu and 32 GB of ram.

Result Code:
E_FAIL (0X80004005)
Component:
MachineWrap
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}

These are the last few lines of the log

55b8.55b4: 00007ffe78b2f000-00007ffe78ba6fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume5\Windows\System32\ntdll.dll
55b8.55b4: 00007ffe78ba7000-00007ffffffeffff 0x0001/0x0000 0x0000000
55b8.55b4: supR3HardNtChildPurify: cFixes=1 g_fSupAdversaries=0x4
55b8.55b4: supR3HardNtChildPurify: Startup delay kludge #1/2: 521 ms, 33 sleeps
55b8.55b4: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
55b8.55b4: Error (rc=-5637):
55b8.55b4: NtQueryVirtualMemory failed for 0000000000000000: 0xc000010a
55b8.55b4: Error (rc=-5637):
55b8.55b4: supHardenedWinVerifyProcess failed with -5637: NtQueryVirtualMemory failed for 0000000000000000: 0xc000010a
55b8.55b4: Error -5637 in supR3HardNtChildPurify! (enmWhat=5)
55b8.55b4: supHardenedWinVerifyProcess failed with -5637: NtQueryVirtualMemory failed for 0000000000000000: 0xc000010a
55b8.55b4: supR3HardNtEnableThreadCreationEx:

[scottgus1]

1. Uninstall Virtualbox and reboot.
2. Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
3. Reboot again.
4. If you have any 3rd-party security or anti-malware software, disable the living daylights out of it for a moment.
5. Reinstall Virtualbox using right-click-Run-As-Administrator.

If this does not get the VMs running, try one VM:

Please start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log" and the "VboxHardening.log", and post the zip file, using the forum's Attachments tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)

[PSSD1]

There isn't a vbox.log. Here is a list of all files in the folder.

-Logs (folder)
-VBoxHardening .log
-Ubuntu1 .vbox (OS name)
-Ubuntu1 .vbox-prev
-Ubuntu1 .vdi
-Unattended-9f743eb3-dab2-4e07-9411-ee634216db56-aux-iso .viso
-Unattended-9f743eb3-dab2-4e07-9411-ee634216db56-grub .cfg
-Unattended-9f743eb3-dab2-4e07-9411-ee634216db56-preseed .cfg
-Unattended-9f743eb3-dab2-4e07-9411-ee634216db56-vboxpostinstall .sh

I have sent the Hardening log if that would help.

I should mention that as soon as I power on the vm, it crashes and turns off.

[scottgus1]

Thanks for the hardening log. Please try uninstalling (not just disable, rather complete uninstall) Avast, as well as any "web-safety" or banking security software, then reboot and try Virtualbox again.

[fth0]

FWIW, another user solved the same issue by not using WindHawk at the same time as VirtualBox: Re: VERR_SUP_VP_NT_QI_VIRTUAL_MEMORY_ERROR: (rc=-5637), sometimes start other doesn't. Please help.

[fth0]

After some googling, this seems to be a known and solved issue for WindHawk: VirtualBox VMs can't start while Windhawk is running. The author of WindHawk has added an exclude list for processes, where you can add "%ProgramFiles%\Oracle\VirtualBox\*".

[PSSD1]

FWIW, another user solved the same issue by not using WindHawk at the same time as VirtualBox: Re: VERR_SUP_VP_NT_QI_VIRTUAL_MEMORY_ERROR: (rc=-5637), sometimes start other doesn't. Please help.

This seemed to have solved it! Thank you so much! I've been trying to figure it out for months!