Error relaunching VirtualBox VM Process:5

Discussions related to using VirtualBox on Windows hosts.

Error relaunching VirtualBox VM Process:5

Postby Joao L Fragoso » 16. Sep 2021, 22:50

I`m getting again "Error relaunching VirtualBox VM Process:5". This sometimes works and sometimes it does not work.
I'm already killed/uninstall everything I had known as culprit, but no success in getting it working properly without a lot of fails.
Now it is falling and no way to get it back.

Any ideas how to identify the culprit of this error?
Attachments
VBoxHardening - tail.log
(100.7 KiB) Downloaded 5 times
VBoxHardening - head.log
(91.89 KiB) Downloaded 6 times
Joao L Fragoso
 
Posts: 5
Joined: 6. May 2020, 18:41
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: CentOs 6.4

Re: Error relaunching VirtualBox VM Process:5

Postby mpack » 17. Sep 2021, 10:28

Instead of fragmenting it, why didn't you just zip the log file? Hardening logs zip very well.

Anyway, you have Avast AV installed. FAQ: Diagnosing VirtualBox Hardening Issues.
mpack
Site Moderator
 
Posts: 34928
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Error relaunching VirtualBox VM Process:5

Postby Joao L Fragoso » 23. Sep 2021, 17:15

This used to work with Avast on that. I even installed Avast before VirtualBox.
But, it is really painful to have anything uninstalled every time... looks like a dedicated machine to run a VM box, almost considering to install destination OS directly on the machine.
Joao L Fragoso
 
Posts: 5
Joined: 6. May 2020, 18:41
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: CentOs 6.4

Re: Error relaunching VirtualBox VM Process:5

Postby scottgus1 » 24. Sep 2021, 00:55

Some AV pulls the same tricks that malware pulls to get into programs on the PC, and under certain circumstances, such as if the AV provider forgets to sign a dll, Hardening will catch on it.

Additionally, some "security software" like HP ProtectTools and Trusteer Rapport and their ilk can interfere in ways that does not show in the hardening log but can trigger hardening issues.

Your hardening log has exit code 1, which fits with the above sources of problems. Last paragraph of post 3 and post 4 cover places to look. If uninstalling Avast as a temporary test step and rebooting does not free up Virtualbox, look around for other security software you might have.

Windows 10's built-in Defender AV does not interfere with Virtualbox. I only use the built-in Defender now that Microsoft decided that being the number one world malware vector was not a good marketing point and decided to do something about it.

Since you're running Windows 10, try using only Defender and see if Virtualbox runs. Then if you want to put the 3rd-party AV or other progs back, do one at a time with a reboot and a Virtualbox test. You might find the causing program. Or reinstallation might engender coexistence.
scottgus1
Site Moderator
 
Posts: 13812
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Martin and 48 guests