After install every command fails with message "C:\Users\%username%\AppData\Roaming\nvm could not be found or does not exist. Exiting."

[bevalorous]

If %username% in path C:\Users\%username%\AppData\Roaming\nvm contains some non-latin symbols (in my case username is written with cyrillic characters), every nvm command displays this error message, for example:

C:\Windows\system32>nvm arch
C:\Users\�����\AppData\Roaming\nvm could not be found or does not exist. Exiting.
System Default: 64-bit.
Currently Configured: 64-bit.

Possible solution is to write settings.txt with encoding UTF-8 instead of ANSI. After manual correction of file encoding with Notepad++ error message disappears and now everything works fine:

C:\Windows\system32>nvm arch
System Default: 64-bit.
Currently Configured: 64-bit.

[yornaath]

The encoding fixed it for me as my name contains "ø".

[jchn-codes]

fixed the issue for me! Thanks! (name contains "ß")

[janjon]

I changed to UTF-8 after,

C:\WINDOWS\system32>nvm arch
**There's a space. C:\Users\中文\nvm could not be found or does not exist. Exiting.
System Default: 64-bit.
Currently Configured: -bit.

[lnaie]

this fails: C:\Users\Lucian Naie\AppData\Roaming\nvm

[espoelstra]

@lnaie I think there is another issue regarding spaces or whitespace in the user name, please add your voice there.
@janjon Do your NVM_* environment variables have the correct values in them if you do a gci env: in a PowerShell window?

[firrae]

I think I have the same issue as my account has a period between my first and last names.

[LizanLycan]

Problem is maintained with blanks

[jose-vasquez-mantum]

Please, solve the problem with blanks in the account name, thanks

[coreybutler]

@jose-vasquez-mantum - I would accept a Pull Request if someone fixes it.

[urbgimtam]

If anyone is suffering from this, here's a suggestion:

• type "nvm root" to know where is the nvm current path
• In windows explorer, copy the contents of the previous path to a simpler path like "c:\nvm".
• In system variables, search for NVM_HOME and update its value to the new path.
• Then type "nvm root [new path]" (like "nvm root c:\nvm").
  (don't forget to close cmd, and open a new one.)

Everything should work without problems.

On a side note, I would like to help, but I don't know Go, so...

[klreeher]

I also have a space in my Windows User folder, and @urbgimtam's work around worked for me.

[Bekhx]

If %username% in path C:\Users\%username%\AppData\Roaming\nvm contains some non-latin symbols (in my case username is written with cyrillic characters), every nvm command displays this error message, for example:

C:\Windows\system32>nvm arch
C:\Users\�����\AppData\Roaming\nvm could not be found or does not exist. Exiting.
System Default: 64-bit.
Currently Configured: 64-bit.

Possible solution is to write settings.txt with encoding UTF-8 instead of ANSI. After manual correction of file encoding with Notepad++ error message disappears and now everything works fine:

C:\Windows\system32>nvm arch
System Default: 64-bit.
Currently Configured: 64-bit.

Thanks a lot, this solution helped me!

[juliavaz]

This #334 was very useful to me, where does it say to run on terminal nvm root C:\Users\username\AppData\Roaming\nvm

[coreybutler]

encodings and white space are now supported in path names as of v1.1.8.

[JoaoVitorLima242]

If anyone is suffering from this, here's a suggestion:

• type "nvm root" to know where is the nvm current path
• In windows explorer, copy the contents of the previous path to a simpler path like "c:\nvm".
• In system variables, search for NVM_HOME and update its value to the new path.
• Then type "nvm root [new path]" (like "nvm root c:\nvm").
  (don't forget to close cmd, and open a new one.)

Everything should work without problems.

On a side note, I would like to help, but I don't know Go, so...

Thanks man! This really help me!

[LesyaSvk]

Nothing works(
At instuction to nvm is line - "If NVM4W doesn't appear to work immediately after installation, restart the terminal/powershell (not the whole computer)." BUT computer restar really help me. Everything works without any problem

[AlibekMussin]

Why the heck this it trouble till this day already? UTF-8 sooooo long existing.

[maxbond2]

2023! Encoding bug still don't fixed!...
@bevalorous Thank you very much for solution!!!

[wcaroman]

Thank you very much, you are my savior! Hate russian win versions, always make a lot of issues

[WildeMax]

This #334 was very useful to me, where does it say to run on terminal nvm root C:\Users\username\AppData\Roaming\nvm

Thanks! It works!