I was using the latest build 6.1.34 and decided to try the newer build. I was experiencing an audio error and hoped it would be resolved in the newer build. But when I try to power-on my Windows VM, I get several error messages and there is a log file referenced. I am attaching the log file.
NtCreateFile(\Device\VBoxDrvStub) failed 0xc0000034 supR3HardenedWinRespawn what: 3
VERR_OPEN_FAILED (-101)
Host PC: Windows 11 build 22621, Ryzen 5950X, Asrock x570 Creator, 64GB RAM, 850 watt EVGA Supernova, Radeon VII, 2 X 1TB M.2 PCIe4 disks.
Crash Report With Build 6.1.35 R151573
Crash Report With Build 6.1.35 R151573
- Attachments
-
- VBoxHardening.log
- (22.86 KiB) Downloaded 358 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Crash Report With Build 6.1.35 R151573
It appears the upgrade might not have worked.
Uninstall Virtualbox and reboot.
Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
Reboot again.
If you have any 3rd-party security or anti-malware software, disable the living daylights out of it for a moment.
Reinstall Virtualbox using right-click-Run-As-Administrator.
Since you're using test builds, it's recommended that you save the test build installer until you up/downgrade later.
Uninstall Virtualbox and reboot.
Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
Reboot again.
If you have any 3rd-party security or anti-malware software, disable the living daylights out of it for a moment.
Reinstall Virtualbox using right-click-Run-As-Administrator.
Since you're using test builds, it's recommended that you save the test build installer until you up/downgrade later.
-
- Volunteer
- Posts: 5690
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Crash Report With Build 6.1.35 R151573
Note that the VirtualBox Windows test builds cannot execute VMs when UEFI Secure Boot is enabled on the host.
Additionally, Windows Insider Preview Builds are generally not supported, so VirtualBox is not guaranteed to work on them.
Additionally, Windows Insider Preview Builds are generally not supported, so VirtualBox is not guaranteed to work on them.
Re: Crash Report With Build 6.1.35 R151573
Since build 22621 could have been the culprit, I booted a handy USB Win 11 that is running build 22000.708, not an Insider Preview build. The exact same thing happened.
It appears user fth0 hit on the problem: UEFI Secure Boot was enabled on the host BIOS. I disabled that and things worked as expected on build 22621. With Secure Boot enabled, VBox 6.1.35 is unable to start a VM, but 6.1.34 is able to start a VM.
Mystery solved. Thank-you.
It appears user fth0 hit on the problem: UEFI Secure Boot was enabled on the host BIOS. I disabled that and things worked as expected on build 22621. With Secure Boot enabled, VBox 6.1.35 is unable to start a VM, but 6.1.34 is able to start a VM.
Mystery solved. Thank-you.
-
- Volunteer
- Posts: 5690
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Crash Report With Build 6.1.35 R151573
You're welcome, and thanks for reporting back!
-
- Posts: 312
- Joined: 21. Apr 2010, 10:39
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Windows XP, 8, 10, Android x86
Re: Crash Report With Build 6.1.35 R151573
FYI, you can bypass having to disable secureboot by enabling the UpgradedSystem dword on 22000 and 22621
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CI\Policy]
"UpgradedSystem"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CI\Policy]
"UpgradedSystem"=dword:00000001
-
- Volunteer
- Posts: 5690
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Crash Report With Build 6.1.35 R151573
Thank you for this hint, which also works on Windows 10.