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

Attempting /SILENT install fails due to prompts (from existing Node install) #210

Open
6 of 17 tasks
dragon788 opened this issue Oct 6, 2016 · 1 comment
Open
6 of 17 tasks

Comments

@dragon788
Copy link

dragon788 commented Oct 6, 2016

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 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.
  • searched the issues (open and closed) to make sure this isn't a duplicate.
  • 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
  • 32 or 64 bit support

Expected Behavior

When I opt for silent mode and suppressmsg it should default to "Yes" for everything in order to ensure a working application.

Actual Behavior

When attempting to install nvm4w from the installer in silent mode, even with the option to suppress messages it stops and prompts the user about "taking over" the existing install.

Steps to reproduce the problem:

Install nodejs from chocolatey, then try to install nvm via nvm-setup /SILENT or nvm-setup /SILENT /SUPPRESSMSGBOX (whatever the exact option is) and you will get an interactive dialog asking you what you want to do, and canceling the first option or choosing 'no' prompts you again, and the final message seems to be wanting to delete the existing nodejs install even if you selected 'no' in the prior prompts.

@coreybutler
Copy link
Owner

Related to issue #17

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

No branches or pull requests

2 participants