Throws ERROR open \settings.txt in windows 7

[byteshiva]

I'm getting this error "ERROR open \settings.txt: The system cannot find the file specified." after installing in windows 7.

[coreybutler]

Closing as a duplicate of issue #22.

[byteshiva]

I'm getting the same error after installing 1.6.0 with hotfix.

PFA for settings.txt folder

[coreybutler]

Sorry, I referenced the wrong issue when I closed this. It has still been filed before though. Please see issue #22.

[byteshiva]

The workaround mentioned in #22 worked!!

For wider audience I'm detailing the steps
Steps followed,

1. Open cmd using Admin Privilege
2. cd c:\users\AppData\Roaming\nvm
3. cp settings.txt to c:\

I could use to copy settings.txt to c:\ .

[reflexdemon]

Oops! none of the workaround works for me.

I get the below error.

cp: cannot create regular file 'c:\\settings.txt': Permission denied

[jamesmanning]

@reflexdemon needs to be an elevated cmd - make sure the title bar of the cmd.exe window says "Administrator:" like in the sshot.

[reflexdemon]

@jamesmanning apparently, I have a to do this on my work machine where I dont have admin rights.

[dreamingUpCode]

Had the same issue on Win 10. Reinstalled it and works fine now.

[hutber]

I know its stupid, but I don't really like having a settings file in my root :( I like a clean drive at all times

[jamesmanning]

@jamiehutber @reflexdemon just searching for settings.txt seems to indicate that it's looking for the file related to the NVM_HOME environment variable, so setting that might be sufficient?

From an elevated cmd prompt, you should be able to run:

setx /m NVM_HOME %APPDATA%\nvm  

Then open a new cmd prompt (so it has that variable set, it won't populate into existing ones) and try nvm without settings.txt in the root?

Seems like the install mechanism should set that variable if it's not already set, I would guess?

It looks like the 'manual' install method already does so, AFAICT.

[lorezzed]

@byteshiva use "copy" instead of "cp" if you don't have cygwin:

1. Open cmd using Admin Privilege
2. cd c:\users<username>\AppData\Roaming\nvm
3. copy settings.txt c:\

Works a treat thanks.

[kpentchev]

@jamesmanning thank you!

[henrycaosg]

@jamesmanning thank you!

[kkoci]

@byteshiva Awesome, worked like a charm!

[fritx]

When I clicked the install.cmd, the settings.txt prompted, but I didn't save the file.
The settings.txt would never prompt again.
What could I do?

[ghost]

@jamesmanning Works great.

Now why doesn't the installer do this for you?

[coreybutler]

@errorx666 - The installer attempts to do this. However; I've seen hundreds of configurations now that are pretty customized... typically the installer fails silently due to a missing permission. The next version will have a new installer, but that may still be a ways off. Installers are, without any doubt whatsoever, the most time consuming element of this entire project.

For anyone coming across this, I'm looking for contributors who will build and maintain installers across different operating systems.

[ghost]

@coreybutler It may be as easy as changing the installer filename. IIRC, Windows uses the setup.exe filename as a heuristic for backwards compatibility, and automatically creates a UAC prompt to elevate to admin privileges. I'm not sure if Windows' default configuration of opening zip files as "Compressed Folders" affects anything, but in my case, it removed the "Run as Administrator" option from the context menu, and probably led to my broken installation.