After all the trouble of building VB without the stupid hardening, I now find that I have to keep my Windows 8.1 machine permanently booted in "test signing" mode even when the VB assets are signed with a valid self-signed certificate that I've added to my root certificate store, in order to run (not just install) VB OSE. Only kernel drivers with cross-signed certs (i.e. from Microsoft, VeriSign, etc.) can be run in normal mode.
So, I'm wondering, is there anything in the forum rules prohibiting me from trying to organize a crowd-funded purchase of a code-signing certificate to sign builds of VB OSE? If not here, then I guess I can try to organize it elsewhere. These certificates are crazy expensive, and I shouldn't have to run a compromised machine when I only want to give a pass to VB OSE, and not every other potential kernel driver out there.