Cant Start VMs on VBOX 6.1 on Win 10

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Martis
Posts: 3
Joined: 9. Mar 2020, 14:26

Cant Start VMs on VBOX 6.1 on Win 10

Post by Martis »

Have a win10 pro workstation and randmomly machine has startd to refuse to allow any VBOX machins to start

Thows VBoxHardening error I've attached the log.

Running latest build of VBOX 6.1 have tried reinstalling the drivers, reinstall whole of VBOX as well inc in raised run as administrator

Just wondering if anyone else have come across this .

Hardening Log throws this [lacks WinVerifyTrust] on many dlls. Main e

for example
1e00.32e8: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\d3d11.dll [lacks WinVerifyTrust]
1e00.32e8: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\dcomp.dll [lacks WinVerifyTrust]
1e00.32e8: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\dxgi.dll [lacks WinVerifyTrust]
1e00.32e8: supR3HardenedDllNotificationCallback: load 00007ffd0b3c0000 LB 0x000c2000 C:\windows\system32\dxgi.dll [fFlags=0x0]
1e00.32e8: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\dxgi.dll [lacks WinVerifyTrust]
1e00.32e8: supR3HardenedDllNotificationCallback: load 00007ffd08ec0000 LB 0x0027e000 C:\windows\system32\d3d11.dll [fFlags=0x0]
1e00.32e8: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\d3d11.dll [lacks WinVerifyTrust]
1e00.32e8: supR3HardenedDllNotificationCallback: load 00007ffd09700000 LB 0x001c3000 C:\windows\system32\dcomp.dll [fFlags=0x0]
1e00.32e8: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\dcomp.dll [lacks WinVerifyTrust]
1e00.32e8: supR3HardenedDllNotificationCallback: load 00007ffcdf860000 LB 0x00056000 C:\windows\system32\dataexchange.dll [fFlags=0x0]
1e00.32e8: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\DataExchange.dll [lacks WinVerifyTrust]
1e00.32e8: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\gdi32.dll [lacks WinVerifyTrust]
1e00.32e8: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffd0f710000 'C:\windows\System32\gdi32.dll'
Attachments
errorssss.jpg
errorssss.jpg (54.31 KiB) Viewed 1118 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Cant Start VMs on VBOX 6.1 on Win 10

Post by mpack »

Zip the complete hardening log and attach the zip here.
Martis
Posts: 3
Joined: 9. Mar 2020, 14:26

Re: Cant Start VMs on VBOX 6.1 on Win 10

Post by Martis »

attached thank you
Attachments
error logs - Copy.zip
(13.37 KiB) Downloaded 11 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Cant Start VMs on VBOX 6.1 on Win 10

Post by mpack »

Thanks for the log. This seems straightforward: you have McAfee installed, with its tendrils everywhere.

FAQ: Diagnosing VirtualBox Hardening Issues.
Martis
Posts: 3
Joined: 9. Mar 2020, 14:26

Re: Cant Start VMs on VBOX 6.1 on Win 10

Post by Martis »

Thanksfor confirming it as I suspected Macafee is a nightmare, not my choice I'm afraid have to live with it

Woudl simply exclusind VBOX exe runtime from AV scan be enough or is there a definete list of other files / paths that shoudl be exculed as didnt see this in fAQ
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: Cant Start VMs on VBOX 6.1 on Win 10

Post by scottgus1 »

Exclude everything in the Virtualbox installation folder, the global settings folder (usually C:\Users\{you}\.Virtualbox), and every folder that has a guest .vbox file in it, as well as any guest virtual disk file that is not in the folder with the guest .vbox file.

You will need to try these exceptions and see if they work, we don't know if it will be successful.
Post Reply