Version
7.2.14
Host OS Type
macOS
Host OS name + version
macOS 26.6
Host Architecture
ARM
Guest OS Type
Windows
Guest Architecture
ARM
Guest OS name + version
Windows 11 25H2
Component
Unspecified
What happened?
On VirtualBox 7.2.14 running on an Apple Silicon Mac, configuring an EFI Windows ARM64 VM with:
VBoxInternal/Devices/efi/0/Config/DmiSystemSerial
causes the VM to fail during startup with:
VBoxManage: error: Configuration error: Querying "UUID" failed (VERR_CFGM_VALUE_NOT_FOUND)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
The DMI serial value is successfully accepted into the EFI configuration tree and appears correctly in VBox.log, but the VM cannot start.
Removing the DMI serial override immediately restores normal VM startup.
This prevents using a VirtualBox Windows ARM64 VM for testing Windows Autopilot scenarios that require a usable BIOS/SMBIOS serial number.
How can we reproduce this?
- Create a Windows 11 ARM64 VM on an Apple Silicon Mac.
- Configure the VM to use EFI firmware.
- Confirm the VM starts normally.
- Power off the VM.
- Set an EFI DMI serial number:
VBoxManage setextradata "VB-Windows" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "VB-57335a386415"
- Confirm the setting:
VBoxManage getextradata "VB-Windows" enumerate
- Expected:
Key: VBoxInternal/Devices/efi/0/Config/DmiSystemSerial, Value: string:VB-57335a386415
- Start the VM:
VBoxManage startvm "VB-Windows"
- Observe:
VBoxManage: error: Configuration error: Querying "UUID" failed (VERR_CFGM_VALUE_NOT_FOUND)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
- Remove the serial override:
VBoxManage setextradata "VB-Windows" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial"
- Start the VM again.
- The VM starts successfully.
Did you upload all of your necessary log files, screenshots, etc.?
Version
7.2.14
Host OS Type
macOS
Host OS name + version
macOS 26.6
Host Architecture
ARM
Guest OS Type
Windows
Guest Architecture
ARM
Guest OS name + version
Windows 11 25H2
Component
Unspecified
What happened?
On VirtualBox 7.2.14 running on an Apple Silicon Mac, configuring an EFI Windows ARM64 VM with:
VBoxInternal/Devices/efi/0/Config/DmiSystemSerialcauses the VM to fail during startup with:
The DMI serial value is successfully accepted into the EFI configuration tree and appears correctly in VBox.log, but the VM cannot start.
Removing the DMI serial override immediately restores normal VM startup.
This prevents using a VirtualBox Windows ARM64 VM for testing Windows Autopilot scenarios that require a usable BIOS/SMBIOS serial number.
How can we reproduce this?
VBoxManage getextradata "VB-Windows" enumerateKey: VBoxInternal/Devices/efi/0/Config/DmiSystemSerial, Value: string:VB-57335a386415VBoxManage startvm "VB-Windows"VBoxManage setextradata "VB-Windows" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial"Did you upload all of your necessary log files, screenshots, etc.?