Opened 7 years ago
Last modified 5 years ago
#17811 new defect
VirtualBox (vboxdrv) installation FAILED on some Windows 7 PCs
Reported by: | Technologov | Owned by: | |
---|---|---|---|
Component: | installer | Version: | VirtualBox 5.2.12 |
Keywords: | vboxdrv installer | Cc: | |
Guest type: | other | Host type: | Windows |
Description
Hi All,
I'we got a new Win 7 PC: Toshiba Z40-C laptop with Intel Core i7 6600U CPU. VirtualBox 5.2.12 (latest), but also tried 5.1.38 and 5.0.40, with the same problem. (and even the ancient 4.1.6 version from 2011, before hardening)
One thing is special about this particular Windows 7 PC: It uses UEFI. All the other dozens of my Windows 7 PCs, where VirtualBox works like a charm, all use BIOS. Maybe some kind of security properties do differ somehow.
VBox.log: https://www.dropbox.com/s/8ss3510bofy4ntd/vbox.log.txt?dl=0
The problem is: no matter what I do, "vboxdrv" never gets installed.
It says cannot start VM : "Make Sure the kernel module has been loaded successfully".
Error in supR3HardenedWinReSpawn NtCreateFile(\Device\VBoxDrvStub) failed
Looking at a list of drivers in "Device Manager", I cannot see "vboxdrv" listed there. (Even with show hidden -> Non-plug-n-play devices)
More info: C:\Users\Alexey>sc.exe query vboxdrv
SERVICE_NAME: vboxdrv TYPE : 1 KERNEL_DRIVER STATE : 1 STOPPED WIN32_EXIT_CODE : 2 (0x2) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0
It seems there is a conflict between VirtualBox and some other software / device driver on my PC, or OS configuration. But how to figure it out ? The PC is totally new, but it has a lot of Toshiba drivers & utils included. Restarting the PC (the Windows way) didn't help either.
Registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxDrv
DisplayName=VBox Support Driver ImagePath=\??\C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys ErrorControl=1 Start=3 Type=1
Event Viewer:
System/Information --- A service was installed in the system. Service Name: VBox Support Driver Service File Name: C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys Service Type: kernel mode driver Service Start Type: demand start Service Account: --- System/Error The VBox Support Driver service failed to start due to the following error: The system cannot find the file specified.
In reality the driver file exists:
C:\Windows\System32\drivers\vboxdrv.sys and C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv.sys
yet, it is completely absent from Windows Device Manager (driver list). So the driver was copied, but not loaded.
-Alexey Eromenko "Technologov". 08.06.2018.
Attachments (4)
Change History (8)
by , 7 years ago
Attachment: | vbox.log.txt added |
---|
comment:1 by , 7 years ago
Great advance in my research : On my exact same laptop, downgrading my 8TB SSD (Micron 5100 series) to a simple 1TB HDD (Seagate Barracuda) let's VirtualBox work! I keep UEFI+GPT boot. So UEFI+GPT is not a problem. Big system disk is.
So, is it VirtualBox doesn't like big storage for system disk ? (>2TiB)
comment:2 by , 7 years ago
NOTE: I am willing to provide said hardware for remote debug (TeamViewer).
comment:3 by , 7 years ago
Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=88245
vbox.log