[Bug]: VM fails to start with VERR_INVALID_NAME (-104) in supR3HardenedWinReSpawn (Windows 11 25H2, AMD)
Los mantenedores suelen responder en 6 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- c
- Área
- backend, operating-systems
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- C
- Estrellas
- 1.4k
- Forks
- 219
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de VirtualBox/virtualbox
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
VirtualBox/virtualbox#996 ·
Los mantenedores suelen responder en 6 días
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
VirtualBox/virtualbox#979 ·
Los mantenedores suelen responder en 6 días
-
[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)Posiblemente ocupada @Berbe la tomó hace 18 días. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
VirtualBox/virtualbox#918 · 9 comentarios ·
Los mantenedores suelen responder en 6 días
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
VirtualBox/virtualbox#995 ·
Los mantenedores suelen responder en 6 días
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
VirtualBox/virtualbox#994 ·
Los mantenedores suelen responder en 6 días
Todos los issues de VirtualBox/virtualbox
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
ESPresense/ESPresense#2680 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
ImageMagick/ImageMagick#9134 ·
Los mantenedores suelen responder en 1 día
-
Builder: a structure opened without calculation data shows the Diffraction (fibre) view by defaultAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
FriendsofECCE/ECCE#1245 · 1 comentario ·
-
Arch: ARM/AArch64 Doc
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
RT-Thread/rt-thread#12082 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
apache/nuttx-apps#4108 · 4 comentarios ·
Los mantenedores suelen responder en 1 día