For anyone else experiencing this problem using Azure DevOps, it's useful to turn on debug mode. For your release, define the pipeline variable System.Debug with value true.
That gave me this output which was much more useful:
Now at least I know it's on my target VM and the path is probably wrong.