VMs not starting: Error -104 in supR3HardenedWinReSpawn! (enmWhat=5)

[plover]

I have last used my VirtualBox machines about a month ago, and today none of them would start. This is the error I found in VBoxHardening.log:

174c.738: Error -104 in supR3HardenedWinReSpawn! (enmWhat=5)
174c.738: Error relaunching VirtualBox VM process: 5

I have read the Diagnosing VirtualBox Hardening Issues, but I cannot find the solution.

I have uninstalled VirtualBox, rebooted, installed the latest version with Run as administrator, and it didn't help.

All the guests, Linux and Windows, don't start with this same error.

The system is Windows 10 Pro version 1903 build 18362.1082. I'm not using any additional antimalware software.

The log file and error message screenshots are attached.

So, what can be done to start my virtual machines?

[scottgus1]

Your hardening log's exit code is 1. There is a topic in the hardening tutorial on that exit code. Regrettably, the hardening log cannot always tell what is the source of the problem You will have to review your installed programs for anything that might match the problem program classes the tutorial points out.

[plover]

But I did review all my installed programs!

I see nothing about malware, or virtualization (except for VirtualBox and BlueStacks), or sandboxing, or anything of the kind there.

The VMs did run with BlueStacks installed, and I didn't upgrade BlueStacks since they ran last time.

How can I find the offending application?

[plover]

... or else, how can I disable VirtualBox hardening?

[scottgus1]

Disabling hardening is not available unless you build Virtualbox from the source code (I don't know how to do that.)

I don't have any ideas myself of the offending program on your computer either. Malware & virtualization are not the only offending program classes the tutorial mentions.

If I were in your place I would put a second disk in my computer in place of the one you boot from now. Reinstall the OS, then Virtualbox, and confirm Virtualbox runs. Then add one 3rd-party program at a time, reboot the PC, and try Virtualbox. Rinse and repeat. The offending program will eventually show itself, if the problem doesn't get fixed by reinstallation of everything, which does sometimes fix the problem.

[plover]

Thank you very much for your replies, scottgus1!

Switching HDDs for a notebook is not at all an easy challenge.

I think I'll try some other virtualization options then.

[scottgus1]

Sorry we couldn't help further! Hope you find a solution.