Error In supR3HardenedWinReSpawn: 0xc000000e STATUS_NO_SUCH_DEVICE

[xerces8foo]

VirtualBox 6.1.30
Windows 10 21H2


Today, when I tried to (re) start a paused ("Saved") VM, I got these error dialogs, one after another:

---------------------------
VirtualBox - Error In supR3HardenedWinReSpawn
---------------------------

NtCreateFile(\Device\VBoxDrvStub) failed: 0xc000000e STATUS_NO_SUCH_DEVICE (163 retries) (rc=-101)

Make sure the kernel module has been loaded successfully.
where: supR3HardenedWinReSpawn
what:  3
VERR_OPEN_FAILED (-101) - File/Device open failed.

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.

Code: Select all

Failed to open a session for the virtual machine foobar.

The virtual machine 'foobar' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\VMs\virtualbox\foobar\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Also:

Code: Select all

>sc.exe query vboxdrv

SERVICE_NAME: vboxdrv
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 3  STOP_PENDING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

The same error happens when trying to start another VM that is "Powered Off".

The last lines of VBoxHardening.log are:

Code: Select all

9994.b3e0: Log file opened: 6.1.30r148432 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa04a6400
9994.b3e0: supR3HardenedVmProcessInit: uNtDllAddr=00007ffc02490000 g_uNtVerCombined=0xa04a6400 (stack ~00000000005bf5d8)
9994.b3e0: ntdll.dll: timestamp 0x1be73aa8 (rc=VINF_SUCCESS)
9994.b3e0: New simple heap: #1 0000000000900000 LB 0x400000 (for 2052096 allocation)
9994.b3e0: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume3\Program Files\Oracle\VirtualBox'
b628.7b10: supR3HardNtEnableThreadCreationEx:
9994.b3e0: System32:  \Device\HarddiskVolume3\Windows\System32
9994.b3e0: WinSxS:    \Device\HarddiskVolume3\Windows\WinSxS
9994.b3e0: KnownDllPath: C:\WINDOWS\System32
9994.b3e0: supR3HardenedVmProcessInit: Opening vboxdrv stub...
9994.b3e0: Error opening VBoxDrvStub:  STATUS_NO_SUCH_DEVICE
9994.b3e0: supR3HardenedWinReadErrorInfoDevice: NtCreateFile -> 0xc000000e
9994.b3e0: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
9994.b3e0: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc000000e STATUS_NO_SUCH_DEVICE (162 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
b628.7b10: supR3HardenedWinCheckChild: enmRequest=2 rc=-101 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc000000e STATUS_NO_SUCH_DEVICE (162 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
9994.b3e0: KiUserExceptionDispatcher: 0xc0000005 (0000000000000001, 0000000000000024) @ 00007ffc024f3416 (flags=0x0)
  rax=0000000000000000 rbx=00007ffc025fa3c0 rcx=00007ffc025fa3c0 rdx=00000000fffffffa
  rsi=0000000000000000 rdi=00007ffc025fa000 r8 =0000000000000000 r9 =00007ffc025fa300
  r10=0000000000000000 r11=00000000005b8e70 r12=0000000000000000 r13=00000000007b3000
  r14=0000000000000001 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffc024f3416 rsp=00000000005b8cd0 rbp=00000000ffffff00    ctxflags=0010005f
  cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b    eflags=00010213   mxcrx=00001f80
   P3=00000000005b8620  P4=0000000000000000  P5=00007ff6f875c3e8  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
b628.7b10: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
b628.7b10: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc000000e STATUS_NO_SUCH_DEVICE (162 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.

I have two other VM running currently, with apparently no problems.

Is there a way out without a reboot?

VBoxHardening.log attached in ZIP.

[xerces8foo]

Got the same error again today.

Differences:

VB version: 6.1.34

The VM I tried to start was "Powered Off".

sc.exe query vboxdrv
returns:

Code: Select all

[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.

Again, I have two other VMs running without issues.

Hardening log attached.

[scottgus1]

This sort of thing happens when Virtualbox isn't installed properly. That you have some VMs working and others not could mean it's a problem with a piece of Virtualbox not used in the working VMs (just a guess).

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.

[fth0]

sc.exe query vboxdrv

FWIW, in VirtualBox 6.1.34 (and newer), you'll have to use sc.exe query vboxsup instead. Looks like someone forgot to adapt a few texts.

[xerces8foo]

what I did was: reinstall Virtualbox

And now it works.

Details:
- stop all VMs
- run (as admin*) VirtualBox-6.1.34-150636-Win.exe
- select more or less the defaults
- finish installation
- run virtualbox
- it works

* not really needed as it asks for admin UAC even when started by a doubleclick, the file has a small shield icon, I guess it has the manifest that makes Windows run it as admin

[scottgus1]

* not really needed as it asks for admin UAC

Theoretically, even according to the devs. On the forum, tons of users report multiple failed attempts to install Virtualbox with a typical double-click start, which a forum-recommended right-click-Run-As-Admin start knocks loose and succeeds. For whatever ethereal reason, it works. Eh, whatcha gonna do?

Glad you're up and running!

[xerces8foo]

It happened again today.


Timeline:
- (re)install vbox (I did that yesterday as described above)
- start 3 VMs : all work
- stop VM #3
- today: start VM #3
- result: same error as above
- starting some other powered off VMs also fails the same way
- the VMS #1 and #2 started yesterday still work without any issues

Code: Select all

sc.exe query vboxsup

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

Code: Select all

C:\Windows\System32\drivers>dir vbo*
 Volume in drive C is Win10main
 Volume Serial Number is XXXX-XXXX

 Directory of C:\Windows\System32\drivers

19.07.2022  15:50           242.656 VBoxNetAdp6.sys
19.07.2022  15:50           252.560 VBoxNetLwf.sys
22.03.2022  19:19         1.046.392 VBoxSup.sys
22.03.2022  19:20           189.256 VBoxUSBMon.sys
               4 File(s)      1.730.864 bytes
               0 Dir(s)  199.333.146.624 bytes free

[xerces8foo]

This sort of thing happens when Virtualbox isn't installed properly. That you have some VMs working and others not could mean it's a problem with a piece of Virtualbox not used in the working VMs (just a guess).

Uninstall Virtualbox and reboot.

First hint: when uninstalling, I noticed it said "version 6.1.36" while I installed 6.1.34

Maybe the IT department (or someone/something else) silently updated Virtualbox, while VMs were running. Does that make sense?

[xerces8foo]

Yep, we have MS Company Portal installed, and there I can see there is an update for Oracle VM Virtualbox version 6.1.36 listed.

Any suggestions how to resolve this?
Run all VMs all the time?
Periodically restart VMs or even the host?

[xerces8foo]

And the confirmation: right now I noticed this system (Windows) notification (on the host):

Microsoft Intune Management Extension

Update for ... virtualbox 6.1.36 ... was installed ... requires restart...


This is in the notifications bar on the right of desktop. I guess I missed them last time. They probably appear for a few seconds and then disappear.