locked
VirtualBox error RRS feed

  • Question

  • Hi, I have instaled virtual box 4.3.14-95030 for windows but if I try to launch it I get an error saying "Failed to instal NtCreateSection monitor: 48 b8 49 e7 e3 67 0 0 0 0 50 c3 1f 44 00 (rc=-8)". Anyone who knows hot to solve it?
    Saturday, July 19, 2014 11:00 PM

Answers

  • Beta version 4.3.15 was introduced tentatively to fix this issue, but it didn't do so for me. Only reverting to 4.3.12 worked (for me).
    • Proposed as answer by ZigZag3143x Sunday, July 27, 2014 5:54 PM
    • Marked as answer by Michael_Martin Tuesday, August 5, 2014 4:13 PM
    Sunday, July 27, 2014 5:23 PM

All replies

  • Same here, just upgraded to Windows 8.1 from 8. VirtualBox was working just fine before.

    Uninstalled VB and re-installed latest version - no change

    Deleted my old virtual machine and started a new thinking that could be the cause but even the new machine has the same fault as above.

    Host Widows 8.1 64Bit

    VM: Ubuntu 14.04 32Bit

    First message as above. Then when you hit abort you get:

    Failed to open a session for the virtual machine Ubuntu 14.x.

    <qt>

    The virtual machine 'Ubuntu 14.x' has terminated unexpectedly during startup with exit code 1.

    Result Code: <tt>E_FAIL (0x80004005)</tt>
    Component: Machine
    Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

    </qt>


    Thanks for any info!

    Sunday, July 20, 2014 11:00 AM
  • Hi,

    For this problem, I checked Virtual Box Forum, found there is plenty of similar problem with yours. It seems like software compatibility problem each other, If you installed any security software, such as MACfee, you can try to disable them temporarilly for test.

    In addition, try to reinstall Virtual Box with 4.3.12 for test.

    For the Virtual Box forum thread, you can refer to the link below:

    https://forums.virtualbox.org/viewtopic.php?f=6&t=62615


    Roger Lu
    TechNet Community Support

    Monday, July 21, 2014 2:09 PM
  • Beta version 4.3.15 was introduced tentatively to fix this issue, but it didn't do so for me. Only reverting to 4.3.12 worked (for me).
    • Proposed as answer by ZigZag3143x Sunday, July 27, 2014 5:54 PM
    • Marked as answer by Michael_Martin Tuesday, August 5, 2014 4:13 PM
    Sunday, July 27, 2014 5:23 PM
  • Hi,

    I have updated my Windows 8 to 8.1 and I have the same problem.

    I'm waiting for a virtual box patch....

    Regards,

    Pyrénées.

    Monday, July 28, 2014 7:48 AM