Receiving error from running new VM session

Discussions related to using VirtualBox on Windows hosts.
Post Reply
dbarit
Posts: 1
Joined: 13. Dec 2017, 03:46

Receiving error from running new VM session

Post by dbarit »

I am trying to install a new VM of Ubuntu 16.04.3. However I am receiving an error message upon starting my created VM. I haven't found any related issues on the forum and would appreciate any help or guidance.

Current System: Virtual Box 5.2.2, HP Z220 Workstation, Windows 10.
Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed (VERR_LDR_GENERAL_FAILURE).

Failed to load VMMR0.r0 (VERR_LDR_GENERAL_FAILURE).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Last edited by socratis on 13. Dec 2017, 08:39, edited 2 times in total.
Reason: Removed unnecessary attachment, be more "green".
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Receiving error from running new VM session

Post by socratis »

Thank you for including some version information, but please keep in mind that "Windows 10" these days is a family of a series of "differently behaving" operating systems that changes every 6 months or so (1511, 1607, 1703, 1709, etc.), and not a single OS...
dbarit wrote:Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed (VERR_LDR_GENERAL_FAILURE).
That is one of the most fundamental files required for VirtualBox operation. The fact that it's failing to load can be due to several things:
  1. Installation
    1. Uninstall VirtualBox. Your VMs are going to be untouched. Reboot.
    2. You may want to clean up your registry and/or filesystem at this point. CCleaner is a freeware utility that could help you. Mind the installation, it comes with "offers" from 3rd parties, known as "bundleware". Also, check out Device Cleanup program that helps you to remove any unused devices from your computer.
    3. Download (if you haven't already) the latest VirtualBox and its matching ExtPack. Store them in a common location, i.e. not on "Desktop", or "Documents", but to "Public/Downloads" for example.
    4. Locate the downloaded file in Windows Explorer. Right-click on the installer and select "Run-as-Administrator", even if you are the administrator. At the end of the installation, choose to "Start Oracle VM VirtualBox". Do not worry if your VMs do not show up.
    5. If you're going to install the ExtPack, go to File » Preferences » Extensions. Click on the icon with the orange, down-pointing arrow on the right. Select the ExtPack from the previous steps.
    6. Quit VirtualBox. Re-start VirtualBox as you would normally, i.e. from the Desktop shortcut or the Start menu.
    7. Update the Guest Additions (GAs) in your guest(s), if the GAs are available for a specific guest.
  2. Wrong filesystem permissions
    Sometimes filesystem permissions get out of whack. You might need to reset them, especially in the "Program Files" directory. The following command supposedly fixes the out of order permissions, I haven't tried it personally:
    • icacls * /T /Q /C /RESET
  3. Hyper-V
    I've seen reports that this also might be due to the activation of Hyper-V. See the following article for (not a definite solution) just some ideas:
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply