Skip to content

[Issue]: install to Temp instead of root #1307

@HelloChandler

Description

@HelloChandler

What happened?

  1. Open PowerShell (as Administrator)
  2. Run: nvm install 18.17.0
  3. Observe that Node files are left in %TEMP% instead of E:\nvm\v18.17.0

Expected Behavior

Node should be installed under the NVM root directory (E:\nvm\v18.17.0).

Actual Behavior

Node files remain in C:\Users\<Username>\AppData\Local\Temp and are not copied to the NVM root directory.

Environment

What did you expect to happen?

Files should be installed under nvm root directory

Version

1.2.0 or newer (Default)

Which version of Windows?

Windows 10

Which locale?

Asian

Which shell are you running NVM4W in?

PowerShell

User Permissions?

Administrative Privileges, Elevated

Is Developer Mode enabled?

None

Relevant log/console output

PS C:\WINDOWS\system32> nvm root

Current Root: E:\nvm
PS C:\WINDOWS\system32> nvm install 18.17.0
Downloading node.js version 18.17.0 (64-bit)...
Extracting node and npm...
Complete

Installation complete.
If you want to use this version, type:

nvm use 18.17.0
PS C:\WINDOWS\system32> nvm use 18.17.0
activation error: Version not installed. Run "nvm ls" to see available versions.
PS C:\WINDOWS\system32> nvm list

No installations recognized.

Debug Output

PS C:\WINDOWS\system32> nvm debug
Running NVM for Windows with administrator privileges.

Windows Version:        10.0 (Build 19045)

NVM4W Version:          1.2.0
NVM4W Path:             E:\nvm\nvm.exe
NVM4W Settings:         E:\nvm\settings.txt
NVM_HOME:               E:\nvm
NVM_SYMLINK:            E:\nodejs
Node Installations:     E:\nvm
Default Architecture:   64-bit
Mirrors:                https://nodejs.org/dist/ (node) and https://github.com/npm/cli/archive/ (npm)
HTTP Proxy:             none

Total Node.js Versions: 0
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.

IPv6 is enabled. This has been known to slow downloads significantly.
If you are experiencing npm problems, check the npm mirror (https://github.com/npm/cli/archive/) to assure it is online and accessible.

No problems detected.

⚠️  We are currently building Author/Runtime to succeed NVM for Windows.


Find help at https://github.com/coreybutler/nvm-windows/wiki/Common-Issues

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions