Tess Gauthier

Thanks. Can you provide the MSBuild diagnostic log? It's located here: `.\openssh-portable\contrib\win32\openssh\OpenSSHReleasex64.log` Another thought - have you tried to rerun the build script in a new PowerShell session after installing...

Thanks for the log file. Can you replace `.\openssh-portable\contrib\win32\openssh\OpenSSHBuildHelper.psm1` with the contents of this [file](https://github.com/tgauth/openssh-portable/blob/build-script-updates/contrib/win32/openssh/OpenSSHBuildHelper.psm1) and retry the build? We were explicitly setting `env:vctargetspath` for Visual Studio 2015, but newer...

It might be easier to build in Visual Studio directly until we can work on the build script fixes - updates have been made to the [build instructions](https://github.com/PowerShell/Win32-OpenSSH/wiki/Building-OpenSSH-for-Windows-(using-LibreSSL-crypto))

Thanks for raising this issue! Just a note - I think the affected versions are V8.9.1.0 & V8.9.0.0. I am not able to repro with V8.6.0.0.

The ARM32/ARM64 binaries will be published as zip pkgs, starting with the next release.

https://github.com/PowerShell/openssh-portable/blob/latestw_all/regress/pesterTests/utilities/askpass_util/askpass_util.exe

@Farmbuyer - sounds like you no longer need a fix immediately, but if you have a chance, could you try out the above suggestions from @jannikac and @weavage & see...

@whentojump, what OpenSSH version are you using? The latest GitHub release or the Windows in-box version?

@whentojump ah so, `-B` and `-b` are two different parameters for ssh. This issue was closed since -b support was added, however `-B` is still not supported. I updated the...

> Recent [Windows Terminal](https://github.com/microsoft/terminal) now support a lot of 8bit character code encoding, including all iso8859 cp. > > Even we change to e.g. iso8859-2 (chcp 28592) OpenSSH switch back...