nschlip
Enthusiast
Enthusiast

Thanks for this info - exact same issue we're experiencing. Doesn't matter if it's Win 10 1803, 1809, or 1903 - VMFS5 of VMFS6, using Pure Storage or vSAN. I also completely left out Horizon and just composed a Win10 VM in vSphere from a template, and THAT helped. It seems if you create all dedicated Win10 VM's from a template (which won't have associate snaps) the issue is fixed, but that's only a workaround (if you have the host resources).

Reply
0 Kudos