-
-
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
Nvm use failed with "Windows cannot access the specified device, path, or file..." #415
Comments
No, what I see is exactly as how I described it. No elevation or VB error. |
I have something similar here, not sure if it's the exact same issue though. |
I'm not able to reproduce on my machine. Is it possible due to a custom installation path on the C drive as the root instead of installing NVM in the default AppData directory? My NVM path is |
I'm on Windows 10 64 Bit German.
Rougly translated from German:
It probably is related to the whitespace in one of the path names. After a full uninstallation I did the installation again, but with "C:\Programme-Meine" (no whitespace!) and it seems to work now. I'm sorry if this should not be related to this issue. |
Like PyrateAkananto, I installed both node and nvm in To fix, I edited the settings.txt file;
|
I'm experiencing the reported problem as well. However, only when I run on an elevated command prompt. I don't think this is a whitespace problem, as I have tried to change the path to a non-whitespace-path location, which didn't change anything. I do have a McAfee Installation, which is why I maybe ran into #551. Could this be Anti-Virus related as well? Edit: |
Closing due to age. This has been addressed in both v1.1.8 and v1.1.9. If the issue persists, please review https://github.com/coreybutler/nvm-windows/wiki/Common-Issues#permissions-exit-1-exit-5-access-denied-exit-145. Open a new issue if this does not help. |
If this is a question about how to use NVM4W, please use stackoverflow instead.
If this is an issue regarding antivirus, make sure you search the existing issues first.
My Environment
Windows 7 or below (not truly supported due to EOL - see wiki for details)
Windows 8
Windows 8.1
Windows 10
Windows 10 IoT Core
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
My Windows installation is non-English.
I'm using NVM4W version:
I have already...
My issue is related to (check only those which apply):
Expected Behavior
Should activate Node v8.15.0
Actual Behavior
After running
nvm use 8.15.0
and approving session elevation I got a pop up errorWindows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.
Back in the terminal, it shows message
Now using node v8.15.0 (64-bit)
but when I runnvm list
I don't see an asterisk on8.15.0
. Also, runningnode
andnpm
returns an error that they don't exist.Steps to reproduce the problem:
nvm install 8.15.0
nvm use 8.15.0
My root path doesn't contain any white space. This is a problem I'd likely need to debug (an excuse to try out Go)
The text was updated successfully, but these errors were encountered: