Cannot start VM after host restart, (VM Process 5)

[kiwi_canuck]

Hi Folks
I install VirtualBox, import an appliance, and start the machine successfully. I can start and stop the machine happily all day long. However, if I restart the host and start VirtualBox, I get an error when trying to start the VM. The errors look very specific but I cannot understand what they mean, so I am hoping one of you will be able to interpret.
[Note I uninstalled Eset endpoint antivirus and uninstalled HP Sureclick to rule out their interference].

VirtualBox version 6.1.16 r140961
Guest additions installed on guest = Yes
Host: Windows 10 Pro, 64 bit, 8 GB RAM, (on a domain)
Guest: Windows XP Pro, 32 bit, 2GB RAM
Logs attached and Error screenshots attached.

Thank you for your help.
Cliff

[fth0]

[Note I uninstalled Eset endpoint antivirus and uninstalled HP Sureclick to rule out their interference].

Good strategy. And what about HP ProtectTools?

[kiwi_canuck]

[Note I uninstalled Eset endpoint antivirus and uninstalled HP Sureclick to rule out their interference].

Good strategy. And what about HP ProtectTools?

Thanks fth0. There is no HP ProtectTools installed (I may have already uninstalled it). I tried uninstalling HP Client Security manager. That didn't solve the problem. Still get same error on restart.

[mpack]

We go by the last log, which still shows a zillion mentions of HP ProtectTools. Show us a log that doesn't and we may proceed from there.

[kiwi_canuck]

We go by the last log, which still shows a zillion mentions of HP ProtectTools. Show us a log that doesn't and we may proceed from there.

OK - will do!

[kiwi_canuck]

I did some research and found that HP Protect Tools Security Manager has been rebranded to Client Security Manager. I uninstalled Client Security Manager and repeated the tests. I got the same error on restarting the host. Checking the logs, I see no HP Protect Tools anymore. See attached logs.
I do not get the error on my home (non-HP) computer, so it seems to be something about this HP machine. Note I previously repeated the test on an identical HP machine and got the same error. So maybe I should be calling HP.

[kiwi_canuck]

I called HP. They suggested HP Sure Sense might cause problems, so I installed that too and tried again. Same problem. HP told me there is no other HP software installed that could interfere with VirtualBox, and suggested I contact Oracle. I have attached the latest logs and error messages. What do you suggest next? Thank you.

[BillG]

I called HP. They suggested HP Sure Sense might cause problems, so I installed that too and tried again.

I hope that is a typo and you uninstalled it!

[kiwi_canuck]

I called HP. They suggested HP Sure Sense might cause problems, so I installed that too and tried again.

I hope that is a typo and you uninstalled it!

Oops, yes typo. *uninstalled*, Thank you Bill.

[mpack]

There is something weird going on with a DLL called "edgegdi.dll", which is crashing out for some reason. From the naming I'm assuming that this is part of the MS Edge browser, but I'm using Edge right now and I don't have that DLL, at least not inside the System32 folder where the other similarly named DLLs are.

I may also be seeing errors getting the DirectSound API working - you might try disabling audio in the VM as a test.

The other thing I notice is that the graphics RAM allocation is not adequate at only 18MB. Increase to 64MB. The settings dialog should have been warning you about invalid settings - it's best not to ignore that warning.

Eject the Guest Additions ISO.

The Windows 10 build 19041.546 seems to map to an October 2020 update of Windows 10 (2004).

[kiwi_canuck]

There is something weird going on with a DLL called "edgegdi.dll", which is crashing out for some reason. From the naming I'm assuming that this is part of the MS Edge browser, but I'm using Edge right now and I don't have that DLL, at least not inside the System32 folder where the other similarly named DLLs are.

I may also be seeing errors getting the DirectSound API working - you might try disabling audio in the VM as a test.

The other thing I notice is that the graphics RAM allocation is not adequate at only 18MB. Increase to 64MB. The settings dialog should have been warning you about invalid settings - it's best not to ignore that warning.

Eject the Guest Additions ISO.

The Windows 10 build 19041.546 seems to map to an October 2020 update of Windows 10 (2004).

Thanks mpack - I will try those things on Monday and report back.

[fth0]

There is something weird going on with a DLL called "edgegdi.dll", which is crashing out for some reason.

The error in the VBoxHardening.log file is a STATUS_DLL_NOT_FOUND (0xc0000135). A Google search for "edgegdi.dll not found" shows that this problem is widespread (gdi32.dll from Windows Insider Previews unconditionally calls into edgegdi.dll, which is not available), and it could also be used as part of malware attacks.

So kiwi_canuck either used a Windows Insider Preview, or the gdi32.dll got into the regular Windows updates. VirtualBox loads gdi32.dll and cannot find edgegdi.dll.

[kiwi_canuck]

There is something weird going on with a DLL called "edgegdi.dll", which is crashing out for some reason. From the naming I'm assuming that this is part of the MS Edge browser, but I'm using Edge right now and I don't have that DLL, at least not inside the System32 folder where the other similarly named DLLs are.

I may also be seeing errors getting the DirectSound API working - you might try disabling audio in the VM as a test.

The other thing I notice is that the graphics RAM allocation is not adequate at only 18MB. Increase to 64MB. The settings dialog should have been warning you about invalid settings - it's best not to ignore that warning.

Eject the Guest Additions ISO.

The Windows 10 build 19041.546 seems to map to an October 2020 update of Windows 10 (2004).

Thanks mpack - I will try those things on Monday and report back.

I tried disabling audio on the VM, and increased Graphics RAM to 64MB, but the same problem persists.
[By the way, the setting dialog did not complain about invalid settings at 18MB, and the setting worked fine on my home computer, but I changed it to your recommended 64MB anyway.]

[kiwi_canuck]

There is something weird going on with a DLL called "edgegdi.dll", which is crashing out for some reason.

The error in the VBoxHardening.log file is a STATUS_DLL_NOT_FOUND (0xc0000135). A Google search for "edgegdi.dll not found" shows that this problem is widespread (gdi32.dll from Windows Insider Previews unconditionally calls into edgegdi.dll, which is not available), and it could also be used as part of malware attacks.

So kiwi_canuck either used a Windows Insider Preview, or the gdi32.dll got into the regular Windows updates. VirtualBox loads gdi32.dll and cannot find edgegdi.dll.

I didn't use a Windows insider preview of Windows 10. Windows 10 Pro came pre-installed on my work HP computer, and at home (where VB doesn't have the problem in question) I installed a retail version of Windows 10 Pro.

[scottgus1]

Windows 10 Pro came pre-installed on my work HP computer, and at home (where VB doesn't have the problem in question) I installed a retail version of Windows 10 Pro.

Depending on how 'work' your work is, the IT dept can put lots of stuff on a computer that can block Virtualbox via the hardening, some of which may not show up in the Hardening log. And work IT depts tend to want to control what employees run on the workstations.

Present to your boss that you need Virtualbox to do your work and the boss may get IT to clear up your PC so Virtualbox can run.