-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue]: Invalid settings generation on install when user name contains non-ASCII characters #1107
Comments
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. |
Comment to not let this issue become stale... |
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 |
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 |
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. |
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. |
This issue was closed because it has been stalled for 7 days with no activity. |
What happened?
After a fresh install the generated path for
Node Installations
in thesettings.txt
contains an invalid character sign (�
) for non-ASCII characters and therefore the path can't be found.Node Installations: C:\Users\Ren�\AppData\Roaming\nvm
What did you expect to happen?
The
settings.txt
is generated with a valid path. If that is not feasable an entry in the common issues and resolutions should be added that you need to manually update the path in thesettings.txt
.In the
Relevant log/console output
window you can see thenvm debug
output before and after adjusting the path in thesettings.txt
.Version
1.1.11 or newer (Default)
Which version of Windows?
Windows 10 (Default)
Which locale?
Western European
Which shell are you running NVM4W in?
PowerShell
User Permissions?
Administrative Privileges, Elevated
Is Developer Mode enabled?
No (Default)
Relevant log/console output
Debug Output
Anything else?
No response
The text was updated successfully, but these errors were encountered: