[Bug]: Windows 11 guests never reach the logon screen (boot spinner forever) and fresh installs fail on AMD Ryzen 5600H host; Linux guest works

Open
#984 0 comments 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
Needs clarification
Activity status
Active
Tech stack
c, linux

Research direction

No source file or test is named; start from the attached LOG.zip and the VBox.log of a hung boot, comparing the Windows 11 VM settings (EFI/Secure Boot, TPM, PIIX3, SVM) against the working Debian guest. Reproduce on the 7.2.22 host, then narrow whether the hang is in guest execution, AMD-V setup, or Guest Additions. Done means a confirmed root cause or a minimal reproducer maintainers can act on, not a speculative patch.

Written by the indexing model from the issue text.

Description

bug
Version

7.2.22

Host OS Type

Linux

Host OS name + version

Arch Linux, kernel 7.2.14-zen1 / 7.2.14-arch1 / 7.3.4-zen2

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

x86

Guest OS name + version

Windows 11 Pro 26H2, build 26300.9974

Component

Unspecified

LOG.zip

What happened?

A Windows 11 guest that was installed and working on 11 Nov 2026 (several
successful reboots, Guest Additions 7.2.22 and SQL Server installed) can no
longer complete a boot since 14 Nov 2026. Every cold boot or guest-initiated
reboot stays on the boot logo with the spinning circle indefinitely.

Observations:

  • VBox.log shows no error. The guest keeps making progress at first: Guest
    Additions drivers load, VBoxService starts about 20 s after power-on, the
    shared folder is auto-mounted, and the display driver keeps drawing the
    spinner. The logon screen never appears and VBoxTray never starts.
  • While it is stuck, the VirtualBoxVM process uses little host CPU
    (roughly 8-25 % of a 12-thread CPU), so the guest seems to be waiting
    rather than working.
  • Restoring an online snapshot (saved state) works: the Windows desktop is
    fully usable until Windows is restarted, then it hangs as above.
  • The Windows Recovery Environment boots normally in the same VM.
  • A fresh Windows 11 install in a brand-new VM (same ISO that worked on
    11 Nov) fails with "Windows 11 installation has failed", typically around
    78 %. Reproduced in three attempts.
  • A Debian 13 guest installs and reboots correctly on the same host.

Host: Medion Erazer Deputy P25 laptop, AMD Ryzen 5 5600H (microcode
0x0A500012), 32 GB RAM, NVIDIA RTX 3060 + AMD iGPU, Arch Linux, KDE Plasma
6.8.2, VirtualBox OSE from the Arch repositories (virtualbox 7.2.22-1 and
7.2.22-2, virtualbox-host-dkms), VMs stored on a SATA SSD (ext4).

Guest VM: Windows 11 Pro 26H2 build 26300.9974, 6 vCPUs, 16 GB RAM, EFI with
Secure Boot, TPM 2.0, PIIX3 chipset, AHCI, VBoxSVGA 128 MB without 3D, NAT
(82540EM), default paravirtualization interface.

What was tried, without any effect
  • Kernels 7.3.4-zen2, 7.2.14-zen1 and stock 7.2.14-arch1
  • VirtualBox packages 7.2.22-2 and 7.2.22-1 (host modules rebuilt each time)
  • Full rollback of the root filesystem (Timeshift) to its state before the
    14 Nov system update (which had brought kernel 7.3.4, openssl 4.1,
    qt6-base, mesa, nvidia 620)
  • kvm_amd/kvm loaded, and fully blocked (lsmod empty while the VM runs)
  • Nested VT-x/AMD-V off, audio disabled, TPM set to None
  • Paravirtualization interface None and Legacy
  • 4 and 6 vCPUs, 8 and 16 GB RAM, PIIX3 and ICH9 chipsets
  • Headless start (no GUI frontend)
  • "Use Host I/O Cache" on the SATA controller
  • Guest clock set back 5 days with the network adapter disabled
  • Guest Additions uninstalled; SQL Server services set to manual
  • auto-cpufreq and tuned stopped, UFW disabled
  • VirtualBox.xml (global configuration) reset and the VM re-registered

Host checks: no kernel oops or MCE in the journal, SMART clean on the SSD,
8 GB direct write at 244 MB/s without errors, all VM disk images read back
without error.
memtester 16G, 1 loop: all tests ok.

How can we reproduce this?
  1. Host as described above, VirtualBox 7.2.22.
  2. Start any Windows 11 26H2 guest from power-off, or restart Windows inside
    a restored snapshot.
  3. The guest stays on the boot spinner forever. Installing Windows 11 from
    the ISO in a new VM fails during setup instead.
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.