PLEASE HELP ME....
VirtualBox v 4.3.28 r100309
it says:
The virtual machine 'CS50 Appliance 2014' has terminated unexpextedly during starup with exit code 1(0x1).
ERROR
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
I'm using:
*Windows 7 Ultimate
*eMachine
*Pentium(R) Dual-Core CPU T4400 2.20 GHz
*32 bit
Failed to start
Failed to start
- Attachments
-
VBoxStartup.log- (101.43 KiB) Downloaded 1 time
Last edited by chun on 5. Jul 2015, 11:26, edited 1 time in total.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Failed to start
Post the guests log file ( as an attachment )
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Failed to start
See the "security" discussion stickied at the top of this forum.
Re: Failed to start
What "security" discussion? There is no "sticky". Perhaps a link would be more helpful.
I have a similar problem. VirtualBox 4.3.28 running on Windows 10, 32-bit, Build 10162. Attempting to start the virtual machine results in:
Failed to open a session for the virtual machine Windoze XP.
The virtual machine 'Windoze XP' has terminated unexpectedly during startup with exit code 1 (0x1).
More details may be available in 'C:\Users\Carl\VirtualBox VMs\Windoze XP\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
This did NOT occur with Build 10130. This does NOT occur with the 64-bit version. This does NOT occur with Windows7. Obviously a Windows 10 problem, but perhaps there is a Vbox work-a-round?
I have a similar problem. VirtualBox 4.3.28 running on Windows 10, 32-bit, Build 10162. Attempting to start the virtual machine results in:
Failed to open a session for the virtual machine Windoze XP.
The virtual machine 'Windoze XP' has terminated unexpectedly during startup with exit code 1 (0x1).
More details may be available in 'C:\Users\Carl\VirtualBox VMs\Windoze XP\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
This did NOT occur with Build 10130. This does NOT occur with the 64-bit version. This does NOT occur with Windows7. Obviously a Windows 10 problem, but perhaps there is a Vbox work-a-round?
- Attachments
-
- VBoxStartup.zip
- (5.74 KiB) Not downloaded yet
Last edited by cdg on 6. Jul 2015, 18:41, edited 1 time in total.
Re: Failed to start
this is the log file
- Attachments
-
VBoxStartup.log- (101.43 KiB) Downloaded 4 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Failed to start
I would have thought that "top of this forum" was a sufficient location clue, but here is the actual link: viewtopic.php?f=6&t=67840.
Re: Failed to start
The virtual machine 'CS50 Appliance 2014' has terminated unexpextedly during starup with exit code 1(0x1).
ERROR
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048} *Virtualbox
v 4.3.28 r 100309 -------------------------------------------------------------------------
I'm using:
*Windows 7 Ultimate
*eMachine
*Pentium(R) Dual-Core CPU T4400 2.20 GHz
*32 bit
*Microsoft Windows
Version 6.1 (Build 760: Service Pack 1)
-------------------------------------------------
--Anti Malwares---
*Avira Free Antivirus
Product version 15.0.11.574
Search engine 8.03.32.14
Virus definition file 8.11.245.42
Control Center 15.00.11.574
Config Center 15.00.11.574
Luke Filewalker 15.00.11.574
Real-Time Protection 15.00.11.572
Filter 15.00.11.550
Web Protection 15.00.11.572
Scheduler 15.00.11.572
Updater 15.00.11.572
Rootkits Protection 15.00.11.550
Local Decider 15.00.11.572
*HitmanPro.Alert
Version 3.0.42 build 190
*hitmanPro 3.7.9 build 242
*Malwarebytes Anti-Malware (free)
v2.1.61022
------------------------------------------
ERROR
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048} *Virtualbox
v 4.3.28 r 100309 -------------------------------------------------------------------------
I'm using:
*Windows 7 Ultimate
*eMachine
*Pentium(R) Dual-Core CPU T4400 2.20 GHz
*32 bit
*Microsoft Windows
Version 6.1 (Build 760: Service Pack 1)
-------------------------------------------------
--Anti Malwares---
*Avira Free Antivirus
Product version 15.0.11.574
Search engine 8.03.32.14
Virus definition file 8.11.245.42
Control Center 15.00.11.574
Config Center 15.00.11.574
Luke Filewalker 15.00.11.574
Real-Time Protection 15.00.11.572
Filter 15.00.11.550
Web Protection 15.00.11.572
Scheduler 15.00.11.572
Updater 15.00.11.572
Rootkits Protection 15.00.11.550
Local Decider 15.00.11.572
*HitmanPro.Alert
Version 3.0.42 build 190
*hitmanPro 3.7.9 build 242
*Malwarebytes Anti-Malware (free)
v2.1.61022
------------------------------------------
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Failed to start
@chun, you have the classic symptoms of a corrupted certificates database. Please see the linked discussion, and the following news articles may interest you as well.
KB3004394
http://www.infoworld.com/article/285801 ... fende.html
http://www.infoworld.com/article/285911 ... 04394.html
KB3045999
http://www.infoworld.com/article/291459 ... albox.html
KB3004394
http://www.infoworld.com/article/285801 ... fende.html
http://www.infoworld.com/article/285911 ... 04394.html
KB3045999
http://www.infoworld.com/article/291459 ... albox.html