Fail to read C:/Users/<username>/.ssh/config if the local username profile contains an accented character

Is there an existing issue for this bug?

• I have searched the existing open issues and found none that apply.
• If I find any issue of interest that is related or closed, I will included a link to it in this issue.

Required Troubleshooting Steps

• I have read and performed the troubleshooting steps
• I have tried both values of the remote.SSH.useLocalServer setting
• My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
• I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar

[Optional] Diagnose with Copilot

I did not ask the @remote-ssh participant for help

In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?

I did not try step 2 of the troubleshooting steps

Remote-SSH Log

[09:38:39.533] Picking SSH host

Expected Behavior

I can connect to a ssh host

Actual Behavior

Steps To Reproduce

Be unlucky enough to have a non-ascii name

Anything else?

If I manually set the path to the config, it works. But then there is another bug:

The terminal process failed to launch: Starting directory (cwd) "C:\Users\Timoth�eMAURICE" does not exist.

It seems the 1.101 update broke handling of non-ascii, as this behavior started occurring right after I updated.

Start by reproducing a Remote-SSH connection on Windows with a non-ASCII local username, using the Remote-SSH log and both values of remote.SSH.useLocalServer. Compare automatic SSH config discovery with the manually specified path and verify that the terminal's starting directory works; done means both connection setup and the terminal handle the accented profile path correctly.