[Bug]: VirtualBox 7.2.22 fails before guest boot on Windows 11 ARM64 with VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619)

Open
#951 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c

Research direction

Start with the attached post-restart-VBox.log and search it for VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619) to find the host driver initialization step that fails. Compare it with issue #870, which reports the same error code. Done means the cause on Windows 11 ARM64 is identified and the reproduction is narrowed to a specific condition, such as Secure Boot or Memory Integrity.

Written by the indexing model from the issue text.

Description

bug
Version

7.2.22 r175245 (native Windows ARM64)

Host OS Type

Windows

Host OS name + version

Windows 11 ARM64, build 26300.9818

Host Architecture

ARM

Guest OS Type

Linux

Guest Architecture

ARM

Guest OS name + version

Ubuntu 26.04.1 Desktop ARM64 (live ISO

Component

Unspecified

What happened?

VirtualBox 7.2.22 r175245 fails on a Windows 11 ARM64 host (build 26300.9818) with VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619) during host driver initialization. I expected the Ubuntu live desktop to open. Instead, the VM stopped before Ubuntu started, and the failure persisted after a Windows restart. VBoxSup was running, and Secure Boot and Memory Integrity were enabled.

The error code also appears in issue #870. This report reproduces it on native Windows ARM64 with VirtualBox 7.2.22.

post-restart-VBox.log

How can we reproduce this?
  1. On Windows 11 ARM64 build 26300.9818, install native VirtualBox 7.2.22 r175245.
  2. Create an ARM64 Linux VM, attach the Ubuntu 26.04.1 Desktop ARM64 ISO, and disable all VM network adapters.
  3. Start the VM using the VirtualBox GUI. It fails before Ubuntu starts with VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619).
  4. Restart Windows and retry. The same error occurs. The attached log is from this retry.

post-restart-VBox.log
Image

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Dominant language
C
Stars
1.4k
Forks
219
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from VirtualBox/virtualbox

All issues in VirtualBox/virtualbox

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.