[Bug]: The virtual environment freezes on Windows-hosted Windows guests starting with version 7.2.8

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

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

Research direction

Start by reviewing the uploaded logs and reproducing the freeze with a Windows host and Windows guest on version 7.2.8 or later. The report gives host and guest versions and hardware details, but only says to run a virtual environment, so the trigger and affected component are not yet clear. Done means identifying the cause and confirming the guest no longer freezes under the reported conditions.

Written by the indexing model from the issue text.

Description

bug
Version

7.2.22

Host OS Type

Windows

Host OS name + version

Windows 11 Pro 25H2(2026-10 KB5127648/build:26200.9711

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

x86

Guest OS name + version

Windows 11 25H2/26H2 build:26200.9711/26300.9711

Component

Other

What happened?

The virtual environment on Windows-hosted Windows guests freezes in the
following environments and therefore cannot be used.

Ryzen 5 7640HS/Radeon 760M
Mem 32GB(16GBx2)
SSD M.2 NVMe Gen4 500GB + M.2 NVMe Gen4 1TB
Win 11 Pro 25H2(2026-10 KB5127648/build:26200.9711

Ryzen 5 7430U
Mem 24GB(8GB+16GB)OnBord + DDR4-3200 SODIMM 16GB
SSD M.2 NVMe Gen3 500GB + SATA SSD 1TB
Win 11 Pro 26H2(2026-10 KB5127648/build:26300.9711

How can we reproduce this?

Run a virtual environment.

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.