All versions of VB on Windows 10 TP give kernel module error

[wirespring]

Hello all,

I had been running VB 4.3.22 on Windows 10 Technology Preview Build 10041 with no apparent problems. When I upgraded to the most recent build (10049), VB would no longer load, giving me an error message that I unfortunately did not write down (though I now know it was due to the TAP driver, which I manually fixed in the registry).

Instead, I uninstalled/reinstalled using VB 4.3.24 and fired up a VM. It immediately errored out with:

NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -626
(0xfffffd8e)(rcNt=0xe986fd8e)
VBoxDrvStub error:RTLdrOpenWithReader failed -626
(Image='\Device\HarddiskVolume2\Windows\System32\ntdll.dll').
(rc=-626)
Make sure the kernel module has been loaded successfully

And then in another dialog popup:

Result Code:
E_FAIL (0x80004005)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}


I've subsequently tried the following:
- Running as administrator
- Running in all of the available compatibility modes (as administrator)
- Downgrading to 4.3.12 and running with compaibility/adminstrator
- Downgrading to 3.2.26 and running with compaibility/adminstrator
- Upgrading to 5.0 Beta and running with compaibility/adminstrator
- The manual driver installation tip from this thread: viewtopic.php?f=6&t=46845

In all of these cases I had to disable installation of bridged network drivers because of the known TAP issue or else the installer would fail. However, host-only or even no network would be sufficient for my needs right now (as I expect TAP will be fixed in the next Win 10 build).

I followed this lead:
viewtopic.php?f=6&t=64107#p307514

to look for the location of my vboxdrv ImagePath only to discover that HKEY_LOCAL_MACHINE\system\currentcontrolset\services\vboxdrv does not exist. So it seems like the driver isn't getting installed for some reason.


Does anyone have any suggestions about what I might try next to fix this?

[Hybrael]

I'm on the same boat, were you able to find a work around for this issue ?