PS> Get-ItemProperty HKLM:\system\currentcontrolset\services\vboxdrv The installer registers an incorrect location for the driver SYS file (the ImagePath in this example). This was an example of how to fix the error: NtCreateFile(\Device\VBoxDrvStub) failed – Error opening VBoxDrvStub: STATUS_OBJECT_NAME_NOT_FOUND.There’s something wrong with the installation of VirtualBox (I’ve been seeing reports of this problem as far back as 4.x). Note: If you don’t have the VBoxDrv.inf file, then I would suggest uninstalling and installing again the VirtualBox.Īfter the installation, no need to restart the computer, just try again to build the Vagrant machine and it should work now. That’s it! Now try again “ vagrant up” to build the machine, or go to the VirtualBox and run it from there. The next step is to open a Command Prompt as administrator and type in the following: sc start vboxdrv. Open the vboxdrv folder and find the file VBoxDrv.inf. The full path is usually: C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv. This means that you need to install the vboxdrv driver located inside the VirtualBox/drivers directory. The error messages that we need to look at are : “ NtCreateFile(\Device\VBoxDrvStub) failed” and “ Error opening VBoxDrvStub: STATUS_OBJECT_NAME_NOT_FOUND“. Rebooting may actually help.ĥd3c.6988: supR3HardenedWinCheckChild: enmRequest=2 rc=-101 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries) Try 'sc.exe query vboxdrv' to get more information about its state. I see the following: 23dc.4d1c: Error opening VBoxDrvStub: STATUS_OBJECT_NAME_NOT_FOUNDĢ3dc.4d1c: supR3HardenedWinReadErrorInfoDevice: NtCreateFile -> 0xc0000034Ģ3dc.4d1c: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)Ģ3dc.4d1c: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)ĭriver is probably stuck stopping/starting. VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
More details may be available in 'C:\Users\username\VirtualBox VMs\deployment_default_1650528653505_23803\Logs\VBoxHardening.log'
Stderr: VBoxManage.exe: error: The virtual machine 'deployment_default_1650528653505_23803' has terminated unexpectedly during startup with exit code 1 (0x1). The command and stderr is shown below.Ĭommand: I’m working a lot with VirtualBox and Vagrant these days, and lately, I’ve started to get the following error when starting up the Vagrant machine with the “ vagrant up” command: There was an error while executing `VBoxManage`, a CLI used by Vagrantįor controlling VirtualBox.
0 kommentar(er)
