Opened 8 years ago
Closed 8 years ago
#16892 closed defect (fixed)
Unable to start Virtual Box 5.1.22 in Window 10 Insider Build
| Reported by: | PaulSchulz | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 5.1.22 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
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'.
Details
Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
File - VBoxHardening.log - attached.
Attachments (1)
Change History (5)
by , 8 years ago
| Attachment: | VBoxHardening.log added |
|---|
comment:1 by , 8 years ago
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 by , 8 years ago
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 by , 8 years ago
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... :)
Error log