Thanks Richard.

Are there any other workarounds other than disabling compression settings?

We won't be moving to 2019 for some time. This issue only seemed to present itself following upgrade to Windows 10.