E_FAIL error again (0x80004005)?

Question

virtual box

Good day to all!
Recently I ran into a problem starting a VirtualBox virtual machine running Win 10, any machine refuses to start on standard startup and gives an error:

Error code:

E_FAIL (0x80004005)
Компонент: 
MachineWrap
Интерфейс: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

At the same time, running in the background works flawlessly.
Similar questions have already been met on the Toaster, but not one of the tips given there has helped.
What I did:
1. Installed old versions of VB - same story
2. Installed VB drivers from drivers folder - nothing changed.
3. Deleted the .virtualbox settings folder
4. Enabled/disabled virtualization in the motherboard settings - zero effect (virtualization support disappears in the virtual machine manager).
5. Renamed the virtual hard disk.
6. Renamed the virtual machine file on the advice from the Internet xml-prev to xml - it's useless
7. Enabled- disabled Hyper-X components in Windows components - only an error about the inability to use VT / AX was added (it is treated by disabling the Windows hypervisor component back) outdated as 5 years judging by the dates of publication. A big topic with a discussion of the hypervisor conflict, but I successfully solved this problem.
9. On YouTube, I came across a video that after the new year, due to another nightmare in the form of a crooked update of Windows (or maybe not a crooked one, but exactly as planned), VMware virtual machines also flew and that some setting for protecting local records and protection is to blame virtual machines from scary hackers. That you need to disable this miracle in Win Defender by adding entries to the registry. I did everything as advised - but the miracle did not happen.
What to do next, xs ... The last attempt to contact the Toaster for help, and then just probably relax and hope that Oracle or Microsoft knows about the problem and will fix everything in the next update.
Maybe someone encountered the same problem and successfully solved it?
After a lot of poking around the forums and the settings of the virtualbox itself, I came to the conclusion that some Windows updates are more likely to blame, which broke the system settings and led to this scenario. In favor of this version, he says that the virtualbox was not updated to version 5.2 and worked quietly without any complaints, and after the New Year this error suddenly appeared and this is not treated by any update or downgrade of virtualbox. The downgrade was also done with the complete removal of the new version of virtualbox through the revouninstaller, followed by cleaning the registry branches, deleting the remaining settings files and rebooting.
For those who are interested, I attach the logs:

Vbox.log
VBoxHardening.log
Thank you for your attention.

Answer 1

The problem was solved by installing absolutely all the latest Win 10 updates, including optional ones . It turns out that my Win was not yet updated to version 1909 (I do not follow the versions of updates, the system works well). After updating Win, virtualbox still doesn't work properly. Next, we put a cumulative update for .Net, reboot and virtualbox does not work again. We go again to the update center, look for updates and see that there is an optional cumulative update available, install it (it takes sooooo long to install), reboot again and voila! Virtualbox works as it should. So if you have a similar problem, try installing all the latest Windows updates, including optional ones, maybe this will help.

Answer 2

I also had this error, and all the virtual machines stopped starting at once. In Google I found the instructions about which the author wrote, nothing helped. Windows updates (I have win 10) did not help either. After that, I remembered that the day before that I had installed VipNet CSP, removed it, after which everything worked again. Maybe someone will come in handy.

Answer 3

some protection setting is to blame

Windows has nothing to do with it: you have Kaspersky.

Answer 4

First link from Google:
How to fix E_FAIL 0x80004005 error in VirtualBox

Answer 5

Found what's wrong. It is necessary to disable in win10: Windows Sandbox (enable or disable Windows components in) Control Panel\All Control Panel Items\Programs and Features)
So if it helps, don't forget to thank you .. :)

Answer 6

Reinstalling VB with the parameter as administrator in CMD/Powershell helped:
.\VirtualBox-6.1.26-145957-Win.exe -msiparams NETWORKTYPE=NDIS5
Taken from here: https://stackoverflow.com/a/33733486/5847153