0

I need to distribute some app to all our stations without users having the ability to close the app.

The app jumps on users' screen and notifies them to restart the computer, and I don't want users to be able to close this app through task manager.

Our users all have local admin privileges, and I couldn't find a way to stop them from closing the app.

So I thought to create a service that runs this app and define the service as unstoppable and uninstallable.

I created the service in this way:

sc create "PU-Restart" binPath= "C:\PURrestart\PURrestart.exe" 

But when I start the service, I get this error:

Windows could not start the PU-Restart service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion. 

I would welcome any help find a solution to it. Thanks Haim

5
  • 3
    This looks a lot like the XY problem. What is the exact thing you want to achieve? Your method as you describe it doesn't look like a good way forward. Commented Sep 4, 2019 at 9:45
  • 2
    if the users have local admin privileges they can stop the service. Commented Sep 4, 2019 at 10:07
  • 4
    The answer to any question beginning "how do i stop local admin users from..." is "you can't". :-) Commented Sep 4, 2019 at 10:48
  • ... but you could monitor the app remotely and get an alert if it is killed so you know who to go yell at. Commented Sep 6, 2019 at 23:43
  • You can not stop admins from doing anything. Commented Sep 12, 2019 at 13:20

1 Answer 1

1

Unfortunately windows doesn't give you the ability/authority to interact with users directly. Services after all do not have interfaces and run on the background even when the user is logged out.

https://stackify.com/what-are-windows-services/

Also about the error, its probably because you didn't implement the Windows Services Control Manager's states (start, stop, pause etc.). They act like event handlers when someone starts stops or pauses a service. By default, the Service Control Manager will wait 30 seconds for a service to respond (basically for the start handler) and if the service hasn't responded then it will throw the error you describe.

1
  • It is possible for services to interact with the user indirectly, though, e.g., by calling WTSSendMessage as per this post. Can't stop the local admin from killing the service, though. Commented Sep 6, 2019 at 23:42

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.