Hello,
We just experienced this same issue on a Windows Server 2012 R2 VM that was recently migrated from a vSphere 5.5 cluster to a new 6.5 cluster.
Did you find a permanent resolution? Did disabling power management work?
Thanks
Hello,
We just experienced this same issue on a Windows Server 2012 R2 VM that was recently migrated from a vSphere 5.5 cluster to a new 6.5 cluster.
Did you find a permanent resolution? Did disabling power management work?
Thanks