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

nvm use 12.4.0 error #443

Closed
3 of 25 tasks
chasangchual opened this issue Jun 7, 2019 · 9 comments
Closed
3 of 25 tasks

nvm use 12.4.0 error #443

chasangchual opened this issue Jun 7, 2019 · 9 comments

Comments

@chasangchual
Copy link

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

  • [x ] 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:

  • [x ] 1.1.7
  • 1.1.6
  • 1.1.5
  • 1.1.4
  • 1.1.3
  • 1.1.2
  • 1.1.1
  • Older
  • OTHER (Please Specify)

I have already...

  • read the README to be aware of npm gotchas & antivirus issues.
  • reviewed the wiki to make sure my issue hasn't already been resolved.
  • verified I'm using an account with administrative privileges.
  • [x ] searched the issues (open and closed) to make sure this isn't a duplicate.
  • [ x] made sure this isn't a question about how to use NVM for Windows, since gitter is used for questions and comments.

My issue is related to (check only those which apply):

  • settings.txt
  • proxy support (Have you tried version 1.1.0+?)
  • 32 or 64 bit support (Have you tried version 1.1.3+?)
  • Character escaping (Have you tried version 1.1.6+?)
  • A standard shell environment (terminal/powershell)
  • A non-standard shell environment (Cmder, Hyper, Cygwin, git)

Expected Behavior

success to run "nvm use 12.4.0 "

Actual Behavior

failed with

exit status 1: 'C:\Users\Sangchual' is not recognized as an internal or external command,
operable program or batch file.

My user account is Sangchual Cha
Likely it failed because of the space between "Sangchual" and "Cha"

Steps to reproduce the problem:

@ian1dunn
Copy link

I don't know if you already saw this, but someone else had the same issue here.

This comment solved it for me. It's just an issue with spaces existing in the username.
#405 (comment)

@cnscorpions
Copy link

no spaces in path, it works for me

@xmedeko
Copy link
Contributor

xmedeko commented Nov 15, 2019

Yeah, this is duplicate of #405 and #480

@Swarag-N
Copy link

Swarag-N commented May 25, 2020

tl;dr

Solved!!

For someone who is not able to work with ~1 method by @kirkouimet (Thanks mate) in #41
Open CMD go to the Users folder and Get the Shortened Folder name.

and type

> dir\x //This don't work.

[Update]

> dir /x

Annotation 2020-05-25 112714

Now later after copying or Noting down the folder name
Annotation 2020-05-25 113201

Hope it helps

@aaztha
Copy link

aaztha commented Jun 22, 2020

It didn't worked for me,I didn't get any shortened version name!

@Swarag-N
Copy link

Swarag-N commented Jun 22, 2020

The command is dir /x not dir\x
@aaztha

@aaztha
Copy link

aaztha commented Jun 29, 2020

Yeah I wrote the same command@Swarag-N

@franciscohanna92
Copy link

@aaztha Make sure to run the command from a CMD (command prompt) terminal and not a Powershell one.

@coreybutler
Copy link
Owner

Spaces in paths are resolved in https://github.com/coreybutler/nvm-windows/releases/tag/1.1.8

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

8 participants