Vagrant up fails with supHardenedWinVerifyProcess failed with -5607: ntdll.dll on Windows 11 Pro Ins

[AiNebula]

Expectation : Help me install VMs using Vagrant on Oracle VB. I am on Windows Insider Program and I """REGRET""" this.

Configuration info :
Versions : (Vagrant 2.3.4, Oracle VirtaulBox Version 7.0.8 r156879 (Qt5.15.2)).
OS settings : Firewall disabled, Antivirus disabled
RAM assigned to VMs : 2GB

Machine
1. Dell Inspiron 7501
2. Processor Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz 2.59 GHz
3. Installed RAM 16.0 GB (15.8 GB usable)
4. System type 64-bit operating system, x64-based processor

Debug output

3078.3554: 00007ffa4da8b000-00007ffa4da8dfff 0x0008/0x0080 0x1000000 \Device\HarddiskVolume3\Windows\System32\ntdll.dll
3078.3554: 00007ffa4da8e000-00007ffa4da8efff 0x0004/0x0080 0x1000000 \Device\HarddiskVolume3\Windows\System32\ntdll.dll
3078.3554: 00007ffa4da8f000-00007ffa4db07fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume3\Windows\System32\ntdll.dll
3078.3554: 00007ffa4db08000-00007ffa4db09fff 0x0000/0x0080 0x1000000 \Device\HarddiskVolume3\Windows\System32\ntdll.dll
3078.3554: 00007ffa4db0a000-00007ffffffeffff 0x0001/0x0000 0x0000000
3078.3554: VBoxHeadless.exe: Differences in section #8 (.rsrc) between file and memory:
3078.3554: 00007ff7d09525f8 / 0x01125f8: 00 != 50
3078.3554: 00007ff7d09525f9 / 0x01125f9: 00 != 41
3078.3554: 00007ff7d09525fa / 0x01125fa: 00 != 44
3078.3554: 00007ff7d09525fb / 0x01125fb: 00 != 44
3078.3554: 00007ff7d09525fc / 0x01125fc: 00 != 49
3078.3554: 00007ff7d09525fd / 0x01125fd: 00 != 4e
3078.3554: 00007ff7d09525fe / 0x01125fe: 00 != 47
3078.3554: 00007ff7d09525ff / 0x01125ff: 00 != 58
3078.3554: Restored 0xa08 bytes of original file content at 00007ff7d09525f8
3078.3554: Error (rc=-5607):
3078.3554: ntdll.dll: SizeOfImage (0x218000) isn't close enough to the mapping size (0x21a000)
3078.3554: Error (rc=-5607):
3078.3554: supHardenedWinVerifyProcess failed with -5607: ntdll.dll: SizeOfImage (0x218000) isn't close enough to the mapping size (0x21a000)
3078.3554: Error -5607 in supR3HardNtChildPurify! (enmWhat=5)
3078.3554: supHardenedWinVerifyProcess failed with -5607: ntdll.dll: SizeOfImage (0x218000) isn't close enough to the mapping size (0x21a000) 

Expected behavior

Vagrant up should succeed and my VM should get installed

Actual behavior

vagrant up command fails and does not inform anything useful to debug further. Could not get information from Vagrant Customer support as well.

Reproduction information

Vagrant version : 2.3.4

Host operating system

Windows 11 Pro Insider

Guest operating system

geerlingguy/centos7

Steps to reproduce

1. vagrant init geerlingguy/centos7
2. vagrant up

Vagrantfile logs : https://drive.google.com/drive/folders/1R5qOFXrMZaNOrzfk67bfD7wFvpb7Er5y?usp=share_link 

[#2]

It seems like this is a common issue -- I've been fighting with it and trying to understand and get it going for a few days now. I wanted to share a few links to people talking about the issue. It seems that for some reason Microsoft is allocating an additional 8kb of memory for each of these dll sections - not only for this DLL, but for the others. I had the same issue trying to run Minikube and even just calling VBoxManage or VBoxHeadless directly.

What I want to know is: Is this due to a feature I have enabled on my installation or possibly to how VBoxManage and VBoxHeadless are loading these DLLs? Is there something I can do to change how the DLLs get loaded so that they don't include this additional 8kb of memory that VirtualBox seems to be upset with? If there is not, can someone provide some information on why this is so that we can work with VirtualBox to get it working on this build of Windows?

I would be happy to try anything anyone wants me to try or report back on, since I've got the issue on my machine (also Windows 11 Pro Insider)

Links:
- Points out the 8kb difference: https://forums.virtualbox.org/viewtopic.php?t=106200&start=15
- https://github.com/hashicorp/vagrant/issues/13163

[#3]

I have the same problem as you when trying to automate the process. Although I have tried to reinstall the Windows version, it still did not work. However, recently, I made it work by changing the "vb.memory = 800" in my Vagrantfile and it worked just fine. Hope this helps!!!

[#4]

@davidthehieu I forgot, I also added the "vb.gui = true" inside my Vagrantfile