[Fixed] The VM session was aborted.(0x80004005)

[Bernard_P]

---

[ModEdit; The problem with "Restoring from Saved State crashes VirtualBox" has been fixed with the release of 5.2.12.]

---

Host: Debian Jessie 64
Guest: Windows XP
Hello,
I am having the following problem for one of my XP guest machines:
When I save the state of the virtual machine, at the next reboot I get the following error message:
The VM session was aborted.
Error Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

I have nothing in the log files that can help me solve this problem.

Thanks for your help.

[callipso]

Hi,

Did you find any solution to this issue. I'm having exactly the same problem.
Host: Debian Stretch 64
Guest: Ubuntu 18.04
Virtualbox version: tested both 5.2 & 5.1
Kernel: Linux extreme 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1 (2018-04-29) x86_64 GNU/Linux

I have also tried reinstall virtualbox and recompile all kernel vbox modules and the issue persists. It was working initially and it seems that the latest Virtualbox upgrade did not do any good.

It is possible to start virtual machine after discarding saved state. This error only occurs when trying to resume virtualmachine from a running state.

[socratis]

Can you please both try the latest 5.2.x test builds? There was an issue with saved states that sounds awfully close to what you're describing.

Since these are test builds, there are not in the repository, you'll have to download the generic 5.2.x Linux package. See the test builds page for the instructions.

[abulhol]

I have the same problem with version 5.2.10. I cannot restore live snapshots, and if I boot normally and take a new snapshot, it is also not possible to start this snapshot afterwards.
In addition, I have found that the same problem exists in version 5.1.36.
Host OS Ubuntu 14.04 and 18.04, guest OS Windows and Android x86.

[socratis]

Can you please both try the latest 5.2.x test builds?

I have the same problem with version 5.2.10.

Did you even read the messages before yours? Or was this a "me too" attempt?

[blackthorn]

WIth an Ubuntu 16.04 Host and an Ubuntu 14.04 guest, running the latest (as of May 3rd) test build, Version 5.2.11 r122401 (Qt5.6.1) has fixed this issue for me.

[socratis]

Thanks for confirming 'blackthorn'!

[doleron]

Same here:

Host: Ubuntu Server 16.04
Guest: Ubuntu Server 16.04
Virtualbox version: 5.2.10 r122088

The VM is runing in headless mode. Other VM running in the same server (Windows 2012 R2) but this last one doesn't abort.

[socratis]

I'm sorry, but "this last one doesn't abort" means that it's working in your case with the test builds?

[yjcb]

Hello everybody,

If this helps I can confirm I have the same problem with ArchLinux. When trying to restore a snapshot it did not work. So, I follow the instructions sent by socratis and installed the latest testbuild and that fixed the problem.

[imrazor]

I was also having this problem and can confirm that build 5.2.11 r122553 resolved the issue I was having resuming from a suspended state. Like the OP, I had previously been getting error 0x80004005 when trying to resume a suspended VM session.

Thanks for the quick fix.

EDIT: After reviewing this thread, there seems to be a common thread. Every one of us is running Debian or Ubuntu. I'm on Debian Stretch x64 if that helps.

[socratis]

Thanks @doleron, @yjcb and @lmrazor for confirming.

@lmrazor, no it's not a Debian or Ubuntu problem only, it was a more generalized problem. You are simply all in the "Linux Hosts" area...

[doleron]

I'm sorry, but "this last one doesn't abort" means that it's working in your case with the test builds?

"this last one"refers to the Windows 2012 VM.

[doleron]

I just confirmed that the release 5.2.12 (122591) solved the issue for me.

[Tacuabe]

Hello everybody!

I'm having the same problem using V5.2.12 in a Dell XPS13-9350 running Lubuntu 18.04 as host. I have two Windows 7 VMs that refuse to start and show the same error.
Now, AFAIK 0x80004005 is a Windows error with a known procedure to correct, IF you have access to the VM, which I do not. Here is what must be done to get rid of the infamous thing:

How to correct Windows 0x80004005 error

1 - Right button click on "My Computer" at the Start Menu
2 - Select "Properties" and the "System Restore" tab
3 - "Turn Off System Restore on All Drives" and then "OK"
4 - Accept with "Yes" and again "Ok"
5 - Reboot
6 - Repeat steps 1 and 2
7 - Now remove check from "System Restore Off"
8 - "Apply" and "Ok"

Error 0x80004005 disappears and "System Restore" works again.

I've read in another similar thread as this one, that VMs can be started from the CLI. Didn't find that in the Help. Can anyone explain how to?

I'm hoping that if I can start my VMs from the CLI maybe using the above procedure may recover their status and could be started later with the Manager.

Thanks in advance for any help provided.

Hector