We are using Run-Executable to run various executables in Windows provisioning scripts, however their stdout and stderr are missing in log. As a result, if something goes wrong it may be hard to understand why. In particular, I'm interested in getting logs from conan, which is rather chatty.

People say [1] that this is inherent peculiarity of Start-Process. One possible workaround is to redirect stdout and stderr into separate files and upload them alongside with provisioning logs, however each invocation of Start-Process seems to overwrite existing log files instead of appending. Other way is to replace Start-Process with something else.

[1] https://stackoverflow.com/questions/8761888/capturing-standard-out-and-error-with-start-process