[Issue] VirtualBox working on and off on Windows 10

[Aura]

Is there anyone else that uses VirtualBox under Windows 10 here? I used it since I upgraded and it always worked just fine, without any issues. Now, since the last Patch Tuesday (where I also installed Emsisoft Anti-Malware), VirtualBox cannot launch any of my Virtual Machine anymore for whatever reason there is. This is the error message I'm getting:

Code: Select all

Cannot load R0 module C:\Program Files\Oracle\VirtualBox/VBoxDDR0.r0:
SUPR3LoadModule: supLoadModule returned VERR_LDR_MISMATCH_NATIVE (VERR_LDR_MISMATCH_NATIVE).

Failed to register ourselves as a PCI Bus (VERR_MODULE_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interace: IConsole 872da645-4a9b-1727-bee2-5585105b9eed

Note: I copy/pasted this error message from a screenshot on the web since right now my VMs are working, but when the error will comeback on the next reboot I'll post an actual screenshot of the error message.

The issue is a 0x05 code, which means "Access denied". And from the looks of it, it seems that VirtualBox cannot create a PCI device (virtual one I guess) for the VM I'm opening and it fails to launch. I have a few ideas of what could cause this but I'm still investigating.

So far, I tried a lot of solutions, and some works, some doesn't but everytime I restart my computer, I have to use a different one.

• Upgraded VirtualBox to the latest version (which is 5.0.2);
• Launched VirtualBox as an Admin, and with normal user rights;
• Deleted a VM from the list and added it back;
• Boot a VM that is shut down, and not restore a snapshot;

The thing is that if I can get one VM to open, past the error message, the rest will open as long as I don't shutdown my computer. I have no idea of what causes this and I'm interested in knowing if some users here uses VirtualBox and if they encountered the issue.

On a side note, I know that VirtualBox isn't officially compatible with Windows 10 yet, but I find it weird that it worked flawlessly until a few days ago.

Anyhow, I'll keep on posting my findings here and hopefully find a solution that will work everytime, or wait until a patch is released if this is a known issue/bug.

[Giusi]

this is the proof that the most issue isn't due to hw..but is the interactivity between vb and win 10..probably the last win updates make yr issue..have you try to unistall them..?

[Aura]

I'm not really a fan of uninstalling Windows Update sadly, even less when they are cumulative so I'll avoid that solution. If I must find a workaround until a patch is released so be it, but I know what a mess it can be when you uninstall Windows Update, and I would rather deal with my current VirtualBox than that situation.

I'm mainly wondering if other users have that issue and if so, what kind of solutions they are using. Maybe I should open a ticket as well and see what comes out of it.

[frank]

The VERR_LDR_MISMATCH_NATIVE error should be fixed with the latest Windows test build from here. Please confirm!

[Aura]

I'm at work right now so I cannot check. However, when I get home tonight, I'll try to open a VM to see if I get the error, and when I do, I'll upgrade to the latest test build and let you know if it works or not. From there if it works I'll keep it in monitoring and see if it still works after a restart.

I'll let you know, thank you Frank

[Aura]

Just got back home, tried to open a VM and got the error message.

Code: Select all

Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE).

Code d'erreur : 
E_FAIL (0x80004005)
Composant : 
ConsoleWrap
Interface : 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Will now proceed to install the latest test build, restart and see what happens.

[Aura]

Installed the latest test build (5.0.3 build 102224), restart my computer and my VMs opened on first try. Thank you.

This is under Windows 10 Professional x64.

[jeffmorlen]

I ran into this same problem yesterday when I tried to spin up a new Debian Linux VM.
My solution, as simple as it is, was to merely shut down VB and restart it.

I am on the latest build of VB and latest patches for Win10.