Don't worry - It is just another untested theory.
Sick Freak says:
![Error Error](http://pic002.cnblogs.com/images/2012/409191/2012080622391157.jpg)
Stop and Start a service via batch or cmd file? Ask Question. (stop then start), the stop returns immediately, the start then fails because the service isn't stopped. Net stop/start returns after the action is complete, so doesn't have this problem. Tell you whether they have succeeded or failed pretty clearly. Simple library that allows one to host dot net core application as windows services. Perfect solution to power micro-services architecture. Join GitHub today. Run the service with action:start and it will start the service. Run the service with action:stop and it will stop the service.
If the service has a space in its name, like Print Spooler, make sure to put quotes around the service name.
First of all, there is no Service called 'Print Spooler' - it is just 'Spooler'.
Followed by:
Once the batch file is created and you've tested it, just go to your scheduled tasks and add the batch file.
Of course, you can also do this via a script or other methods if you'd like.
Of course, you can also do this via a script or other methods if you'd like.
Of course Sick Freak has not tested that or described how to 'add the batch file' to Scheduled Tasks or use a script or other methods if I like. It would seem to be useful to know how to do that, huh?
And even if you were to come up with a Scheduled Task to restart stopped Services, that would not be fixing the problem - it would be fixing the symptom of the problem. The problem is Services are stopping.
If Services are stopping and they should not be stopping it would make more sense to figure out why they are stopping and fix the problem and not come up with some convoluted way to address the symptom of the problem.