Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Discussions related to using VirtualBox on Windows hosts.
Post Reply
thomaszhou
Posts: 6
Joined: 18. Sep 2021, 11:40

Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Post by thomaszhou »

when i upgrade my virtualbox to 6.1.26, all my virtualbox vm cannot start and retrun fail: E_FAIL (0x80004005).

Follow this harden issue diagnose guide, it's still not work.

Can anyone help?
Attachments
VBoxHardening.log
VboxHardening log
(33.16 KiB) Downloaded 30 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Post by mpack »

You have superfluous third party AV installed, in this case Symantec. So it could be that.

FAQ: Diagnosing VirtualBox Hardening Issues.
thomaszhou
Posts: 6
Joined: 18. Sep 2021, 11:40

Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Post by thomaszhou »

yeah,symantec is the reason,after uninstall it, the vm can start, thanks
thomaszhou
Posts: 6
Joined: 18. Sep 2021, 11:40

Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Post by thomaszhou »

but for IT compliance, we need to install AV Softwares, how to resolve the conflict issue?
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Post by scottgus1 »

thomaszhou wrote:symantec is the reason,after uninstall it, the vm can start, thanks
Great! Glad you're up and running.
thomaszhou wrote:IT compliance
Does this mean that you are in a workplace with an IT department? You can convince your boss that Virtualbox is important for your work. Then the boss will tell IT to make AV cooperate with Virtualbox.

They may have to set exceptions in AV to not scan any Virtualbox folders or files, nor any VMs. Each VM that accesses the internet would get its own AV.
thomaszhou
Posts: 6
Joined: 18. Sep 2021, 11:40

Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Post by thomaszhou »

After I had changed to another AV software, one or two virtualbox vm can run same time,but if continue to start more virtualbox vm, it will raise E_FAIL error, the vboxhardening log is not same with previous error.

Anyone knows?
Attachments
VBoxHardening.log
(28.78 KiB) Downloaded 9 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Post by mpack »

thomaszhou wrote:but for IT compliance, we need to install AV Softwares
Windows 10 has AV software built in (Windows Defender + firewalls). You should ask why "IT compliance" requires you to compromise the PC by installing unnecessary third party kernel level software.

This is not 1995 - Windows has its own AV these days, and with access to the OS source code it does a far better job with far fewer performance impacts than anything a third party app could do.
thomaszhou wrote:After I had changed to another AV software, one or two virtualbox vm can run same time,but if continue to start more virtualbox vm, it will raise E_FAIL error, the vboxhardening log is not same with previous error.
On the contrary, the latest log shows that Symantec is still present:

Code: Select all

2ad8.4090:     ProductName:     Symantec CMC Firewall
2ad8.4090:     ProductVersion:  14.2.3329.1000
2ad8.4090:     FileVersion:     14.2.3329.1000
2ad8.4090:     FileDescription: Symantec CMC Firewall sysfer
Third party AV is basically optional malware: the user decides to install this stuff, it hits the performance of the PC, and then it can sometimes be a nightmare to be rid of it.
thomaszhou
Posts: 6
Joined: 18. Sep 2021, 11:40

Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Post by thomaszhou »

after delete sysfer.dll(symantec cmc firewall), everything is ok, all of the virtualbox vms can run together, thanks
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Post by mpack »

Hmm. Make sure it doesn't come back after a boot, or just a period of time. AV/malware writers have tricks to fight back against would-be deletion.
thomaszhou
Posts: 6
Joined: 18. Sep 2021, 11:40

Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)

Post by thomaszhou »

yes, I had reboot several times, it's work fine, thanks @mpack
Post Reply