unable to start vm: VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH

[rosch]

I'm getting the following error again when trying to restore a saved machine. Same machine worked fine a couple of days ago. No update or reinstall of VirtualBox in the meantime.

supHardenedWinVerifyProcess failed with
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH: (rc=-5618)

Please try reinstalling VirtualBox.

where: supR3HardNtChildPurify what: 5
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH: (rc=-5618)- Process Verification 
Failure: Executable file name and process image name does not match up.

After reinstalling VirtualBox by choosing "repair" when running the executable, and rebooting Windows, I was able to start the vm guest just fine from the saved state.

VirtualBox: 5.2.3r119650

Host: Windows 10 64bits

[rosch]

Exactly the same issue again with VirtualBox 5.2.5r120042.

After reinstalling VirtualBox by choosing "repair" when running the executable, and rebooting Windows, I was able to start the vm guest just fine from the saved state.

[rosch]

Was wrong, repairing vb and rebooting Windows didn't help this time.

There is no new test build at this time, so no luck.

[Siegmund]

I installed latest Windows 10 updates yesterday, and can confirm that VirtualBox 5.2.4 throws this error, when both old and newly-created virtual machines are started, even after I attempt to repair the installation.

[Socratis]

Do not simply try to repair the installation. Uninstall it completely and then re-install it. Your VMs and your settings are not going to be harmed.

Oh, and if you want to use the latest version for your host/guests, you should also consider doing the same for VirtualBox. If that doesn't work, you should try the latest test builds.

[rosch]

Thanks for your advice.

Version 5.2.5r120042 works again, but don't ask me why, I didn't have to reinstall it.

[rosch]

Same issue once again. Started up without a problem after installing the latest test build (5.2.7r120528).

[rosch]

Same issue once again. Started up without a problem after installing the latest test build (5.2.13r123115).

[Socratis]

• Uninstall VirtualBox. Restart your computer.
• Uninstall any/all 3rd party antivirus. Restart your computer.
• Search for any Virtual*, VBox* and VM* files. And their parent directories. Delete them.
• Do the same for the registry. I use CCleaner. Beware, it's bundleware and set to run at startup, easily avoidable both of them.
• Re-install VirtualBox by right-clicking and selecting "Run As Administrator", even if you are the Administrator.

[vlapr]

Hardening error

[vlapr]

Error supHardenedWinVerifyProcess happens time to time on Win 10. Reinstalation of the VirtualBox help, but it is boring.

Version 5.2.20. It happend also at few previous versions.

See attached file VBoxHardening.log

There is a message "2e0.9fc: Process image name does not match the exectuable we found: \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VirtualBox.exe vs \Device\HarddiskVolume2\PROGRA~1\Oracle\VIRTUA~1\VIRTUA~1.EXE." in the file.

It seems that there is an error with matching LONG and SHORT filename.

Thanks for bugfix !!!

[Emadin]

log for 6.0.2

[Emadin]

This also happens in VirtualBox 6.0.2 on Windows 10 1709. With FSecure. Right now this happens for me with every windows restart.

supHardenedWinVerifyProcess failed with VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH:(rc=-5618) Please try reinstalling VirtaulBox

Earlier on 5.2.24 such problem would happen only when launching VM in detached/headless mode. When running in normal mode it would usually start OK.

[rosch]

Also happens on 6.0.3 r128231

Starting to get really annoying. The ticket is older than a year now..

[SylwBar]

Hi. I observe this problem frequently since 6.0.0 release. I must restart PC and try to start VB again - usually helps but it is very annoying.

Since the problem could be related to LONG/SHORT names matching I installed VirtBox on c:\VirtBox\ folder and after one week of testing it looks like good workaround for the problem. My host PC is Windows 10 (1607 build)

[rosch]

This is very annoying and simply keeps going on since at least December 2017..

[Socratis]

@rossch
Here's the thing. It happens with some systems, very few of them. And if you re-install your host, it won't happen, I guarantee you that. So, the question/burden lies mostly with the affected setups to find a common denominator.

What do you have installed that's causing this, because as sure as I can see my 3 Win hosts, it doesn't happen here. Plus not a whole of mentions (if any at all actually) in the forums.

It can't be addressed, if it can't be reproduced...

[rosch]

"re-install" your host, you mean reinstall VirtualBox? Well that's what I do. That's what I keep doing for about the last 15 months now.

I'm downloading and installing the latest test version (https://www.virtualbox.org/wiki/Testbuilds) every time I encounter the VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH error. Currently I'm on version 6.0.5 r129380.

Just now, I only restarted Windows 10, which did the trick.

I'll try and add more details of my findings later-on.

[Socratis]

Replying to rossch:

"re-install" your host, you mean reinstall VirtualBox?

No, I actually, litereally, mean your host. Your Windows 10 host. There's something wrong with your that one, methinks. Tough to pinpoint what exactly...