VirtualBox

Opened 13 years ago

Last modified 12 years ago

#9737 closed defect

Starting a virtual machine returns VERR_LDR_MISMATCH_NATIVE error. — at Version 3

Reported by: Marcin Floryan Owned by:
Component: VM control Version: VirtualBox 4.1.4
Keywords: Cc:
Guest type: Linux Host type: Windows

Description (last modified by Frank Mehnert)

A fresh installation of VirtualBox 4.1.4 on Windows 7 32-bit An attempt to run any virtual machine results in the following error:

Failed to open a session for the virtual machine openSuSE-12.1.

Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}

It works when VirtualBox is started as Administrator.

The user logged in already has a local administrator rights on the machine.

Change History (5)

by Marcin Floryan, 13 years ago

Attachment: VBox.log added

Log file describing the problem

by vs40fresh, 13 years ago

Attachment: vbox.log added

comment:1 by vs40fresh, 13 years ago

This is also happening for me.

I'm trying to upgrade my install from 3.1.4.0 r57640 to 4.1.8 r75467. My host OS is Win7.

I'm running with UAC disabled, using an Administrator account, and have no VirtualStore directory. Running as admin using the right click context menu makes no difference. Running with UAC enabled as either a Standard User or Administrator makes no difference. I've made sure all previous installed files and folders are removed, prior to installing 4.1.8, but yet the problem still occurs.

It sounds like why most users are saying running as administrator works for them is because when they do that, they then have permissions to modify the Program Files directory, and VirtualBox is no longer using some stale data/config information that may have been left behind from the previous installation. This isn't really a solution, it's more like a temporary workaround.

comment:2 by Dhjohn, 12 years ago

Have just loaded the latest update, and this problem has suddenly appeared. The reason for failure seems clunky, better design needed.

comment:3 by Frank Mehnert, 12 years ago

Description: modified (diff)

Can only be some installation issue. Is the problem reproducible if after you uninstalled and re-installed VirtualBox?

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette