Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)
-
- Posts: 6
- Joined: 18. Sep 2021, 11:40
Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)
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?
Follow this harden issue diagnose guide, it's still not work.
Can anyone help?
- Attachments
-
- VBoxHardening.log
- VboxHardening log
- (33.16 KiB) Downloaded 33 times
-
- Site Moderator
- Posts: 39134
- 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)
You have superfluous third party AV installed, in this case Symantec. So it could be that.
FAQ: Diagnosing VirtualBox Hardening Issues.
FAQ: Diagnosing VirtualBox Hardening Issues.
-
- Posts: 6
- Joined: 18. Sep 2021, 11:40
Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)
yeah,symantec is the reason,after uninstall it, the vm can start, thanks
-
- Posts: 6
- Joined: 18. Sep 2021, 11:40
Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)
but for IT compliance, we need to install AV Softwares, how to resolve the conflict issue?
-
- Site Moderator
- Posts: 20945
- 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)
Great! Glad you're up and running.thomaszhou wrote:symantec is the reason,after uninstall it, the vm can start, thanks
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.thomaszhou wrote:IT compliance
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.
-
- Posts: 6
- Joined: 18. Sep 2021, 11:40
Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)
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?
Anyone knows?
- Attachments
-
- VBoxHardening.log
- (28.78 KiB) Downloaded 15 times
-
- Site Moderator
- Posts: 39134
- 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)
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.thomaszhou wrote:but for IT compliance, we need to install AV Softwares
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.
On the contrary, the latest log shows that Symantec is still present: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.
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
-
- Posts: 6
- Joined: 18. Sep 2021, 11:40
Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)
after delete sysfer.dll(symantec cmc firewall), everything is ok, all of the virtualbox vms can run together, thanks
-
- Site Moderator
- Posts: 39134
- 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)
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.
-
- Posts: 6
- Joined: 18. Sep 2021, 11:40
Re: Windows10 21H1 virutalbox 6.1.26 start vm fail: E_FAIL (0x80004005)
yes, I had reboot several times, it's work fine, thanks @mpack