[Solved] Cannot start Windows XP VM, exit code -1073741819

[Jack Yan]

Good evening: in 2015, I began having problems with the latest version of Virtualbox due to hardening, and the only immediate solution then was to run 4.3.12.

With the Windows 10 Creators fall update, I began experiencing three to six BSODs per day, which could be traced to driver issues. One of the drivers identified in the latest crash was VBoxDrv.sys so I decided to update Virtualbox, figuring that after three years the bug would have remedied itself.

I have to say it is still there. Here is the message, which is identical to what this user reported.

Specifically:

The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\User\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log'.

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

I have followed the steps detailed at viewtopic.php?f=25&t=82106.

On the other thread, Cylance is mentioned. I have no idea what that is, but if it’s a program we have to install, I don’t have it.

My set-up is Windows 10 Home v. 1709 build 16299.192 running v. 5.2.6 r120293 (Qt5.6.2). The PC was formerly a Windows 7 box.

I should add I have Avira anti-virus. I have attempted to run Virtualbox with Avira switched off.

I have also tried headless mode. Also there are no issues with sfc /scannow.

I could be described as a gifted novice, but am definitely not as computer-savvy that many other posters on this forum.

Any pointers would be very welcome.

[mpack]

Cylance has nothing to do with this. You seem to have Malwarebytes installed, which IMHO has a high probability of being the problem.

Might I ask why you installed Malwarebytes? ISTM that your Win10 host has perfectly adequate and trouble free AV built in.

[Jack Yan]

Update: when I read the log, I found drivers there for McAfee (which I removed in early 2016) and Malwarebytes (which I did have; now removed). The error remains the same but I have attached a fresh hardening log for your reference.

[mpack]

Other possibilities: make sure that Hyper-v is disabled (box in OptionalFeatures.exe neither checked nor shaded, reboot if you make a change).

Your hardening log shows an early abort, so this isn't graphics, it's going to be AV or something similar, e.g. a web browser filter. Or, a hacked PC.

[Jack Yan]

Hi mpack, my apologies. I had reloaded the page before I typed my second message but your first one didn’t show up.

Thank you for your advice on Cylance. There’s a long story on why Malwarebytes was installed but the short version is that Facebook had forced me to download their malware scanner in early 2016, and Malwarebytes was one of the programs I had used to make sure I cleared all remnants of their spyware.

I have removed Malwarebytes completely now but the hardening error remains.

Hyper -v is disabled.

[Jack Yan]

Hi mpack, I might have solved it.

I run MacType as Windows 10’s font smoothing isn’t up to scratch.

I added these three lines into MacType.ini:

[UnloadDll]
VirtualBox.exe
VBoxSvc.exe

The Windows XP VM has just loaded for the first time.

[mpack]

Yes, that sounds like the solution. You might want to contact the MacType people and mention the importance of signing their DLLs if they intend to behave like malware! At least they have the exclusion option.

[Jack Yan]

Thanks, mpack. I read that it was on their to-do list and may have been remedied in the latest version.