Skip to content
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

Access is denied #700

Closed
ClusterH opened this issue Nov 22, 2021 · 20 comments
Closed

Access is denied #700

ClusterH opened this issue Nov 22, 2021 · 20 comments

Comments

@ClusterH
Copy link

Issue:
After install nvm 1.1.8, nvm install lts, it seems installing node 16.13.0.
But when I do nvm use 16.13.0 or nvm use lts, got error like that: exit status 1: Access is denied

Tried open cmd as administrator, but it does not help

@ClusterH
Copy link
Author

Tried again reinstall nvm and nvm install 16.13.0, it worked. but it is really weird, why did not worked with nvm install lts

@quanticle
Copy link

I'm getting the same error with nvm use latest, when running PowerShell as a regular user. When I run PowerShell as admin, nvm use latest works.

@erikyuzwa
Copy link

Hitting this lately as well when I want to switch to any node version. Had to run my cmd shell as Administrator for it to work

@robertwt7
Copy link

I'm getting this error as well, was about to open an issue

@JeffersonUCC
Copy link

same here. Prior to 1.1.8 system would prompt me to grant admin privileges. I think the issue might be nvm not using the elevated.cmd to get admin status.

@chaostheory
Copy link

This might be related to this issue, but I was able to install node 16. However, if I try to use npm, then I get hit with the Access Denied error.

@lawweiliang
Copy link

I am having this problem with my 'Cmder Console' as well.
image

Over Command Prompt Administrator, no problem
image

@onikienko
Copy link

Same issue. Possible it is because v1.1.8 is not code signed. Installing v1.1.7 resolves the issue.

@hyf510
Copy link

hyf510 commented Dec 7, 2021 via email

@danillolima
Copy link

I tried both v1.1.7 and v1.1.8 and both need to run with administrative privileges to change the versions of node.

@coreybutler
Copy link
Owner

Admin privileges are required (by the operating system) to create the links. If the error states "insufficient privileges", it means exactly that. You need an admin account.

For those of you struggling with nvm use latest, lts, or newest - there was a bug introduced with these aliases. I've fixed this locally and will release it as v1.1.9 very soon.

For those installing a version with npm v5.x.x - there are hard coded issues in some versions of npm that have affected node version managers. See the wiki and search the issues for more details.

I have also reintegrated automatic elevation. This means you will be prompted with the UAC prompt when needed. If you are running in "Developer mode", the prompts are unnecessary and will not be displayed.

These issues have nothing to do with code-signing. However; the next release will be code-signed, thanks to a generous sponsor whose financial contribution made it possible to obtain an extended validation certificate.

I will close this issue when v1.1.9 is released (this week).

coreybutler added a commit that referenced this issue Dec 7, 2021
@erikyuzwa
Copy link

thanks for moving on this @coreybutler - appreciate it 🙇

@coreybutler
Copy link
Owner

v1.1.9 has been released.

@matthiasthieroff
Copy link

Hey Corey,
thanks for your great work. Unfortunately the "access is denied" error is still present with v1.1.9 on powershell 7.2. There is also no automatic elevation happening. I just had a fresh installation on a new Windows 10 system.

@quckslvr
Copy link

quckslvr commented Dec 14, 2021

He @coreybutler same thing too

Did nvm install 16.9.1 and when I do nvm use 16.9.1 it prompt exit status 1: Access is denied.

I followed the readme to delete node.js delete the files mention and still experience the issue.

on the other on admin it works but not on my user.
USING V1.1.9

@lehug
Copy link

lehug commented Dec 14, 2021

open windows terminal with Administrator, and rerun the command nvm use x.x.x,then it works.

and also,next time to open windows terminal without administrator, node can work well.

@MattHoneycutt
Copy link

Same issue here, fresh install on Win 11. I downgraded to 1.1.7, and everything works great.

@dgchrt
Copy link

dgchrt commented Dec 31, 2021

Same here. After removing 1.1.9 and installing 1.1.7 (without Administrator privileges) everything works fine, apart from the lts alias:

Microsoft Windows [Version 10.0.19044.1415]
(c) Microsoft Corporation. All rights reserved.

C:\Users\User>nvm version
1.1.7

C:\Users\User>nvm install lts
lts.0.0
Node.js vlts.0.0 is only available in 32-bit.

C:\Users\User>nvm install 16
16.0.0
Downloading node.js version 16.0.0 (64-bit)...
Complete
Creating C:\Users\User\AppData\Roaming\nvm\temp

Downloading npm version 7.10.0... Complete
Installing npm v7.10.0...

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

nvm use 16.0.0

C:\Users\User>nvm use 16.0.0
Now using node v16.0.0 (64-bit)

@ojintoad
Copy link

ojintoad commented Mar 9, 2022

This item covers some things people are posting here and likely should be followed instead: #767

@afanfian
Copy link

Who knows someone can help, because I've tried several times still can't use the node js version through nvm, thank you
Problem
image
Path NVM
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests