I have a quick question regarding how to configure NSSM. I followed the steps posted here: http://www.htpcguides.com/create-sickrag...ervice-v2/ in an attempt to make that Python Command Prompt window stop appearing when SickRage is running.
However, when I download NSSM 2.24 and move the executable to the C:\Windows\System32 I am unable to run a command in cmd.exe starting with nssm. It doesn't recognize it as a valid input. So I added it to the Environment Path thinking that that may help but I achieve the same results.
I'm also running Windows 10 (x64). I grabbed the file that's on this page: https://nssm.cc/download (Latest Release). I know that there is an "All Builds" page but I'm not too sure if I was supposed to grab something from there.
Did you use the nssm 32 bit or 64 bit binary? I am using the 64 bit on Windows 10 x64 and just installed a SickRage service. Can you share the exact syntax you are running.
I'm honestly not too sure. I extracted the contents of the ZIP folder and copied the exe from here: C:\Users\%username%\Downloads\nssm-2.24\nssm-2.24\win64. So I guess the 64-bit binary.
Once I moved it in there I went to Advanced System Settings -> Environment Variables -> TEMP -> Path and added the line ";C:\Windows\System32" to the end of it.
With or without the Path, when I open a command prompt (as Administrator) and enter "nssm install SickRage" it gives me errors.
I've attached a screenshot to this. So when I go to System32 to run it manually, the executable isn't there... which is strange because I know I put it there. So I copied it in there again and I got a prompt asking me to overwrite the nssm.exe that's already there. Apparently it exists in System32, but it is not there at the same time.
[Not Solved]Sep 26, 2015, 12:24 PM (This post was last modified: Sep 26, 2015, 12:25 PM by Mike.)
Something weird is definitely going on. Try explicitly typing nssm.exe. It may have to do with your system adding extra protection to the system32 folder or something like that. You can try removing nssm.exe from system32 and put the nssm.exe somewhere else and try browsing and executing it manually again.
If it still won't budge I'd do this next:
Fire up a Windows 10 virtual machine and put nssm.exe in system32. Then start adding the same programs you have on your main machine into the virtual machine, see if something clicks.