virtualbox.org

Sorry if this has been mentioned before or if I have posted in the wrong place but I only just found this forum and so signed up.
Last night I discovered that Virtual Box 5.0 was now available and so I upgraded my existing virtual machines.
Everything was fine until tried to upgrade the Guest Additions in my Windows 10 technical preview (On a Windows 8.1 64 bit host).
I was required to reboot the machine to complete the installation whereupon I was met by the blue screen of death. It informed me there was a problem with a driver.

I had to attach the virtual hard drive to another VM to gain access to the drive contents.
I then had to rename C:\Windows\System32\drivers\VBoxGuest.sys to be able to get my Windows 10 VM to work again.
(Taught me to take a snapshot before doing any major changes)

I may be wrong but it seems to be something to do with Windows 10 requires all drivers to be signed otherwise they get rejected by Windows.

There is no VirtualBox version currently in beta test. Moving your topic to the "Windows Guests" forum.

p.s. I suggest that you make backups before making big changes, not take snapshots.

AFAIK, all VirtualBox drivers are signed. Certainly the 64bit ones are.

I'm also having this same issue with the exact same message. It's a fresh brand new install. The only thing I did to the 10074 build install was set the Preferred DNS statically which works fine fine before I installed the guest addtitons. Yes, I do have the newest version of them installed.

duplicate?:
viewtopic.php?f=2&t=68840

"the digital signature for this file couldn't be verified."

Looks like Win10 does not know the certificate from Oracle.

I upgraded virtualbox to version 5 running on a Windows 7 64-bit host and installed Windows 10 build 10074 inside a VM.

The installation of Windows 10 was fine and the installation of the latest Guest Additions finished OK.

Upon reboot, I get the same BSoD.

I tried some Windows 10 built-in troubleshooting (startup repair, etc.) but resorted to "resetting the system" in Windows 10 parlance to get back into the VM. It took the guest OS back to factory, removing the Guest Additions. I probably could've renamed VBoxGuest.sys, but wasn't in a hurry nor did I have anything saved in the image.

This appears to be a different issue than that reported in thread 68840 where they couldn't get Windows 10 to run at all after installing it in a VM.

I'll try this again with a newer build of Windows 10 and see which side the problem is on.