[Solved] NS_ERROR_FAILURE (0x80004005) on Multiple Guests

[Haythm]

[mod note] NS_ERROR_FAILURE (0x80004005) is a general failure message when loading a VM. Subsequent lines in the error dialog will give the exact cause of the error. You do NOT have the same error just because you see the generic leader. If you don't provide a log or the supplemental error description then we can't help you. Locking this topic to prevent any more mistaken "me too" posts.

Hello,

I am having a problem with VB and keep getting this exact error for over a year now and I tried my best and could not fix it. I get the same error code for any VM I have installed once it appears. I had Kali installed today and when I got this error, now Ubuntu is not working either.

Error Message:
NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}


Setup:
Guest: Kali Linux 2018.1 (Also with Ubuntu, Debian, Windows [XP, 7, 10], Parrot OS)
Host: macOS 10.13.3 (Same problem happened with previous macOS too)
VirtualBox 5.2.8 r121009
Oracle VM VirtualBox Extension Pack 5.2.8r121009


Attempted solutions:
- Reinstalling macOS
* Making a fresh install of macOS and formatting the hard drive a couple of times
* with and without installing MalwareBytes
- Installing guest machines using ,ova files and using .iso files multiple times
- Disabling USB port, networking, sound
- Increasing the allocated storage size up to 30 GB

Attached Files:
- VBox.log
- VBoxSVC.log
- The output of running kextstat | grep -v com.apple on terminal
- The output of running VBoxManage showvminfo "VMNAME" on terminal

Thank you for your help. I really appreciate it.

[socratis]

First of all thank you for the detailed and analytical report. Kudos!

It is extremely puzzling that you are having a failure even after a clean OS re-installation. Really puzzling. Are you sure that you did a clean OSX install and you installed nothing else except VirtualBox and it failed? Because I have the following in your kexts which I vaguely remember causing trouble in the past:

144    0 0xffffff7f80f5c000 0x7000     0x7000     com.kairos.driver.DuetDisplay (1) EAA64844-C599-3560-954D-31EBFC433071 <99 5 4 3>

Can you see if unloading that makes a difference?

[Haythm]

Hi socratis,

Thank you very much for your response. I appreciate it.

After three days of testing, it seems Duet Display was the cause of the problem. I have deleted it since and so far, no issues with any VM. I don't know how I missed that but I guess I did not expect it to be the cause of the issue since rarely use it and I get the error without actively using it.

I will keep testing VB and if any issues occurs, I will update this thread. But for now, you can consider this thread as solved.

Again, thank you for your help.

[socratis]

Excellent! Thanks for the feedback. Marking as [Solved].

[vk713]

I had the exact error.

The following steps resolved the issue:
- Right click on the VM entry (for me it was in saved state)
- Click on "Discard Saved State"

[socratis]

I had the exact error.

Every single failure to load a VM results in that 0x80004005 error. The reason, is of course different every time

[Fidokomik]

Please can anybody help me? I have the same problem.

Code: Select all

A new node couldn't be inserted because one with the same name exists. (VERR_CFGM_NODE_EXISTS).


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Here is vbox log

VBox.log

(2.88 KiB) Downloaded 129 times

My Windows XP is legal copy and it did work at previous version of VirtualBox. I forgot version number, but maybe it was 4.x or 5x. I did export in *.OVA format, I did reinstall my Linux Mint (19.3), I made fresh install VB 6.1 but I cannot to start my WinXP after import.

[mpack]

You do not have an OS X host. Please post questions in an appropriate forum. Before doing that I suggest that you check if you have another VM with the same name, i.e. "WindowsXP".

[windarin]

Hi everyone.
I have the same error and I have tried one thousand things but.... no way.
I'm using Mac OS Catalina (but it happened with the previous version). In fact, after the update, I started for one second a Virtual Machine and it worked... but then it crashed again.
No matters what the virtual machine is. All of them crash.
I have tried with previous versions of Virtual Box but same result. I don't know what I changed, but it worked a few months ago...
First of all, I create a new Virtual Machine with parameters by default (Windows 10 x64 or x86, Ubuntu, Android...).
Then, I start the virtual machine (for installing the operating system), and this is the error:
The virtual machine 'Ubuntu x64' has terminated unexpectedly during startup with exit code 1 (0x1).
Código resultado:
NS_ERROR_FAILURE (0x80004005)
Componente:
MachineWrap
Interfaz:
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Attempted solutions:
- Reinstall VB (deleting the program or using the uninstaller).
- Install Extension Pack.
- Use different kind of Operating system to install.
- Change permissions in Virtual Box directory.
- Try with previous versions of VB
...

Any new idea? Thank you in advance!