virtualbox.org

I get this error whe nI try to run docker quickstar terminal

Starting "default"...
(default) Check network to re-create if needed...
(default) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed:
VBoxManage.exe: error: The virtual machine 'default' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\fende\.docker\machine\machines\default\default\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

Details: 09:16:08.277894 Audio: Device configuration of driver 'DSoundAudio' has changed
Looks like something went wrong in step ´Checking status on default´... Press any key to continue...


what could go wrong? I reinstalled docker toolbox for windows and still I get this error

We don't support Docker here, only un-modified official Virtualbox from www.virtualbox.org.

However, the hardening error is a Virtualbox thing. Zip the hardening log file mentioned in the error, and post the zip file, using the forum's Upload Attachment tab.

here it is

Thanks.

You have Avast antivirus and Malwarebytes installed. Try uninstalling both of them. Also consider letting Windows 10's built-in AV run instead of Avast. W10's AV does not block Virtualbox.

You have a lot of "[lacks WinVerifyTrust]"s. Try an 'sfc /scannow' in an admin command prompt. Also look for other security software, perhaps from your host PC's manufacturer (HP had security software that caused hardening trouble but did not show in the hardening log.)

Further, read through Diagnosing VirtualBox Hardening Issues

I disabled avast and malware bytes, reinstalled docker toolbox, tried to run VB again, I get error again...
I dont understand what else to do
I need docker to run ddev... and I am stuck now for some reason

attaching the log again after disabling avast and malwarebytes

parisrenko wrote:after disabling avast and malwarebytes

scottgus1 wrote:Try uninstalling both of them.

the hardening log wrote:f54.36c0: supR3HardenedWinFindAdversaries: 0x4
f54.36c0: ProductName: Avast Antivirus

It's still there.

sfc /scannow?

I tried everything uninstalled malware bytes too, but avast I need to keep it....I disabled it though

same error

Starting "default"...
(default) Check network to re-create if needed...
(default) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed:
VBoxManage.exe: error: The virtual machine 'default' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\fende\.docker\machine\machines\default\default\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Looks like something went wrong in step ´Checking status on default´... Press any key to continue...

If you can't take Avast off you might not be able to run Virtualbox. Also check Avast's settings, see if it can be set to stay completely out of every Virtualbox folder and process.

You could try putting a different disk in the PC, install the OS and Virtualbox, nothing else, and see if the guest will run. Then add other programs one at a time, rebooting the host and trying Virtualbox each time to see what happens. When Virtualbox fails, the offending program will be the last one installed. It has happened that a full reinstall of everything also allows everything to coexist and Virtualbox to run.

when you disable avast it stays out of eveyrthing
i reinstalled virtualbox and docker.....it worked
then i restarted computer and i get same error as before
i am attaching latest log

I understand there should be an option in the Avast software which allows the user to "disable hardware virtualisation" which the software uses by default. I suggest you try disabling that feature if you haven't already.

From the Avast site:

"Enable hardware-assisted virtualization: improves the performance of virtualization. Avast uses hardware virtualization in anti-rootkit, Sandbox, self-defense, and CyberCapture components. This option is ticked by default. If Avast detects another virtualization software on your PC, it automatically disables this option. If Avast is not able to recognize virtualization software installed on your PC, and you encounter performance or compatibility issues, we recommend temporarily unticking this option."

The above suggests, to me, that Avast can only automatically recognise "other virtualisation software" that is already on the PC before Avast is installed and, probably, not software that's installed later, which would be why totally uninstalling Avast and reinstalling after VirtualBox is working should usually work.

so I need to reinstall virtual box? Or I can keep it like it is?
i unticked that box in avast too....I did not even see settings before, thank you for that..
I use avast instead of default antivirus from wondows because I never got infected when using avast, but with default windows antovirus, and other softwares I always got virus...

I uninstalled avast completely and restarted computer, tried to run virtual box, still same error....so I dont know what is going on anymore

Even if you could install Docker, you cannot run VirtualBox on a PC which is running Docker, Sandbox, WSL 2, Hyper-V, Credential Guard, Device Guard or any other program which utilizes the hardware virtualization capabilities of the CPU. Only one application can use these capabilities. You can run Docker or VirtualBox but not both.

i switched to docker desktop and updated my windows to 2004 update so now I dont need to run virtual box anymore but straight docker....
i would never figure this out anyways, it took me hours and still no solution, i will not be coming back to VB
thank you for help and good luck with virtual box