From my perspective, VMware is aware of an issue:
– appears they have been aware for aprox. 2 mos.
– appears it has to do with VMFS6 configured storage
– appears it begins with 1803
– appears there may be a hot fix, however, the ask from VMware is to build out a debug environment to test
We are moving to our own ‘Plan B’ to keep our Win10 project rolling. This consists of setting up seperate storage configured with VMFS5.
Will continue to update as I see this play out.