Result Code: E_FAIL (0x80004005)

Discussions related to using VirtualBox on Windows hosts.
Post Reply
rattle9
Posts: 1
Joined: 15. Nov 2018, 11:31

Result Code: E_FAIL (0x80004005)

Post by rattle9 »

Hi,

I was using VirtualBox earlier and the Virtual CentOS was working fine.

Recently, I updated my Windows 8 to Windows 10 to run Docker with Hyperversion on windows. For some reason I had to uninstall Docker because I was giving some problems and I wanted to move back to VirtualBox. But when I try to run it, it wouldn't start. I also disabled Hyper-v but no luck.

I am attaching my VBoxHardening.log here.

Your help will be appreciated.

Thanks
Shubh
Attachments
VBoxHardening.zip
(19.62 KiB) Downloaded 7 times
andyp73
Volunteer
Posts: 1631
Joined: 25. May 2010, 23:48
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation

Re: Result Code: E_FAIL (0x80004005)

Post by andyp73 »

VBoxHardening.log wrote:
ef4.734: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 4395 ms, the end);
f28.f24: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 5105 ms, the end);
It appears not to be a hardening issue! There is likely another cause which will show up in the VBox.log file. Can you post that one as well.

-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Post Reply