Yes, even with version 16.2.2 build-19200509 the problem still exists in different scenarios. If it takes too long until a paused machine is resumed, the error occurs. The same applies if the disk is compressed in a Linux machine (vmware-toolbox-cmd disk shrink /). Even the workaround
isolation.tools.hgfs.oplockmonitor.enable = "FALSE"
does not help in this case. Only
mks.sandbox.socketTimeoutMS = "1000000"
helps.
