-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Installation completes ... then executable does nothing #301
Comments
On some systems, the installer doesn't quite finish before it tries to launch the terminal. I was never able to force it to run synchronously, so on occasion this occurs. It's rare, but has happened a handful of times. The fix is simple though.... close the terminal and open it again. |
FYI, there seems to be an error in the program which prevents it from doing anything when launched. When launched, it looks for the "\settings.txt" , can't find it, and crashes. The file is in the same directory as the executable, NOT in the root directory. I circumvented this problem by copying the file to the root directory for now. The only problem now is that the program does nothing useful (version 1.1.6). I ask it to install node 5.12 and it replies that it installed it after a short delay. Then it's impossible to switch to it. And node is not even available anymore at all. Can't ask for the version number, can't run npm. Installed 1.1.5. Asked for 5.12 to be installed: pgm replied that it's there already. Asked to switch to 5.12: replied done. Checked node version: 5.12. All ok. |
I tried running it from command line again and it worked. Thanks for the
help
…On Thu, Sep 14, 2017 at 6:59 PM Mmikeyy ***@***.***> wrote:
FYI, there seems to be an error in the program which prevents it from
doing anything when launched.
When launched, it looks for the "\settings.txt" , can't find it, and
crashes.
The file is in the same directory as the executable, NOT in the root
directory.
I circumvented this problem by copying the file to the root directory for
now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#301 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWTsl1-y8QuThs7VX52VydO0pKF95kAWks5sia_BgaJpZM4PVES_>
.
|
I just installed nvm through chocolatey and have the same issue:
(after adding |
I installed via nvm-setup.exe 1.1.9 to C:\nvm (because the default location in AppData results in exit status 1 error when trying to
|
This issue still exists in 2022 with Windows 11. For example, if you install via choco (silent CLI script), it installs fine -- but does not work until you restart Powershell; not even with the standard scripts to refresh the env vars, eg:
nvm is completely unusable until you restart PS - there's something undocumented that needs to happen in addition to refreshing the env vars. EDIT: Found a temporary workaround:
|
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
Run the installer, use it correctly, run the program, it works.
Actual Behavior
The above, except it doesn't work. The installer.cmd does absolute jack when I try to run it.
I run the .exe file and it just flashes a cmd window.
Steps to reproduce the problem:
I don't know if this is reproduceable or just something I have wrong with my computer
The text was updated successfully, but these errors were encountered: