Opened 8 years ago
Last modified 7 years ago
#16878 new defect
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH error on Windows 10
Reported by: | arshad01 | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.1.22 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
Hello
I keep getting the above mentioned error when I start a guest. I remove and reinstall VirtualBox and the error goes away, but after a few days it comes back again (usually after a restart of my PC). I am attaching the screen shot of error box and VBoxHardening log. A shorter error message is below:
Failed to open a session for the virtual machine Ubuntu-16.04. The virtual machine 'Ubuntu-16.04' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\arshad.khan\VirtualBox VMs\Ubuntu-16.04\Logs\VBoxHardening.log'. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Any help is greatly appreciated.
Thanks Arshad
Attachments (3)
Change History (8)
by , 8 years ago
Attachment: | vbox_err.png added |
---|
by , 8 years ago
Attachment: | VBoxHardening.log added |
---|
follow-up: 2 comment:1 by , 8 years ago
Please could you install VBox 5.1.24 and add the VBoxHardening.log file of a VM session with 5.1.24? This will print more information (5.1.24 has a relevant change) which will help to find the problem.
comment:2 by , 8 years ago
Replying to frank:
(5.1.24 has a relevant change) which will help to find the problem.
Frank, could you please state what change is that, and how it helps identify the problem easier? That's for future reference, for the "next" VBoxHardening.log that we may bump into...
comment:3 by , 8 years ago
It's in r67950. We need to know the output of that SUP_DPRINTF() statement. So far the reason for this problem is not clear, thus the additional logging.
Screenshot of error