I did indeed perform the test I said I would in the above post. TP vmcs.sys and vsock.sys failed to satisfy Microsoft driver verification and blue screened. Remove the two drivers and rebooted (this time the OS was forced to chkdsk and in fact found incorrect files, attributes and index problems it fixed. First time I needed to chkdsk so nothing lost except a bit more time.Therefore, on my system,
Host: Windows Server 2016 TP2 with essential features.
VMware WS 11.1.02 installs and runs nominally.
VMware July TP installs but fails after reboot (blue screen)
Solution: Boot from install disk - enter recovery mode, choose open command prompt, delete vmci.sys and vsock.sys from c:\windows\system32\drivers. Reboot, uninstall TP via Add/Remove Programs. Reinstall WS 11 GA.
I'll need to wait until the next TP (September?) to continue testing. In the meantime I'll work on seeing what I can do with WS 11 on this server and Hyper-V on the workstation running Windows 10 final.
In the meantime perhaps the developers can work on a interim fix for their drivers so they run on Windows Server 2016 TP or maybe I will just wait for server tech preview 3 which is rumored to be out by years end.
Good luck with further testing
Marty Felker