Can't open VM!

[Andrew6523]

Hello, I get the following error message: https://imgur.com/hrlP2IL I added the Hardening file as attachment, maybe it will help to diagnose?

[scottgus1]

Pictures can be posted using the forum's Attachments tab on the first day first post.

The hardening log is not complete, and doesn't have the exit code.

Try uninstalling Avast & Malwarebytes, then if a hardening or other error happens again, post the error message using the error box's Copy button if possible, or a screenshot using the Attachments tab. Also, please close all windows and error messages related to the VM before taking the log.

[Andrew6523]

Ok I have uninstalled Avast and Malwarebytes as you suggested. I have two VM's which both have the error message. I created the second one after the first one stopped working. The first one has ''Aborted'' on it, I don't know why it says that. The second one simply says ''Powered off''. I have included in attachment a picture of the error, and also the hardening log:

VM Name: Linux Mint 20.1 64 bit

The virtual machine 'Linux Mint 20.1 64 bit' has terminated unexpectedly during startup with exit code -1073740791 (0xc0000409). More details may be available in 'D:\VM's\Linux Mint 20.1 64 bit\Logs\VBoxHardening.log'.
Result Code:
E_FAIL (0X80004005)
Component:
MachineWrap
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}

[scottgus1]

I think this is a mixup of Virtualbox version files on the PC, unless you have other security software also on the PC (there's some such software that doesn't show in the log).

1. Uninstall Virtualbox and reboot.
2. Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
3. Reboot again.
4. If you have any 3rd-party security or anti-malware software, disable the living daylights out of it for a moment.
5. Reinstall Virtualbox using right-click-Run-As-Administrator.

[Andrew6523]

Those steps worked! Will have to see what happens when i turn anti virus back on but for now it's working. Thanks for your assistance

[Andrew6523]

Hello, unfortunately the error message is back again. I didn't reinstall Avast or Malwarebytes so it can't be those causing it.

[scottgus1]

Does re-doing the solution above fix the problem again?

[Andrew6523]

Hello, sorry for the late reply. Yes, redoing the steps does fix it, I have just done that now.

[scottgus1]

Interesting. Do you have to repeat the reinstall process every time you reboot the host? Or can you start and shut down the host several times, then all of a sudden the problem happens and you have to reinstall?

[Andrew6523]

I can start and shut down the VM a few times before it stops working again. Strangely the error message still appears even when it's working, so the VM doesn't load the first time I attempt it, but it does the second time.

[scottgus1]

Thanks. So the error doesn't necessarily happen when a reboot of the host happens. But you can keep trying to boot the VM when the error happens, and the VM could eventually start.

I'd start to suspect antivirus or some other security software interfering with Virtualbox or its drivers at times. Try setting an exception in the antivirus/security software(s) you have, to stay out of Virtualbox's install folder and all the VMs.

[Andrew6523]

I already uninstalled malware bytes and avast, pretty sure i don't have any other virus software, so i don't know how to get rid of this problem. Every time it comes up again i have to reinstall the program, delete the vbox.sys files, which means also restarting the pc a couple times, in order to regain access to the vm. I can't keep on doing it every couple days, takes too long.

[scottgus1]

pretty sure i don't have any other virus software,

On a Windows host you'd have built-in Windows Defender, which doesn't normally interfere.

There's something unusual happening on your PC that hasn't happened before to my recollection. At this time we have no new data to determine why it's happening. You'll have to use some imagination to figure out what on your host could be up-ending Virtualbox's installation. Registry cleaners, something that scans, you'll have to start guessing.

[Andrew6523]

Ok, thanks for your assistance.