KB3081320 (10Nov15) breaks VirtualBox 4.3.30 (WinVerifyTrust

[da4an1qu1]

After the Nov 2015 Windows 8.1 updates, I started encountering WinVerifyTrust failed on stub executable: WinVerifyTrust failed with hrc=... on '\Device\HarddiskVolume.\Program Files\Oracle\VirtualBox\VirtualBox.exe'(rc=-22919) error when trying to start any VM.

It took me an age, but I isolated the breakage to the update for KB3081320. I've got to run, but is anyone encountering this? Can anyone raise this with Microsoft? I have a corporate installation of Windows, so I think I will have to go to my IT dept to get a ticket raised.

[frank]

Please attach the VBoxHardening.log file!

[bird]

Do you have a VBoxStartup.log / VBoxHardening.log file for failure? It would help getting a clue what the problem is...
-bird

[anouvel]

Same problem here, using VirtualBox 4.3.30 and couldn't launch a single VM since last windows update.
Removing KB3081320 made the trick, thanks a lot !

Here is my VBoxStartup.log prior to removing the KB. I hope it helps..

[da4an1qu1]

Hi. Sorry about the "hit-and-run" style report earlier. I've attached the log files.

However, I didn't realise that 4.3 had moved on from .30 to .34. I tried that one, and the update does not affect it. Nor 5.0.10. So, I don't know that there is a valid problem anymore

[bird]

Thanks for the logs!

Looks like we're having trouble parsing the cryptographic signature of ncrypt.dll. I'm very much suspecting this is the timstamp parsing bug we fixed in 4.3.32. It first showed up in some new windows 10 builds a while back.

Upgrade to latest and greatest version of VirtualBox and things should work fine.

-bird

[xorbe]

I didn't realize 4.3.34 was was out, will try that first before KB3081320 removal.

[CountryLawyer]

I just upgraded to 4.3.34, but in the process of trying to fix the situation, something got royally messed up. I am desperate for any help that can be offered, as I use VirtualBox for my accounting software.

When I try to start my most recent snapshot, I'm getting the following error:

VirtualBox - Error

Failed to open a session for the virtual machine XPMode.

pci#0: Device in slot 0x30 has been removed!
vendor=0x106b device=0x003f [ver=3 pass=final]
(VERR_SSM_LOAD_CONFIG_MISMATCH).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole
{8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

[Fukao]

Hi, uninstalling KB3081320 solved 100% for me. Save me a lot of time and mainly my VMs! Thank you!

VirtualBox 4.3.20
Windows 8.1

[frank]

I just upgraded to 4.3.34, but in the process of trying to fix the situation, something got royally messed up. I am desperate for any help that can be offered, as I use VirtualBox for my accounting software.

When I try to start my most recent snapshot, I'm getting the following error:

VirtualBox - Error

Failed to open a session for the virtual machine XPMode.

pci#0: Device in slot 0x30 has been removed!
vendor=0x106b device=0x003f [ver=3 pass=final]
(VERR_SSM_LOAD_CONFIG_MISMATCH).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole
{8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

Sounds to me like your VM has USB support and now (after upgrading VBox) you did not upgrade the Extension Pack and therefore USB is not available anymore. So when you load the saved state, VBox complains that it cannot initialize the device anymore.

[CountryLawyer]

OK... How do I fix that? If it's not obvious yet, I am not very computer savvy.

[frank]

Make sure to install the Extension Pack. Download the 4.3.34 Extension Pack from here and in the VirtualBox VM selector window open File / Preferences / Extension Packs and make sure the 4.3.34 ExtPack is installed. That's also all described in the user manual.

[Groot90]

I had the same problem today.
After regular Windows 8.1 update, my Virtual Box 4.3.22 stopped working. The error message while trying to start any guest VM was something like "WinVerifyTrust failed........Please reinstall VirtualBox".

Thanks to da4an1qu1's post, I have deleted Windows Update KB3081320, restarted, and VirtualBox is back to normal.

Thank you da4an1qu1!

[CountryLawyer]

I just installed the Extension Pack and rebooted and still receiving identical error message.

[frank]

I just installed the Extension Pack and rebooted and still receiving identical error message.

For the record, this was solved in another topic.