VirtualBox 7.2.4 Fails to Start VM - Error VERR_INVALID_NAME (-104) and 0xc0000409

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Arthur_o
Posts: 1
Joined: 15. Jan 2026, 19:58

VirtualBox 7.2.4 Fails to Start VM - Error VERR_INVALID_NAME (-104) and 0xc0000409

Post by Arthur_o »

System Configuration:

Host OS: Windows 11 Professional (Build 10.0.26100.7462)
CPU: AMD Ryzen 7 9700X
RAM: 32GB
VirtualBox Version: 7.2.4 r170995
Guest OS: Kali Linux (Debian 64-bit)
BIOS Settings: AMD-V (SVM Mode) confirmed enabled in BIOS

Problem Description:
I'm unable to start any virtual machine in VirtualBox. Every attempt to launch a VM results in one of two errors:

Error VERR_INVALID_NAME (-104)

Error message: "Invalid (malformed) file/path name"
Full error: supR3HardenedWinReSpawn what: 5 VERR_INVALID_NAME (-104)

Exit Code 0xc0000409

Status: STATUS_STACK_BUFFER_OVERRUN
VM terminates immediately during startup


Troubleshooting Steps Already Attempted:
1. Hyper-V and Conflicting Features:
Disabled Hyper-V via Windows Features
Disabled Virtual Machine Platform
Disabled Windows Hypervisor Platform
Disabled Windows Sandbox
Executed: bcdedit /set hypervisorlaunchtype off
Executed: dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All
Disabled Memory Integrity (Core Isolation)
Restarted computer after each change

2. BIOS Configuration:
Confirmed AMD-V (SVM Mode) is enabled in BIOS
Secure Boot: Enabled
Virtualization verified active in system

3. VirtualBox Installation:
Completely uninstalled VirtualBox
Removed all VirtualBox folders from Program Files
Cleaned registry entries
Reinstalled VirtualBox 7.2.4 as Administrator
Also tested VirtualBox 7.0.20 (same errors)

4. VM Configuration:
Tried different VM storage locations (including paths without spaces)
Changed VM folder from C:\Users\arthu\VirtualBox VMs\ to C:\VMs\
Set Paravirtualization Interface to KVM
Verified hardware virtualization settings
Executed: VBoxManage setproperty machinefolder "C:\VMs"

5. Permissions:
Ran VirtualBox as Administrator
Verified full control permissions on VM folders
Disabled antivirus temporarily

Error Logs:

From VBox.log:
HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
VMSetError: WHvCapabilityCodeHypervisorPresent is FALSE!
VMSetError: AMD-V is not available (VERR_SVM_NO_SVM)
Power up failed (vrc=VERR_SVM_NO_SVM, hrc=E_FAIL (0X80004005))

From VBoxHardening.log:
supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000409 (STATUS_STACK_BUFFER_OVERRUN)

Error Screenshot:
The error dialog shows:
Error relaunching VirtualBox VM process: 5
Command line: 'C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe...'
VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name

Thank you very much for taking the time to help me with this issue. I really appreciate any guidance from this community.
jdelano
Posts: 4
Joined: 12. Oct 2015, 12:43

Re: VirtualBox 7.2.4 Fails to Start VM - Error VERR_INVALID_NAME (-104) and 0xc0000409

Post by jdelano »

Hey, I had this very error this morning. I uninstalled the last app I had installed (in this case AppControl from https://www.appcontrol.com/) after doing so VB worked again.

So, have a look at recent app installations / OS updates and uninstall each until you find which one is blocking VB from working.
Post Reply