I have now also tried the later release v17.0.2 and the error is still the same.
Hopefully VMware will find a way to fix this.
