E_FAIL (0x80004005)
-
- Posts: 16
- Joined: 30. Sep 2021, 22:02
E_FAIL (0x80004005)
I am having the same issue with all my VMs on the latest Version 6.1.26 r145957. The VMs are a combnation of Windows and Linux. The errors I keep getting is:
Launched VM: 79353904 pid: 1188 (0x4a4) frontend: GUI/Qt name: WinVM10
00:00:43.425595 Watcher ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The virtual machine 'WinVM10' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)}, preserve=false aResultDetail=0
I uninstalled and re-installed VBox 10 times on my Windows 10 machine and I still get this error.
Launched VM: 79353904 pid: 1188 (0x4a4) frontend: GUI/Qt name: WinVM10
00:00:43.425595 Watcher ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The virtual machine 'WinVM10' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)}, preserve=false aResultDetail=0
I uninstalled and re-installed VBox 10 times on my Windows 10 machine and I still get this error.
-
- Posts: 16
- Joined: 30. Sep 2021, 22:02
Re: E_FAIL (0x80004005)
Here are the VM logs.
- Attachments
-
- WinVM10-2021-09-20-15-33-37_part2.log
- (71.06 KiB) Downloaded 7 times
-
- WinVM10-2021-09-20-15-33-37_part1.log
- (118.16 KiB) Downloaded 8 times
-
- Posts: 16
- Joined: 30. Sep 2021, 22:02
Re: E_FAIL (0x80004005)
Here's a screenshot of the error as well.
- Attachments
-
- Capture.JPG (32.71 KiB) Viewed 5726 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: E_FAIL (0x80004005)
Let's start by fixing that, then we can see what's next.00:00:05.837309 VirtualBox VM 6.1.18 r142142 win.amd64 (Jan 7 2021 15:32:19) release log
...
00:00:05.934144 Oracle VM VirtualBox Extension Pack (Version: 6.1.26 r145957; VRDE Module: VBoxVRDP)
I would also reduce the VM to 2 cores. VirtualBox is a host app, so leaving the host with only one core will not improve performance.
p.s. In future please zip logs, don't break them into pieces.
-
- Posts: 16
- Joined: 30. Sep 2021, 22:02
Re: E_FAIL (0x80004005)
I am already on the latest version of VBox.
- Attachments
-
- Capture.JPG (27.8 KiB) Viewed 5647 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: E_FAIL (0x80004005)
If it's assertion vs log, I go with the log. If things have changed then a new log is needed. Zipped this time please.
-
- Posts: 16
- Joined: 30. Sep 2021, 22:02
Re: E_FAIL (0x80004005)
vbox.log attached below
- Attachments
-
- WinVM10.zip
- (36.04 KiB) Downloaded 7 times
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: E_FAIL (0x80004005)
The WinVM10-2021-09-20-15-33-37.log file is from September 20th, and most probably not from your current attempt to start the VM. The background reason is that the error occurs before a new VBox.log file is created. Please start the VM from inside a command prompt with the following commands:
When the error dialog occurs, close it with the OK button. Then provide any messages you get inside the command prompt window, and a zip file containing the file C:\Users\<username>\.VirtualBox\VBoxSVC.log and the VBoxHardening.log file.
Code: Select all
cd "C:\Program Files\Oracle\VirtualBox"
VirtualBoxVM --startvm "WinVM10"
-
- Posts: 16
- Joined: 30. Sep 2021, 22:02
Re: E_FAIL (0x80004005)
No entry when I run from cmd. See attachment below.
- Attachments
-
- Capture2.JPG (41.7 KiB) Viewed 5630 times
-
- Posts: 16
- Joined: 30. Sep 2021, 22:02
Re: E_FAIL (0x80004005)
Please see the VBoxSVC.log files
- Attachments
-
- VBoxSVC_2.log
- (6.41 KiB) Downloaded 9 times
-
- VBoxSVC_1.log
- (6.76 KiB) Downloaded 8 times
-
- VBoxSVC.log
- (5.92 KiB) Downloaded 8 times
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: E_FAIL (0x80004005)
Unfortunately, the VBoxSVC.log file(s) do not show unexpected additional error information, except perhaps regarding USB devices. You could try to disconnect or disable as many USB devices on the host as you can, to see if the error is somehow caused by an USB device.
Other than that, check the file date/time of the VBoxHardening.log file (next to the VBox.log files). If it is from your latest attempt, please provide a zip file containing it.
Additionally, try if using VBoxManage startvm "WinVM10" instead of VirtualBoxVM --startvm "WinVM10" gives other responses.
Other than that, check the file date/time of the VBoxHardening.log file (next to the VBox.log files). If it is from your latest attempt, please provide a zip file containing it.
Additionally, try if using VBoxManage startvm "WinVM10" instead of VirtualBoxVM --startvm "WinVM10" gives other responses.
-
- Posts: 16
- Joined: 30. Sep 2021, 22:02
Re: E_FAIL (0x80004005)
I did all of the above and still nothing starts. How can I resolve this issue?
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: E_FAIL (0x80004005)
1. Please repeat fth0's request about a zipped VboxSVC and Hardening logs. Always provide new logs after trying a suggestion that apparently did not work. (BTW no hardening log was posted. Does that mean there was no hardening log, or did you forget to post it?)
2. Also, consider that some hardening errors do not show up in the hardening log. Exit code 0xc0000005 is discussed in Diagnosing VirtualBox Hardening Issues, where it is diagnosed as:
3. Also consider, as a test, uninstalling (not just disabling) every bit of security software your computer has on it: 3rd-party antivirus, web-safe browsing, safe-banking, malware-scanning, etc. HP ProtectTools, Trusteer Rapport, etc. Only allow Windows Defender, 10's built-in AV to run. Reboot the host for a fresh start then try Virtualbox. Please report what happens.
So note there are three points to consider. Please act on each point.
2. Also, consider that some hardening errors do not show up in the hardening log. Exit code 0xc0000005 is discussed in Diagnosing VirtualBox Hardening Issues, where it is diagnosed as:
Suggestions are given in the Hardening tutorial in post "Error Symptom 2: Error code 0xC0000005".a bad DLL got unloaded, but some other DLL is still trying to use it.
3. Also consider, as a test, uninstalling (not just disabling) every bit of security software your computer has on it: 3rd-party antivirus, web-safe browsing, safe-banking, malware-scanning, etc. HP ProtectTools, Trusteer Rapport, etc. Only allow Windows Defender, 10's built-in AV to run. Reboot the host for a fresh start then try Virtualbox. Please report what happens.
So note there are three points to consider. Please act on each point.
-
- Posts: 16
- Joined: 30. Sep 2021, 22:02
Re: E_FAIL (0x80004005)
1) I don't have any hardening files at all on my system. I am attaching the VBoxSVC.log zipped.
2) No hardening log exists.
3) Yes I did that. I have reinstalled VBox multiple times, I had the IT team add VBox to the my Cyclance whitelist even though it was never being blocked by the AntiVirus software. Also I've been using VBox with AV for the last two years but then all of a sudden things stopped working. It sounds like a hardware/firmware issue that's not compatible anymore.
2) No hardening log exists.
3) Yes I did that. I have reinstalled VBox multiple times, I had the IT team add VBox to the my Cyclance whitelist even though it was never being blocked by the AntiVirus software. Also I've been using VBox with AV for the last two years but then all of a sudden things stopped working. It sounds like a hardware/firmware issue that's not compatible anymore.
- Attachments
-
- VBoxSVC.zip
- (22.57 KiB) Downloaded 6 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: E_FAIL (0x80004005)
Ah-Hah! This may be it!!Wassim Kayrala wrote:my Cyclance whitelist
Cylance pushed an update recently that killed Virtualbox. Which means:
scottgus1 wrote:3. uninstalling (not just disabling) every bit of security software your computer has on it:
No you didn't. A whitelist is not an uninstall, it's a disable. Note the the instructions:Wassim Kayrala wrote:3) Yes I did that.
Following instructions is critical in troubleshooting software problems.scottgus1 wrote:uninstalling (not just disabling)
Since you have corporate IT overlords, you must convince your boss that Virtualbox is important for your work. Then your boss can have IT get Virtualbox working on your computer. Your job's IT's security is too strict for Virtualbox to run. I believe there is nothing we can do to get your Virtualbox to work on your computer in the present situation.