Ticket #16892 (closed defect: fixed)

Opened 17 months ago

Last modified 16 months ago

Unable to start Virtual Box 5.1.22 in Window 10 Insider Build

Reported by: PaulSchulz Owned by:
Priority: major Component: VM control
Version: VirtualBox 5.1.22 Keywords:
Cc: Guest type: Linux
Host type: Windows


Unable to start Virtual Box 5.1.22 in Window 10 Insider Build

  • Recently updated Sat, 8 Jul 2017 Version 1703 (OS Build 16237.1001)

VirtualBox was working beforehand.

  • Hyper-V disabled (Windows Features)
  • Ubuntu 64bit installation.
  • Doesn't work with same error even if VirtualBox started as Administrastor

Error displayed: The virtual machine 'ubuntu' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Paul\VirtualBox VMs\ubuntu\Logs\VBoxHardening.log'.


Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

File - VBoxHardening.log - attached.


VBoxHardening.log Download (104.4 KB) - added by PaulSchulz 17 months ago.
Error log

Change History

Changed 17 months ago by PaulSchulz

Error log

comment:1 Changed 17 months ago by PaulSchulz

Reverted Windows 10 Insider Edition to previous version, and VirtualBox started working again (able to open/run virtual machines).

Windows 10 Pro Insider Edition Version 1703 (OS Build 16232.1004)

comment:2 Changed 17 months ago by Dougie

Same failure happens with VBox 5.1.23 r116680 (Qt5.6.2) on Win10 16237.1001.

I'd prefer not to revert my Win10 home insider preview back to 16232.1004.

comment:3 Changed 17 months ago by socratis

If anyone wants to follow the discussion, here's the  thread in the forums.

It's actually better if you keep an eye on the  VirtualBox on Windows pre-releases section. The issues were so many that a sub-forum had to be created especially for that reason. If there was a new bug report every time Microsoft's faster releases created a problem, your ticket now would be in the 100,000+ number... :)

comment:4 Changed 16 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in 5.1.24.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use