NSSM - The Non-Sucking Service Manager icon
NSSM - The Non-Sucking Service Manager icon

NSSM - The Non-Sucking Service Manager

nssm is a service helper which doesn't suck. srvany and other service helper programs suck because they don't handle failure of the application running as a service. If you use such a program you may see a service listed as started when in fact the application has died.

Environment tab

Cost / License

  • Free
  • Open Source

Alerts

  • Discontinued

Platforms

  • Windows
Discontinued

Last release is from 2014, and last pre-release is from 2017, but it can still be downloaded from the official website.

21likes
0articles
Save

Features

Features

Highlights All activities

NSSM - The Non-Sucking Service Manager News & Activities

Recent activities

NSSM - The Non-Sucking Service Manager information

AlternativeTo Category

OS & Utilities

Popular alternatives

View all
NSSM - The Non-Sucking Service Manager was added to AlternativeTo by CyberInferno on and this page was last updated . NSSM - The Non-Sucking Service Manager is sometimes referred to as NSSM, Non-Sucking Service Manager. 

No comments or reviews, maybe you want to be first?

Featured in Lists

My Go To Software - Cross Platform & FOSS

Great Software that Never Lets Me Down AlternativeTo won't let me add it to the list, but Windows Ameliorated is incredible: https://ameliorated.info/
By Kai Nau66 appsUpdated

Official Links

Install from the command line

  • winget install -e --id NSSM.NSSM

Be careful what you paste into a terminal. Check what a command installs before running it.

What is NSSM - The Non-Sucking Service Manager?

nssm is a service helper which doesn't suck. srvany and other service helper programs suck because they don't handle failure of the application running as a service. If you use such a program you may see a service listed as started when in fact the application has died. nssm monitors the running service and will restart it if it dies. With nssm you know that if a service says it's running, it really is. Alternatively, if your application is well-behaved you can configure nssm to absolve all responsibility for restarting it and let Windows take care of recovery actions.