I'm exploring how to run arbitrary .exe files as Windows services. Over the years, I've transitioned various services from one server to another, and I ended up developing a solution that makes this easier. This includes converting .exe files into services, creating services with a graphical interface, and allowing JSON-based configurations for easy import/export. I've also implemented logging for stdout and stderr, automatic restarts on failure, and additional notifications via email, Discord, or Telegram. I'm even considering adding a Build button to generate an installer that includes the service. I'd love to hear about your experiences! What features do you find most essential in tools like NSSM or WinSW?
5 Answers
It's essential to understand that Windows services require specific functionality built into the app. If you want to run an .exe as a service, tools like NSSM, srvany, or commercial options like FireDaemon can help you bridge that gap. Personally, I usually favor using scheduled tasks for most applications, but those tools are reliable too!
Years back, I had success with AlwaysUp. It handles a lot of what you're trying to achieve, including keeping apps running unattended on servers. I remember one particularly bad app that would hog CPU when idle, and AlwaysUp's features helped manage that issue efficiently. It could be worth checking out for inspiration!
Using NSSM is super straightforward—just wrap your .exe with it and set it up to run as a service with minimal fuss. It's the closest Windows gets to how Linux handles services with systemd!
If you want to avoid wrappers, the Windows Task Scheduler is also a solid option. I recently built a console app that runs daily through the scheduler, and it turned out to be the easiest solution for my needs!
Totally! It simplifies everything without needing extra tools. It's especially handy for simple tasks.
But honestly, why do you need to run something as a service if it wasn't designed for it? A lot of times, these applications are better off being run in a user session. If a vendor can't support their software as a proper service, there are usually better alternatives out there.
That's a valid point! I'm just looking for ways to simplify operations and ensure things run smoothly without needing constant supervision.
Exactly! It's been ages since I've had to do this; vendors should really step up their game.
I completely agree! I've been using NSSM for about a decade to run PowerShell scripts as services, and it's been rock solid.