Version 1.4.2 for Windows does not work

[radio-miskovice]

C:\...> nvs

'nvs' is not recognized as an internal or external command, operable program or batch file.

It would be nice if the windows installer either set the PATH to the NVS directory, or if it displayed any hint where to find it, or if the documentation would mention what is the target directory for the NVS installation on Windows. Ideally, all three of them. Unfortunately, there is nothing in the docs and no message during the installation, so I can only guess where in the several thousands of directories it could be...

I checked all the "usual places", i.e. \Program Files and \Program Files(x86) as well as \WINDOWS, and it is just nowhere. At least nowhere where it could be normally found.

[jasongin]

The installer does add nvs to your PATH. If you have any console windows open you would need to close and reopen them for that change to take effect.

The installation path depends if you selected a per-user or per-machine installation. If per-user (recommended to avoid admin prompts) it is at %LOCALAPPDATA%\nvs.

[radio-miskovice]

Thank you, found it! Unfortunately, there was still something going wrong unnoticed during the installation. Apparently PATH was not updated. PATH was updated when, after successful MSI installation, I started manually nvs install (apparently updated PATH in Windows registry, works for any new command shell window). However, any further attempt to start nvs fails due to company policy not permitting running PS scripts. The policy is controlled by domain admin, therefore it is out of my control and cannot be overidden (although I am local admin on the machine).

I assume that there is no other way how to start NVS, only via the PS script... So, sorry, won't work for me :-(

[radio-miskovice]

C:\Users\JVavruska>nvs
. : File C:\Users\JVavruska\AppData\Local\nvs\nvs.ps1 cannot be loaded because 
running scripts is disabled on this system. For more information, see about_Execution_Policies
at http://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3
+ . 'C:\Users\JVavruska\AppData\Local\nvs\nvs.ps1' bootstrap
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

C:\Users\JVavruska>

[BCool13]

My two cents. Have you change your system PowerShell Script Execution Policies ? If not try to change the registry key HKEY_CURRENT_USER\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell to RemoteSigned. It works for me.