I copied this from LHC's forums about VB errors for any one that it may help.
From: Jacob Klein
Sent: Wednesday, January 4, 2017 10:48 AM
To: Rom Walton; Marius Millea
Subject: Re: vbox debugging
I'll chime in.
Oracle VirtualBox has a "Windows process hardening" security system in their code, that will intentionally disallow VMs to run, if the security check fails. The code is a bit fragile, and when new "Windows Insiders" builds of Windows 10 get releases, they are prone to cause the problem, until Oracle fixes it. And those would lead to your problems I think.
That link Rom gave, is the best avenue to keep track of which Win10 builds work against which VBox versions.
https://forums.virtualbox.org/viewforum.php?f=38
Ultimately, what you need to do (to determine if the problem was caused by Oracle VirtualBox's "Windows process hardening"), is:
Make 2 tables.
Table 1:
Windows 10 Build Version || Minimum Oracle VirtualBox Version including the R number, which passes security check
Table 2:
VBoxWrapper Version || Maximum compatible Oracle VirtualBox Version
Building Table 1 will involve going through all those threads in that forum. Which you could do!
For instance, I know for fact that, in order to run Win10 Build 14971 or 14986, without error, you must use these VirtualBox branch versions or newer:
VirtualBox 4.3.41 r112025
VirtualBox 5.0.29 r112021
VirtualBox 5.1.9 r112020
Another for instance, is..
If you're using VBoxWrapper 26167, you must use VirtualBox 4.3.x or older
If you're using VBoxWrapper 26184, you must use VirtualBox 5.0.x or older
If you're using VBoxWrapper 26197, you must use VirtualBox 5.1.x or older
Are we having fun yet?
Regards,
Jacob