Hello,

Did some further testing on additional systems in the network. Tried another server, that was not part of the normal Terminal Server deployment, and the issue was present on it as well. Also tried an older version of Office (2010) just to see if it was a 2013/newer issue, but the same error was generated.

Any update or workaround available for this issue yet? Thanks.