What happened?

Running nvm use 22.12.0 won't set the current version.

I had the previous version installed. After running the v1.2.0 installer, Node.js won't work anymore. I uninstalled NVM4W and removed any Node.js reference I could find. Re-installed v1.2.0 and run nvm install lts and nvm use 22.12.0 and it still didn't set the current version.

I tried different prompts/shells: PowerShell for Windows, PowerShell 7, Command Prompt, Bash.

I also tried to run the installer as Administrator.

I verified that Environment Variables are set.

Then I noticed that there was also no folder nvm4w under C:\.
After creating that folder and manually creating the symlink, I finally had a working current version.
C:\nvm4w>mklink /D "nodejs" "C:\Users\jeron\AppData\Roaming\nvm\v22.12.0"

(Probably creating the folder was enough, and adding the symlink was redundant)

Maybe the new C:\nvm4w\ directory is not created during installation and symlink fails silently.

What did you expect to happen?

NVM use should set the current version.

Version

1.2.0 or newer (Default)

Which version of Windows?

Windows 10

Which locale?

English (Default)

Which shell are you running NVM4W in?

Command Prompt, PowerShell

User Permissions?

Standard User, Elevated

Is Developer Mode enabled?

No (Default)

Relevant log/console output

No response

Debug Output

jeron is not using admin or elevated rights.
Windows Version:        10.0 (Build 19045)
Windows Developer Mode: UNKNOWN
NVM4W Version:          1.2.0
NVM4W Path:             C:\Users\jeron\AppData\Roaming\nvm\nvm.exe
NVM4W Settings:         C:\Users\jeron\AppData\Roaming\nvm\settings.txt
NVM_HOME:               C:\Users\jeron\AppData\Roaming\nvm
NVM_SYMLINK:            C:\nvm4w\nodejs
Node Installations:     C:\Users\jeron\AppData\Roaming\nvm
Default Architecture:   64-bit
Mirrors:                No mirrors configured
HTTP Proxy:             none
Total Node.js Versions: 2
Active Node.js Version: none
(run "nvm use <version>" to activate a version)
NVM_SYMLINK does not exist yet. This is auto-created when "nvm use" is run.
PROBLEMS DETECTED
-----------------
"pwsh in jeron" not recognized: the Command Prompt and Powershell are the only officially supported consoles. Some features may not work as expected.

Anything else?

Based on nvm debug results it appears that PowerShell (and also Command Prompt) is not correctly recognized within the Windows Terminal program.