Error by starting Virtualmachines!! Please help!! (0x80004005)

[UnalO]

i have the same problem as others. i tried following the recommended steps, but it still didn't work.
Now I am using a Windows 10 Pro Version 1909
The version of VirtualBox is 6.1.16 including the extension pack.
Last time i used virtualBox was 2 days ago and i just looked if the VM's working fine or not.

I don't have an antivirus program, for example I didn't preinstall mcAffee. VT-x and VT-d are activated for me. Hypervisor is disabled.

There are no problems in USER32.dll either. I checked that in cmd with "sfc /scannow".

I looked up possible solutions here because it was recommended to look up here: Diagnosing VirtualBox Hardening Issues
In addition, I can add pictures so that you have an overview. And I am also adding the VBoxHardening file.

I need virtualBox for my school. So i am sorry that i can't solve the problem by myself, because i don't have the recommended knowledge for now.
So, I thank you very very much for helping me!

[scottgus1]

Very complete post with good listing of attempted fixes. Good job!

You have HP ProtectTools installed. That's a definite Virtualbox killer. Try to uninstall any such HP nanny software (the HP hardware drivers should be OK though). Reboot the PC, then reinstall Virtualbox using right-click Run As Administrator, even if your account as Admin privileges.

If you get another hardening error, repost a new zipped hardening log.

If you get a Virtualbox VM semi-running but see the green V turtle in the status bar, or the words Attempting fall back to NEM appear in the VM's vbox.log, let us know.

(ps I deleted your other post on this subject, since that topic probably wasn't your issue and forum rules want a problem to be in one topic not in multiples.)

[fth0]

I deleted your other post on this subject, since that topic probably wasn't your issue and forum rules want a problem to be in one topic not in multiples.

I've read that post in the other thread while it got deleted. It was about the variant with error code -101, not -104, and IMHO it was only superfluous because it was already answered in that thread a few years ago.

Peripheral question: Can a moderator restore a post they deleted?

i tried following the recommended steps

Guessing from your post in the other thread, I think you already changed the StartType of VBoxDrv.sys to SERVICE_DEMAND_START. What you probably missed, is that you may have to start the driver either manually or via an elevated task scheduler script. Both methods are described somewhere in that other thread.

PS: Good thing is that this topic made me read the other thread again (after some years), and rediscover this potential solution to the -104 error.

[UnalO]

At first I am thankful for your answear. I posted this post, before i found the thread. Yes, in the other were a solution for error -104. After i did the steps the error -101 popped up. There stand that rebooting may actually help. So after 5-10 minutes I rebooted it. Now since yesterday I can run my VM without any problems. But I tried this only with one VM. Now I am installing Win10 (32Bit) on it and lets see if this works!

[scottgus1]

Can a moderator restore a post they deleted?

To the best of my knowledge, no. Sorry if I misunderstood these posts were different subjects, I should have merged them here.

UnalO, delete the HP ProtectTools suite and check for the green turtle, see what happens.

[UnalO]

Ok, I did what you've told me. So I deleted HP Client Security Manager and reinstalled VirtualBox.
After that I reboot my PC and run VB as Administrator. Now I can run any VM like Kali or Win10.

But I couldn't see the turtle. Maybe it stood "Attempting fall back to NEM" and I didn't see it.

In Addition I am uploading the Hardening file for safety before something happen.

I am really thankful for the time that you have spent for me!

[scottgus1]

Everything looks good now! The blue V is what you want, not the turtle. No Hyper-V problems, and hardening has an exit code of 0 so no hardening problems. You are completely set!

FWIW try running Virtualbox normally, not as Administrator. Running as Admin opens your computer to greater risk of malware troubles.