Windos 10 Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE)

[7.3Ford]

After upgrading Windows PC from Windows 8.1 to Windows 10, I get the following error start Oracle Linux 5 VM.

Failed to open a session for the virtual machine BigJohn-VM.
Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I have Virtual Box 5.0.0 r101573

If I keep trying to start it sometimes it will run, other times it causes the PC to lockup and core dump.

[7.3Ford]

Well I may have found a fix. Under User Interface --> Devices --> Unchecked Webcams and Floppy Drives.

My VM starts without issue now.

[Perryg]

I believe they have a fix for this instead of your workaround. It should be available in the next maintenance release and you should be able to enable the devices after that.

[7.3Ford]

Well today same message when trying to start Oracle Unix 5. Tried 4-5 times, and last time I checked all the devices and it started.

[sybrandb]

Same problem here. I'm on 5.0.2.r102096

I applied the fix described above to two VMs running Ubuntu, no luck.
I also have an Oracle Developer Day machine imported and it fails with LoadLibrary 1114.
This also seems to be a Virtualbox 5 issue.

[7.3Ford]

Update:

Seems to be related to changing something so the setting save.

I continue to get same error, but if I change a setting, any setting enough times, it will finally start or cause my PC go to Blues screen of death with a message DPC_WATCHDOG_VILOATION.

[TerryR]

I am experiencing the issue as well. I have 4 VMs setup in the VirtualBox Console and I'm hosting that in WIndows 10. If I start several VMS at once, I can usually get past the error, but if I am trying to start one at a time I experience this error.

So as quickly as I can in succession I start my Windows AD VM, SQL Server 2012 VM, TeamFoundation Server 2012 VM. If one of them actually starts, but the others fail, I can then restart the failed VMs and they work.

Each of my VMS worked flawlessly until I upgraded to Windows 10 host, mind you, I was warned that the Windows 10 was not supported at the time I upgraded. Hopefully, someone here had found how to solve the issue, If not I will keep checking back.