[Bug]: VM fails to start with VERR_INVALID_NAME (-104) in supR3HardenedWinReSpawn (Windows 11 25H2, AMD)
維護者通常 6 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 35/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- c
研究方向
Start with the attached VBoxHardening log and the VERR_INVALID_NAME failure in supR3HardenedWinReSpawn during Respawn #1; the issue does not identify a source file or test. Reproduce by creating an empty VM with the listed VBoxManage commands on the specified Windows host, then trace the respawn path and Windows error 5. Done means identifying and fixing why VM startup fails, with a regression check that the empty VM starts.
由索引模型根據 Issue 內容生成。
描述
Version
7.2.22
Host OS Type
Windows
Host OS name + version
Windows 11 25H2 Build 26200.9974
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
Ubuntu 24.04 LTS (64-bit)
Component
VMM
What happened?
Any VM fails to start on this Windows 11 25H2 host (AMD x86-64, UEFI + Secure Boot, VBS/HVCI enabled, Hyper-V/WSL2 present), VirtualBox 7.2.22 r175245. The VM process dies while creating the second hardening child (SUPR3HardenedMain: Respawn #1); the parent reports VERR_INVALID_NAME (-104) from supR3HardenedWinReSpawn with enmWhat=5, and VBoxSVC reports "terminated unexpectedly during startup with exit code 1 (0x1)". No VBox.log is created, only VBoxHardening.log (attached).
Key log lines:
NtOpenDirectoryObject failed on '\Driver': 0xc0000022
SUPR3HardenedMain: Respawn #1
supR3HardenedWinInit: SUPHARDNTVPKIND_SELF_PURIFICATION_LIMITED -> VINF_SUCCESS, cFixes=5
SUPR3HardenedMain: Respawn #1 - opening vboxsup stub...
supR3HardenedWinDoReSpawn(1): Spawning ...
Error -104 in supR3HardenedWinReSpawn! (enmWhat=5)
Error relaunching VirtualBox VM process: 5
Reproduces with a brand-new empty VM, see "How can we reproduce this?".
The same host ran VMs fine with 7.2.6 on 2026-11-11/12/15 (HVCI already enabled then); failures started on 2026-11-17 without any intentional change. Upgrading to 7.2.22 and a clean reinstall into C:\Program Files\Oracle\VirtualBox did not help (the failure moved from Respawn #2 to Respawn #1).
Already ruled out: VM config/disk (fresh empty VM fails), VM folder/drive, install path and directory ACL, VirtualBox version, HVCI/VBS, leftover IFEO ImageExpansionMitigation values, and third-party software (full clean boot: all non-Microsoft services disabled plus 25 third-party kernel drivers disabled) - identical failure.
Related host event: provider VBoxNetLwf, Event ID 12, "internal driver error on \Device\VBoxNetLwf" (twice on 2026-11-17).
Questions: is the Respawn spawn performed through VBoxSup? Under which conditions can it fail with Windows error 5 / VERR_INVALID_NAME? Is there any way to get more diagnostics from VBoxSup (log level / trace build)?
How can we reproduce this?
Step 1. Install VirtualBox 7.2.22 on a Windows 11 25H2 host (AMD x86-64, UEFI + Secure Boot, VBS/HVCI enabled, Hyper-V/WSL2 present).
Step 2. No VM image is needed. Create a brand-new empty VM from a command prompt:
代码块
VBoxManage createvm --name probe1 --ostype Other_64 --register
VBoxManage modifyvm probe1 --memory 64 --cpus 1 --nic1 none
VBoxManage startvm probe1 --type headless
Step 3. Observe the failure:
代码块
VBoxManage.exe: error: The virtual machine 'probe1' has terminated unexpectedly during startup with exit code 1 (0x1).
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Step 4. Optional check: VBoxManage showvminfo probe1 --machinereadable reports VMState="poweroff".
Step 5. In the GUI, starting any VM additionally shows the supR3HardenedWinReSpawn dialog with VERR_INVALID_NAME (-104); see the "What happened?" section for the full text.
Notes:
Reproduces on every attempt, deterministic.
A VBoxHardening.log is written under the VM folder's Logs directory, but no VBox.log is created — the process dies before VM initialisation.
The same host started VMs fine with VirtualBox 7.2.6 until 2026-11-15 16:33; see "What happened?" for the history and for everything already ruled out.
Did you upload all of your necessary log files, screenshots, etc.?
- Yes, I've uploaded all pertinent files to this issue.
- 主要語言
- C
- 星號
- 1.4k
- 分支
- 219
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
VirtualBox/virtualbox 的其他 Issue
-
bug
難度 1/5 1 小時以內 新手友好度 84/100
VirtualBox/virtualbox#996 ·
維護者通常 6 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 68/100
VirtualBox/virtualbox#979 ·
維護者通常 6 天內回覆
-
[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)可能已有人在做 @Berbe 於 18 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 76/100
VirtualBox/virtualbox#918 · 9 則留言 ·
維護者通常 6 天內回覆
-
bug
難度 4/5 3-5 天 新手友好度 25/100
VirtualBox/virtualbox#995 ·
維護者通常 6 天內回覆
-
bug
難度 3/5 1-2 天 新手友好度 45/100
VirtualBox/virtualbox#994 ·
維護者通常 6 天內回覆
查看 VirtualBox/virtualbox 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 80/100
ESPresense/ESPresense#2680 · 2 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
ImageMagick/ImageMagick#9134 ·
維護者通常 1 天內回覆
-
Builder: a structure opened without calculation data shows the Diffraction (fibre) view by default未關閉bug
難度 2/5 1-3 小時 新手友好度 65/100
FriendsofECCE/ECCE#1245 · 1 則留言 ·
-
Arch: ARM/AArch64 Doc
難度 1/5 1 小時以內 新手友好度 90/100
RT-Thread/rt-thread#12082 · 1 則留言 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
apache/nuttx-apps#4108 · 4 則留言 ·
維護者通常 1 天內回覆