[Issue]: Invalid settings generation on install when user name contains non-ASCII characters about nvm-windows

[magynhard]

Same Problem here:

Opening settings.txt and converting it to UTF-8 using Notepad++ solved it.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[renepanke]

Comment to not let this issue become stale...

[iancward]

We did the noinstall method for NVM and wrote out the settings.txt file with PowerShell, which caused the file to be generated in the (PowerShell default) UTF-16LE encoding, which caused an issue just like this.

Converting the settings.txt to ascii fixed it. It didn't work even with regular UTF-8.

[iancward]

That's interesting you got it to work using UTF-8; for me, I could only get it to work if the file was ASCII
#1124

[magynhard]

I was running on Windows 11 with German locale on the latest nvm 1.1.12 on node 18.12.1

Using the classic command line (cmd).

Notepad++ recognized the settings.txt as ASCII format, so i chose "convert to UTF-8" and it worked.