Page 1 of 1

WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 15. Nov 2015, 17:00
by zlpan
I just finished the new Windows 8.1 update. After my laptop restarted, I could not start my guests on virtualbox. I have ubuntu guest on windows host. I have seen people have the same issue, but I'm not sure if we share the same reason.

Below is the error message:

WinVerifyTrust failed on stub executable: WinVerifyTrust failed with hrc = Unknown Status 0x8009200D on
'\Device\HarddiskVolume7\Ubuntu\VirtualBox.exe' (rc=-22919)
Please try reinstalling VirtualBox.


My VB version is 4.3.22.
Thanks for help.
VBoxStartup.zip
VB startup log
(10.08 KiB) Downloaded 556 times

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 15. Nov 2015, 17:19
by loukingjr
See if removing the windows KB3081320 update fixes it. You may want to update to VB 4.3.34 or 5.0.10 btw.

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 15. Nov 2015, 17:35
by zlpan
Problem fixed. Thank you sir. Btw, if I'm going to update my VB to 4.3.34 or 5.0.10, do I need to worry about the content of my VB getting corrupted?

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 15. Nov 2015, 17:40
by loukingjr
If you update to 5.0.10 you should probably uninstall VB first just to be safe. You can install 4.3.34 in place. Don't forget the matching extension pack and update the guest additions for your guests.

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 15. Nov 2015, 17:43
by zlpan
Gotcha, thanks.

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 15. Nov 2015, 17:46
by loukingjr
most welcome. In either case, your guests will be unharmed.

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 18. Nov 2015, 03:15
by Naresh
Could you please tell me that how it's fixed.

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 18. Nov 2015, 20:29
by zlpan
Go to Control Panel -> System and Security -> Windows Update -> Installed Updates (bottom left corner) -> Search for KB3081320 -> Right Click -> Uninstall -> Reboot.

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 18. Nov 2015, 22:06
by hansdb
Thank you zlpan. Removing the update did the job.

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 20. Nov 2015, 19:26
by VM2VM
I can confirm that removing the Windows Patch KB3081320 solves the problem.

At least on:
OS: Fully patched Win 8.1
VB: 4.3.30 r101610

Other relevant links:

Discussion of Problems due to Hardened Security

KB3081320 (10Nov15) breaks VirtualBox 4.3.30 (WinVerifyTrust)

KB3081320 breaks VB 4.3.30 on Windows 8

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 31. Mar 2016, 01:41
by SlowlyButSurly
I'm seeing this on Win8 with 5.0.16;

1. Run Vbox and run a VM...
2. Shutdown VM, close VBox
3. Try to run VBox again and "winverifytrust on stub ...."
4. Do a repair install with 5.0.16, restart
5. goto 1.

I can't remove OS updates and patches at work; has The Vritualbox team root caused this issue? Is there an ETA on a "real" fix?

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 17. Jun 2016, 23:19
by Reddy21
For windows 10 you will have to uninstall update KB3163017 for the same issue.

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 17. Jul 2016, 08:13
by salfosni
Reddy21 wrote:For windows 10 you will have to uninstall update KB3163017 for the same issue.
i don't have that patch and i have W10... still getting the error

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 6. Dec 2017, 16:47
by user7129341
I also received this error when I installed the Windows 64 bit version of Virtualbox on a 32bit Windows host. Whoops!

Re: WinVerifyTrust failiure after Nov 15 Windows 8.1 update

Posted: 6. Dec 2017, 17:30
by mpack
There is no such thing as "Windows 64 bit". Win7 is not the same as Win8 is not the same as Win10, and the latter label is a brand rather than a version, so there are several actual versions of Win10 around.

The 2 year old discussion above concerns Win8 and the VirtualBox version of its day, so time to lock this topic I think. If you have a problem with a current version of VirtualBox and a guest OS which precedes it then you should open a new topic to discuss the issue, providing a zipped VM log attachment in evidence.