Seeing as this is an issue with VMWare + Hyper-V integration, it would seem that Microsoft has a role to play in fixing this, since this integration was a joint project between Microsoft and VMWare (see: -workstation-now-supports-hyper-v-mode.html), and it no longer works correctly due to patches that Microsoft introduced.