{"id":13011,"date":"2025-07-07T04:15:15","date_gmt":"2025-07-07T11:15:15","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=13011"},"modified":"2025-07-07T04:15:15","modified_gmt":"2025-07-07T11:15:15","slug":"regular-users-restart-windows-service","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/windows-services\/regular-users-restart-windows-service\/","title":{"rendered":"Q&A: How do I Let Regular Users Monitor and Restart a Windows Service?"},"content":{"rendered":"
\"How<\/div>\n
\n  I see that you guys have a lot of tools for Windows Services. Maybe you can help me solve this problem.<\/p>\n

We have an important service and only Admins are allowed to use it. If there’s an issue and the service needs to be restarted, regular users who aren’t in the Administrators group have to put in a ticket.<\/p>\n

To reduce the support calls, we’d like to give certain regular users the capability to see if the service is running and restart it if it isn’t. What’s the best way to do that?<\/p>\n

— Alex<\/p>\n<\/div>\n

Hi Alex, thanks for reaching out. We can definitely help you tackle this issue with our free Windows Service utilities. It should only take you a few minutes to implement the following two-step process and you’ll be good to go.<\/p>\n

\n

Step 1: Use Service Security Editor to allow the user to start or stop the Windows Service<\/h2>\n

By default, only administrators can manage a Windows Service. And more often than not, regular users are summarily rejected with an “access denied” error when they try to start or stop the service because they don’t have the necessary rights. That’s the first problem we have to fix.<\/p>\n

For example, we have a regular user named “Hazel Jones” on our system. Because she’s not in the Administrators group, her attempts to stop the Print Spooler service using the NET command are consistently rebuffed:<\/p>\n

\"Hazel<\/a><\/div>\n

Your team’s probably in the same situation as Hazel.<\/p>\n

So here’s what you should do to allow your users to control your Windows Service. We’ll use Hazel and the Spooler service to illustrate:<\/p>\n

    \n
  1. \n

    Download our free Service Security Editor<\/a> program.<\/p>\n<\/li>\n

  2. \n

    Start Service Security Editor.<\/p>\n<\/li>\n

  3. \n

    Select your Windows Service from the list:<\/p>\n

  4. \n

    Click the Open<\/b> button.<\/p>\n<\/li>\n

  5. \n

    As you can see in the Service Security Settings<\/b> window that comes up, only Administrators have full control over the service. For example, Hazel was nowhere to be found in our list.<\/p>\n

    Click the Add<\/b> button to add the non-admin account:<\/p>\n

  6. \n

    Enter the account name and click OK<\/b>:<\/p>\n

  7. \n

    Back in the Service Security Settings<\/b> window, select the newly added user in the top panel. Afterwards, ensure that the user has all the rights you would like to give them in the lower panel.<\/p>\n

    For example, we granted Hazel full permissions over Spooler. She’ll be able to start, stop or restart the service whenever she likes:<\/p>\n

  8. \n

    Click OK<\/b> to save your changes. And exit Service Security Editor since we’re done with that program.<\/p>\n<\/li>\n<\/ol>\n

    At this point, your non-admin user should be able to control your Windows Service. The NET command should succeed now, as it did here for Hazel:<\/p>\n

    \"Hazel<\/a><\/div>\n

    But even though your user can now stop the service, that alone won’t make it easy for them to do so! The truth is that very few folks are comfortable invoking the NET command from a prompt, and it’s almost as painful to explain how to drive the Services application. We can do better — and that’s the focus of the next step.<\/p>\n

    \n

    Step 2: Have your user install ServiceTray, to make it easy to work with the Windows Service<\/h2>\n

    In this second part of the solution, your non-admin user will install another of our popular, free programs, ServiceTray<\/a>. This helpful tool will make it obvious when the service is running — and allow the user to easily stop, start or restart the service whenever there’s trouble.<\/p>\n

    To set this up, your regular user should:<\/p>\n

      \n
    1. \n

      Download and install ServiceTray<\/a>. It should only take a couple of minutes to breeze through the straightforward process.<\/p>\n<\/li>\n

    2. \n

      Start ServiceTray.<\/p>\n<\/li>\n

    3. \n

      In the window that comes up, choose the Windows Service from the drop-down at the top. For example, Hazel selected the Print Spooler service here:<\/p>\n

    4. \n

      Next, click the Save<\/b> button. That will create a shortcut in your Windows Startup Folder<\/a> — the location holding the applications that Windows launches whenever you log in:<\/p>\n

    5. \n

      Click the Done<\/b> button to close ServiceTray.<\/p>\n<\/li>\n<\/ol>\n

      The next time the user logs in, Windows will start ServiceTray automatically. After a few seconds, a new icon will show up in the “tray area” on the right of the Windows taskbar:<\/p>\n

      \"DESCRIPTION\"<\/a><\/div>\n

      If the icon doesn’t show up in the tray area, they may need to change their Windows taskbar settings to show the icon<\/a>. Hazel had to make that change:<\/p>\n

      \"Show<\/a><\/div>\n

      Using ServiceTray<\/h3>\n

      A quick look at the tray icon will tell the user if the service is running or not. The color of the icon will be:<\/p>\n