[Bug]: Windows 11 25H2 host — Intermittent VM freezes using NEM/WHPX with VBS enabled (Ryzen 9950X3D)
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- backend, operating-systems
Research direction
Start by reading the attached sanitized log and tracing the NEM/WHPX initialization and guest heartbeat paths mentioned in the report. The issue provides no source files or failing test, and the freeze is intermittent, so first identify a reproducible diagnostic path; done means the guest remains responsive with Windows virtualization-based security enabled or the cause and supported workaround are documented.
Written by the indexing model from the issue text.
Description
Version
7.2.20
Host OS Type
Windows
Host OS name + version
Windows 11 Pro 10.0.26200 Build 26200
Host Architecture
x86
Guest OS Type
Windows
Guest Architecture
x86
Guest OS name + version
Both Windows and Linux VMs
Component
GUI
What happened?
Environment
VirtualBox: 7.2.20 r175154
Host OS: Windows 11, build 26200.9711
Host architecture: x86-64
Processor: AMD Ryzen 9 9950X3D
Host RAM: 32 GB
Guest OS: Windows 11 64-bit
Guest RAM: 6 GB
Guest processors: 8 vCPUs
Graphics: VMSVGA, 3D acceleration disabled
Windows Core Isolation / Memory Integrity: Enabled
Component: VMM / NEM / Windows Hypervisor Platform
Description
I am experiencing recurring, intermittent freezes of VirtualBox virtual machines on my Windows 11 workstation. Includes both Windows and Linux OS machines.
The issue has persisted across multiple VirtualBox updates over several months. I previously used VirtualBox on an Intel-based Windows 10 computer without experiencing this behavior.
The Windows 11 host has its normal virtualization-based security features enabled. VirtualBox falls back to the Windows Hypervisor Platform (NEM/WHPX) rather than accessing AMD-V directly.
The attached log explicitly reports that NEM's reduced-performance execution mode is active, followed by guest heartbeat failures.
Relevant log entries
HM: HMR3Init: Attempting fall back to NEM:
AMD-V is not available
NEM: WHvCapabilityCodeHypervisorPresent is TRUE
[VirtualBox_Win11_25H2_Sanitized_Log.txt](https://github.com/user-attachments/files/34638673/VirtualBox_Win11_25H2_Sanitized_Log.txt)
NEM: NEMR3Init: Snail execution mode is active!
The guest subsequently becomes unresponsive:
00:04:33 Guest seems to be unresponsive.
Last heartbeat received 4 seconds ago
00:04:54 GuestHeartBeat: Guest is alive
00:04:59 Guest seems to be unresponsive.
Last heartbeat received 5 seconds ago
How can we reproduce this?
Run an existing Windows 11 guest in VirtualBox on the described Windows 11 host.
Leave the host's default security features, including Memory Integrity, enabled.
Start the VM while VirtualBox is using the NEM/WHPX execution backend.
Use the guest normally and observe intermittent freezes and heartbeat failures.
The issue is intermittent rather than reliably triggered by a particular application.
VirtualBox reports reduced-performance NEM execution mode, and the guest experiences intermittent periods of unresponsiveness.
Troubleshooting performed
Tested multiple VirtualBox versions over several months.
Confirmed the host hypervisor is active.
Confirmed VirtualBox is using NEM/WHPX.
Captured guest heartbeat failures in the VirtualBox log.
I would prefer to retain Windows 11's built-in security protections, including Memory Integrity and virtualization-based security.
Could the VirtualBox development team investigate whether this is a known Windows 11 NEM/WHPX compatibility or scheduling issue?
Is there a planned correction, development build, or supported workaround that allows VirtualBox to operate reliably while Windows virtualization-based security remains enabled?
Please advise whether additional diagnostic traces would help identify the cause.
Attachment: VirtualBox_Win11_25H2_Sanitized_Log.txt
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from VirtualBox/virtualbox
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
VirtualBox/virtualbox#996 ·
Maintainers usually reply within 6 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
VirtualBox/virtualbox#979 ·
Maintainers usually reply within 6 days
-
[Bug]: Guest Additions 7.2.20 vboxvideo fails to build on Linux kernel 6.12.113 (drm_fb_helper_restore_fbdev_mode_unlocked: too few arguments)Possibly taken @Berbe claimed this 18 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
VirtualBox/virtualbox#918 · 9 comments ·
Maintainers usually reply within 6 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
VirtualBox/virtualbox#995 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
VirtualBox/virtualbox#994 ·
Maintainers usually reply within 6 days
All issues in VirtualBox/virtualbox
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ESPresense/ESPresense#2680 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ImageMagick/ImageMagick#9134 ·
Maintainers usually reply within 1 day
-
Builder: a structure opened without calculation data shows the Diffraction (fibre) view by defaultOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
FriendsofECCE/ECCE#1245 · 1 comment ·
-
Arch: ARM/AArch64 Doc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
RT-Thread/rt-thread#12082 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/nuttx-apps#4108 · 4 comments ·
Maintainers usually reply within 1 day