I have a Windows 10 Enterprise edition 64 bit laptop [16299]. Trying to launch an existing image with the latest VirtualBox [5.2.6] gives the following error. I have tried reinstalling Virtual box multiple times. Any help appreciated.
VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread.
Failed to open a session for the virtual machine dev....
The virtual machine 'dev' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\su\VirtualBox VMs\d\Logs\VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e}
Thanks, I have attached the complete log file. The issue is seen when the VM is launched (I've updated the original msg). VirtualBox itself comes up fine. I am unable to open existing images and also see the same error when creating a brand new image with the latest Lubuntu 17.10.1 Desktop ISO and opening it.
Things I have already tried without success:
- ensure virtualization is enabled in BIOS
- hyper-v feature disabled
- uninstalled malwarebytes (but didn't seem to make a difference)
- reinstalled VirtualBox (using Run as Administrator) after shutdown (and waiting) several times (deleted ~/.virtualbox and extension /Program Files/Oracle completely before installing fresh)
Last edited by sony.thumm on 18. Feb 2018, 15:11, edited 1 time in total.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
I still see MalwareBytes in the log, and something called Avecto DefendPoint. A foreign thread executing in the VirtualBox process space is IMHO going to be either AV or a debugger, and I assume you're not running a debugger.
Thanks. I did uninstall Malwarebytes but it seems to have gotten re-installed again. Avecto Defendpoint is probably the culprit as you mentioned. I am seeing other threads related to this here. But since this is not a personal laptop I don't have much control over disabling/uninstalling certain software. I'll see if the corporate sys admins can do anything about this.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.