Virtualbox on Ubunty 22 fails to start VMs with error 0X80004005

En3pY · 2024-08-05T16:58:29+00:00

There was an error rendering this rich post.

Hi everyone,

starting today, after about one week from its installation, my VirtualBox 7.0 started misbehaving. More precisely, when starting any VM (previously perfectly working) it throws an error:

NS_ERROR_FAILURE (0X80004005)

I'm currently using BEST version 7.2.0.200144, on Ubuntu 22.04.4 LTS.

The problem seemed to start today aroun 11AM GMT, when the VM I was working on suddenly crashed.

I already tried changing the policy shutting down the various components in Antimalware, but nothign appeared to work.

The only way I have to let the VM start is disabling the bdsec

systemctl stop bdsec

The VMs starts perfectly as it used to.

I tried adding exclusions of all kinds to the VirtualBoxVM binary, but with no success at any stage (forgetting that CommandLine is available on Windows only).

Did anyone else find the same problem? Any suggestion?

TIA

Find more posts tagged with

Accepted answers

Andrei_S Enterprise

Hello,

I have confirmation from the Engineering team that the issue is now resolved and has been released on the Slow Ring as well on August 20th.

If the issue still persists please reach out to our Enterprise Support Team for further investigation.

Kind Regards,

Andrei

All comments

Andrei_S Enterprise

Hello @En3pY ,

This case needs to be investigated by an Enterprise Support engineer, please reach out to us using the following form: https://www.bitdefender.com/support/contact-us.html?last_page=BusinessCategory

Kind Regards,

Andrei

19sjm88

Has anyone got an update on this?

En3pY

https://community.bitdefender.com/en/discussion/comment/342198#Comment_342198

I will be opening a ticket at BD Enterprise support in the next days, whereas it doesn't seem to be a signature related problem.

Andrei_S Enterprise

If you need any help, you can share the case in private with me and I can look over it.

Kind Regards,

Andrei

19sjm88

I have a reponse….

The issues that you have encountered with the Virtual Box VMs crashing have been identified by our Development team and a fix will be released today on Fast Ring.

It is totally your choice to decide if you want the fix now via the fast ring release or wait for the slow ring general availability. Although is unlikely, fast ring releases could introduce other issues than the one you reported. If this occurs, they will be treated with high priority.

Choosing between the slow and fast update rings allows you to better control how updates are sent to your network. For more information, refer to the Administrator’s Guide

Andrei_S Enterprise

Hello,

I have confirmation from the Engineering team that the issue is now resolved and has been released on the Slow Ring as well on August 20th.

If the issue still persists please reach out to our Enterprise Support Team for further investigation.

Kind Regards,

Andrei

En3pY

Charming, thank you for the update.

Yes I can confirm that on our side things are working up again as well after the update. Thanks a lot!