Home/ Questions/Q 8565149
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T17:21:32+00:00

We’re using the stop-service cmdlet to kill a few services on our boxes. Most

  • 0

We’re using the stop-service cmdlet to kill a few services on our boxes. Most of the time it works great, however we have one or two services (who doesn’t?) that occasionally don’t play nice.

In this instance one of the services in question will remain in the stopping state, and the cmdlet puts this out to the console over and over:

[08:49:21]WARNING: Waiting for service 'MisbehavingService (MisbehavingService)' to finish 
[08:49:21]stopping...
[08:49:23]WARNING: Waiting for service 'MisbehavingService (MisbehavingService)' to finish 
[08:49:23]stopping... 
[08:49:25]WARNING: Waiting for service 'MisbehavingService (MisbehavingService)' to finish 
[08:49:25]stopping...

Eventually we have to kill the service in the task manager, and our script then continues.

Is there a way to have the stop-service cmdlet give up or timeout after a certain point? I figure we can check afterward and if the service is still running, use the kill-process cmdlet to provide a final chop.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There is no timeout option for stop-service, but if there are dependent services, you may need to use -force.

    Services can define a wait hint (which specifies a timeout) when they start, but the timeout is controlled by the service. Any service control requests (start, stop, pause, resume) go through the service control manager (SCM) and will respect the wait hint for each service. If the wait hint is exceeded, the operation will fail and an error be returned.

    You could use invoke-command to run Stop-Service as a job and check it periodically. If it hasn’t completed, you could use Stop-Process to kill the process and continue.

    • 0