VBox 7.1.6 on Windows Error In supR3HardenedWinSpawn

[marcelomarques]

Hello,

I have a physical machine with Windows 10 22H2 that is running Virtual Box 7.1.4.

I need to install Virtual Box 7.1.6 because it has the fix for Windows 11 24H2.

VMM: Fixed issue when Windows 11 24H2 guest was experiencing BSOD in rare conditions

​https://forums.virtualbox.org/viewtopic.php?t=113059

I installed Virtual Box 7.1.6 on my machine. I opened a cmd window as administrator, executed the installer, and the installation was successful, after that, I rebooted the machine.

I then opened Virtual Box 7.1.6 and try to start an existing VM and I got an error.

---

Virtual Box - Error In supR3HardenedWinReSpawn

NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)

Make sure the kernel module has been loaded sucessfully.

where: supR3HardenedWinReSpawn what: 3 VERR_OPEN_FAILED (-101) - File/Device open failed. Driver is probably stuck stopping/starting. Try 'sc.exe query vboxsup' to get more information about its state. Rebooting may actually help.

---

If I uninstall Virtual Box 7.1.6 and reinstall 7.1.4 then the VM starts fine again.

Has anybody else seen this issue? Any workaround available?

[agilis]

I am experiencing the same issue as ticket reporter - Microsoft Windows 22H2.

[gcharles]

I see the same issue, running Windows 11 Pro, 24H2, OS build 26100.2894 and VirtualBox Ver 7.1.6 r167084 (Qt6.5.3). My Windows 11 build is almost perfectly clean from scratch as the purpose of the build is to run a particular VM. I have seen the same issue on: 1) VM which runs successfully on the current latest release for ubuntu 24.04 LTS 2) A 2nd VM from another source.

[ilp]

I've had the same problem since upgrading to version 7.1.6 on Windows Pro 24H2.

It seems that you have to start the VirtualBox service manually with the command: net start vboxsup

[pentagonik]

Reproduced the issue, working on a fix.

[pentagonik]

I've uploaded new 7.1 test builds which can be found here: https://www.virtualbox.org/wiki/Testbuilds

VirtualBox 7.1 builds >= 167262 should fix the issue.

Please let me know if that fixes the issue for you.

[hammertime]

Hi,

I was also experiencing this symptom on a Windows 10 Pro 22H2 (OS Build 19045.5371) host, when upgrading from VirtualBox 7.1.4 to 7.1.6.

Try 'sc.exe query vboxsup' to get more information about its state.

VirtualBox 7.1.4:

PS C:\Windows\system32> sc.exe query vboxsup

SERVICE_NAME: vboxsup
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

VirtualBox 7.1.6 symptom:

PS C:\Windows\system32> sc.exe query vboxsup
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.

Rebooting may actually help.

It' didn't make a difference for me :/

Workaround

(stumbled upon this approach while trying to verify the workaround provided by ilp)
The following steps worked for me

1. Manually uninstall VB 7.1.4
2. Manually install 7.1.6
3. Reboot
4. Open VB as usual, and the symptom was gone for me :)

[ilp]

For me, it seems to work. But, strangely, I don't have the “vboxsup” service in the list of services.

When I search for info on the “vboxsup” service, I get this :

PS C:\Users\ilpla> Get-Service vboxsup

Status   Name               DisplayName
------   ----               -----------
Running  vboxsup            VirtualBox Service

But, when I search for “vbox*” services, I get this:

PS C:\Users\ilpla> Get-Service "vbox*"

Status   Name               DisplayName
------   ----               -----------
Running  VBoxSDS            VirtualBox system service

Same using WMI:

PS C:\Users\ilpla> Get-CimInstance -ClassName win32_service | Select Name,DisplayName,State,PathName | Where-Object {$_.Name -like 'vbox*'}

Name    DisplayName               State   PathName
----    -----------               -----   --------
VBoxSDS VirtualBox system service Running "C:\Program Files\Oracle\VirtualBox\VBoxSDS.exe"

Replying to pentagonik:

I've uploaded new 7.1 test builds which can be found here: https://www.virtualbox.org/wiki/Testbuilds

VirtualBox 7.1 builds >= 167262 should fix the issue.

Please let me know if that fixes the issue for you.

[pentagonik]

That looks good. “vboxsup” does not appear in the list of services as it's a driver and not a regular (user) service.

[ilp]

I've tried the new test build version 7.1.7-167370-Win, and I get the supR3HardenedWinReSpawn error again:

VirtualBox - Error In supR3HardenedWinReSpawn

NtCreateFile(\Device\VBoxDrvStub) failed: -5657 (rcNt=0xe986e9e7)<br>VBoxDrvStub error: Signature #1/1: Not signed with the build certificate (serial 0a a1 8f 63 f9 6f 11 77 1c bb 0b 43 e4 d6 90 b8, expected 06 0e 2f 8f 9e 1b 8b e5 18 d5 fe 2b 69 cf cc b1): \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe (rc=-5657)

Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn what: 3 VERR_SUP_VP_NOT_SIGNED_WITH_BUILD_CERT (-5657) - The image is required to be signed with the same certificate as the rest of VirtualBox.

[pentagonik]

@lip Can you please retry with the latest 7.1 test build, if this fixes the issues for you?

https://www.virtualbox.org/wiki/Testbuilds

[galitsyn]

Hello,

We just released VirtualBox 7.1.8 which is available on the Downloads page. This issue should be fixed in this version.

[solmyr]

It's not fixed. I just installed 7.1.8 and got this exact error.

[solmyr]

Replying to solmyr:

It's not fixed. I just installed 7.1.8 and got this exact error.

After a reboot the issue disappeared!