VirtualBox 5.2.33 installer does not install VBoxDrvStub - STATUS_OBJECT_NAME_NOT_FOUND

[Jacob Klein]

I noticed this problem trying to get VirtualBox 5.2.x working on a Windows 10 x64 Home PC that has never had VirtualBox before.

This problem happens on Windows 10 x64 Home, for both Release (v1903, Build 18362.356) and Insider Fast (Build 18980).

It's strange, because all my other PCs which are Windows 10 x64 Pro haven't had problems installing/upgrading to 5.2.33 versions. Only this PC has, and it is "new to VirtualBox".

Could something be broken on Windows 10 x64 Home only?

VirtualBox 5.2.32 Build 132073 installs fine and can run VMs fine.

The following do not work (Prompt to restart, and after restart doesn't work due to VBoxDrv): Oracle VirtualBox v5.2.33 Test Build 132166 Oracle VirtualBox v5.2.33 Test Build 132430 Oracle VirtualBox v5.2.33 Test Build 132658 Oracle VirtualBox v5.2.33 Test Build 132750 Oracle VirtualBox v5.2.33 Test Build 132969 Oracle VirtualBox v5.2.33 Test Build 133021 Oracle VirtualBox v5.2.33 Test Build 133385

The repro steps are:

• Clean Install Windows 10 x64 Home, v1903 Release
• Use Windows Update, to fully update it
• Install one of the VirtualBox 5.2.33 Test Builds
• Erroneously get prompted to restart
• Click Yes to restart
• Briefly see a strange dialog as it is restarting: "Installation failed! Error: The requested operation completed successfully. The system will be restarted so the changes can take effect."
• After restart, double-click an .ova file - I was testing with one from here: ​https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
• Click Import to add the VM instance to the Manager.
• Try to run the VM normally
• Get error messages indicating that VBoxDrvStub is not installed.

I tried the workaround here: ​https://forums.virtualbox.org/viewtopic.php?t=66442#p314829 ... but it did not work to workaround the problem.

Can anyone reproduce this? Can Oracle devs find out what is happening?

Note: The community is additionally tracking this issue here: ​https://forums.virtualbox.org/viewtopic.php?f=6&t=94816

[Jacob Klein]

Note: The community is additionally tracking this issue here: ​https://forums.virtualbox.org/viewtopic.php?f=6&t=94816

[Jacob Klein]

I found the culprit:
In the BIOS/UEFI options, I had "Secure Boot" enabled.

Once I disabled "Secure Boot", I was able to install the VirtualBox Test Builds without error, and run VMs on the Test Builds without error.

Can anything be done to improve this? Could we: Detect the "Secure Boot" status, warn the user at Test-Build-install-time if it is on, and mention "Secure Boot" if they get this error trying to start the VM on a Test Build?

... Hours of painful frustration over here, trying to track this down and log it ... all a preventable waste.