[Bug]: VirtualBox 7.2.18 on Windows 11 fails to start VMs with VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619) after upgrading from 7.2.16

[sirkay2006]

Version

7.2.18

Host OS Type

Windows

Host OS name + version

Windows 11 - Version 24H2 - Build 26100.9445

Host Architecture

x86

Guest OS Type

Linux

Guest Architecture

x86

Guest OS name + version

Linux Debian 13

Component

Unspecified

What happened?

Summary
VirtualBox 7.2.18 on Windows 11 fails to start VMs with VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619) after upgrading from 7.2.16

Host OS
Windows 11

VirtualBox Version
Working: 7.2.16
Failing: 7.2.18

Guest OS
Linux Debian 13

Description
After upgrading VirtualBox from version 7.2.16 to 7.2.18, existing virtual machines no longer start.
The same VMs start successfully after downgrading back to version 7.2.16. No VM configuration changes were made between the two VirtualBox versions.
The issue appears immediately after the upgrade and is reproducible.

Steps to Reproduce
Install VirtualBox 7.2.16 on Windows 11.
Confirm that the VM starts normally.
Upgrade VirtualBox to 7.2.18.
Attempt to start the same VM.

Result
VM startup fails with the following message:

NtCreateFile(\Device\VBoxDrvStub) failed:
VERR_SUP_VP_FOUND_EXEC_MEMORY (rcNt=0xe986ea0d)

VBoxDrvStub error:
Found executable memory at 00000180ae4f1000
(00000180ae4f1000 LB 0x1000):
type=0x20000 prot=0x20 state=0x1000 aprot=0x4
abase=00000180ae4f0000

Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn
what: 3

VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619)
Process Verification Failure:
Found executable memory allocated in the process.
There is only supposed to be executable memory associated with image file mappings (DLLs & EXE).

Expected Result
The VM should start successfully, as it does under VirtualBox 7.2.16.

Workaround
Downgrade VirtualBox to version 7.2.16.
After downgrading, the VM starts normally again.

Additional Information
Upgrade was performed via:
winget upgrade --all

Reverting to 7.2.16 restores normal operation.
No VM configuration changes were made.
The issue may be related to a regression in the Windows hardening checks introduced in 7.2.18.

VBoxHardening.zip

How can we reproduce this?

Steps to Reproduce
Install VirtualBox 7.2.16 on Windows 11.
Confirm that the VM starts normally.
Upgrade VirtualBox to 7.2.18.
Attempt to start the same VM.

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.

[GianTag]

I have the same issue after the update carried out this morning. My host is win11.

[sirkay2006]

I suspect it can be related to some antivirus software running on the system (or some security settings).
I tested version .18 on a completely different Windows 11 pc and it worked.

[mimski2-0]

I had the same issue after updating to .18 this morning on a Windows 11 host. I reinstalled .16 and my VMs are starting as expected again.

[harryytm]

I had the same issue after upgrading to 7.2.18-175117 and had to roll back to 7.2.16-174877.

[arthurJonsey007]

It happened to me too when upgrading from version 7.2.16-174877 to version 7.2.18-175117. It is worth noting that reinstalling—or uninstalling and reinstalling the same version (7.2.18-175117)—does not solve the problem. Furthermore, I have four virtual machines defined, and when attempting to run any of them, they all return the same error reported in this issue.

[rbargerhuff]

I encountered the same issue described by others here after upgrading to 7.2.18-175117. I was forced to roll back to 7.2.16-174877 where the error is not present.

[JP95Git]

Some issue on Windows 10:

• Update from 7.2.16 to 7.2.18: Error.
• Reboot: Error.
• Uninstall 7.2.18 and verified that the folder in Program Files is gone. Install 7.2.18: Error.

I have to revert back to 7.2.16.

[harryytm]

I had the same issue after upgrading to 7.2.18-175117 and had to roll back to 7.2.16-174877.

I tried updating to preview build 7.2.19-175129 and it worked as normal. If anyone is comfortable with preview builds, it might be a viable solution.

[firefoot007]

Downgrading to VirtualBox 7.2.16 fixed it.

[eskaypsilon]

disabling avast antivirus (for 10 min) has fixed it for me. Alternatively put VirtualBox.exe (or the installfolder) to the exception list in your antivirus program. VirtualBox 7.2.18 running now without problems.

[Achim-Haag]

Host Windows 10 22H2 ESU
Update 7.2.18 -> VERR_SUP_VP_FOUND_EXEC_MEMORY
Update 7.2.19 preview r175129 -> problem solved

[banro86]

me funciono perfecto actualizar a la version 7.2.19!

[GianTag]

confirm ! 7.2.19 is ok.

[rbargerhuff]

confirm ! 7.2.19 is ok.

7.2.19 has not been officially released yet. Does anyone have any idea when this will be officially released?