Oracle released VirtualBox 7.2.20 today, shipping a fix for a regression that stopped virtual machines from starting on Windows hosts. The error, VERR_SUP_VP_FOUND_EXEC_MEMORY, was introduced by 7.2.18 and left Windows 11 users unable to launch any VM. Oracle responded quickly, releasing the patch just days after the breakage. Windows users on 7.2.18 or 7.2.19 should update now, or temporarily revert to 7.2.16 if they want to hold steady.

Oracle ships VirtualBox 7.2.20 to fix a regression that bricked VMs on Windows

Oracle released VirtualBox 7.2.20 today, ending a short-lived headache for Windows users whose virtual machines stopped working outright. The fix is the only change in this release, and it arrives a mere seven days after 7.2.18 broke VM startup. That's a quick turnaround for a company that normally moves on a much more relaxed schedule.

The whole changelog is a single line. It reads, in Oracle's own words: "Fixed regression causing VMs to fail with VERR_SUP_VP_FOUND_EXEC_MEMORY," referencing GitHub issue #870. Not much to it. But for anyone who upgraded to 7.2.18 on Windows 11, that one line is the difference between a working machine and a wall of error text.

The error nobody asked to see

The error code itself is a VirtualBox "hardening" failure, the kind that trips up process verification. The message spells it out: executable memory was found where only image file mappings should exist. In plain terms, VirtualBox's anti-tampering check detected something it didn't expect and refused to go further.

It surfaces during supR3HardenedWinReSpawn, the phase where the software verifies its kernel-mode driver before launching anything. Break that step and you can't start a VM at all. No degraded performance. No partial functionality. Just nothing.

What makes this one galling is that it's a regression, not a long-standing issue. Similar VERR_SUP_VP_* errors have haunted VirtualBox since the 6.1 and 7.1 eras, usually tied to antivirus conflicts or signed-driver hiccups. People had workarounds. This one was self-inflicted, landing in 7.2.18 and forcing thousands back to 7.2.16.

To say the community reaction was brisk is an understatement. Forum members immediately told folks to revert to 7.2.16 and wait. Oracle then shipped 7.2.20 just days later. Not every vendor responds that fast to a self-caused breakage.

What's actually in the box

The release is build 175154. You can pull it from the usual spot at download.virtualbox.org/virtualbox/7.2.20/, alongside the MD5 and SHA256 verification files. Do check those hashes. It costs you nothing and saves you a bad install.

The Windows installer lands at 170 MB. Linux x86_64 is 128 MB, the macOS Intel DMG is 144 MB, and the Apple Silicon build tips out at 152 MB. Solaris gets both a p5p package and a tarball, and if you want to compile from source, the archive is a hefty 245 MB.

Guest Additions, the Extension Pack, and the SDK round out the usual supporting cast, all versioned to 7.2.20. Linux distro packages are there too for Debian, Ubuntu, RHEL, and Fedora builds. As of right now, this is just the maintenance patch, but it covers every platform Oracle still ships for.

Some background on 7.2 itself

7.2.20 sits in the 7.2 series, which dropped as a major release back on August 14, 2025. That branch brought ARM virtualization for Windows/ARM hosts, experimental 3D acceleration for Apple Silicon guests using DXMT, and a GUI overhaul that finally moved tools out of hamburger menus. It's also the series where Oracle has been quietly moving proprietary features like NVMe emulation and disk encryption into the open-source base.

This particular fix, though, has nothing to do with any of that. It's a pointed repair. If you upgraded to 7.2.18 or 7.2.19 on Windows, jump to 7.2.20. If you're still stuck on the broken version and want to hold steady, 7.2.16 remains your fallback.

The branch has run on a roughly bi-monthly cadence all year, mostly chasing kernel compatibility and Windows-host regressions. If history holds, expect the next point release before too long. But for now, the Windows headache is over, and that's worth something.

Head here to grab the release.