It seems, for me, that everything is working as expected -- all the latest versions (that include the "Generic Hardening Fixes" from several months ago), are all still working just fine as the host, on Windows 10 Build 14926, and the older versions (from before the "Generic Hardening Fixes) don't work, as expected. Details below.
Generic Hardening Fixes first implemented in:
VirtualBox v5.0.19 Test Build 106880
VirtualBox v4.3.39 Test Build 106879
Immediately crashes (with WerFault.exe) on host Windows 10 Build 14926 (released today):
VirtualBox v5.0.18 Build 106667
VirtualBox v4.3.38 Build 106717
Works (launches and can start/resume VMs) on host Windows 10 Build 14926 (released today):
VirtualBox v5.1.7 Test Build 110653
VirtualBox v5.1.6 Build 110634
VirtualBox v5.0.27 Test Build 110660
VirtualBox v5.0.26 Build 108824
VirtualBox v5.0.20 Build 106931
VirtualBox v4.3.40 Build 110317
Oracle VirtualBox v5.0.27 Test Build 110660... has been working just fine, on my "Windows 10 Build 14936" host.
I'll run a quick check of 5.1.x later, but ..
Thought it was odd that no one complained for that build or the one since. Wasn't sure if things were fine or if I should schedule half a day playing version whackamole.
Yeah, I think Microsoft either got confused, or were talking about Windows 10 clients (instead of hosts), not sure.
Regarding running it on hosts:
When they had that note for 14931, my thorough testing showed that it worked fine on Windows 10 hosts for that build. See 4 posts ago.
I'm working fine on 14936 host, too.
I'm noticing a problem, also. I'd like to create a new thread, and then I'll put a bunch of info in the first post, then you can look to see if it matches up with your data. Sound good?
Yes, this thread's too old, though there's not much data. Logs don't get written here and there's no error message. Just what's in Event Viewer, I think.
Maybe it can be an RS2 general thread, one good until RS2 goes final? Rather than build-specific.
Just right after the upgrade process at first boot.
