Opened 7 years ago
Last modified 7 years ago
#17591 new task
windows10 host failed to open a session for virtual machine
Reported by: | eiddy | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.2.8 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
host: OS name: Microsoft Windows 10 enterprise OS edtion: 10.0.16299 manufactor: Dell Inc. OptiPlex 790 x64-based PC
BIOS edtion: Dell Inc. A18, 2013-9-24
The virtual machine 'win10'
has terminated unexpectedly during startup with exit code -1073741819
Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
Attachments (3)
Change History (6)
by , 7 years ago
Attachment: | VBoxHardening.2.log added |
---|
comment:1 by , 7 years ago
when i install virtualbox 4.3.40, show "the selected virtual machine is inaccessible ,please inspect the error message show below and press the Rfresh button if you want o repeat the accessbility check :"
Error in C:\Users\Administrator\VirtualBox VMs\win10\win10.vbox (line 35) -- Invalid value 'XHCI' for Controller/@type attribute. F:\tinderbox\win-4.3\src\VBox\Main\src-server\MachineImpl.cpp[731] (long cdecl Machine::registeredInit(void)). Result Code: E_FAIL (0x80004005) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
comment:2 by , 7 years ago
41e0.37a0: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 235 ms, CloseEvents);
Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some guidelines/ideas.
As for the second issue, in VirtualBox 4.x.x there was no USB3 controller. So that's expected.
comment:3 by , 7 years ago
oh,i see ,thank u.but how can i solve the error in windows10 : Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
log file