Windows audio service stuck on stopping

How to manually forcetotally soptimal a hung Windows service process that hangs at “Stopping” or “Not responding”? Many Windows administrators have challenged a trouble, when they attempt to soptimal (restart) a organization, but it gets stuck to the Stopping standing. You won’t be able to speak this organization from the Service management consingle (services.msc), considering that all manage buttons for this organization come to be inenergetic. The most basic method is to restart Windows, but it is not always acceptable. Let’s take into consideration an alternate method, which permits to forcecompletely kill a stuck Windows service or process without system reboot.

You watching: Windows audio service stuck on stopping


*

If within 30 seconds after trying to stop the business, it doesn’t stop, Windows display screens this message:


Windows Could not stop the xxxxxx service on Local ComputerError 1053: The company did not respond in a timely fashion.

If you try to speak such a business from the command also prompt: net sheight wuauserv, a message appears:

The organization is starting or protecting against. Please try aacquire letter.

*

Contents:

How to Terminate a Hung Windows Service Process Using TaskKill?

The easiest way to speak a stuck organization is to usage taskkill. First of all, you should uncover the PID (procedure identifier) of the business. As an example, let’s take Windows Update service, its mechanism name is wuauserv (you can inspect the name in the company properties in the services.msc console).


Quite often this trouble happens with the Windows Modules Installer organization at server reboot, particularly after installing updays on Windows Server 2012 R2 / 2008 R2.

See more: How To Unblock Someone On Tumblr App, Blocking Users


Important. Be attentive. A required shutdvery own of crucial Windows solutions can result in BSOD or an unmeant mechanism rebegin.

Run this command in the elevated command also prompt (it is important, or accessibility denied error will appear):sc queryex wuauservIn our instance the PID of the wuauserv company is 816.To pressure speak a hung procedure through the PID 816, run the command:

taskkill /PID 816 /F

*


SUCCESS: The procedure with PID 816 has been terminated.

You have the right to speak a hung business more elegantly without checking the business PID manually. The taskkill energy has the /FI choice, which permits you to usage a filter to select the important services or procedures. You deserve to shutdown a particular organization with the command:

taskkill /F /FI "SERVICES eq wuauserv"

Or you have the right to skip the business name at all and also killing all solutions in a hung state with the command:

taskkill /F /FI "status eq not responding"

After this, the service that hangs in the Stopping condition need to stop.

PowerShell: Stop Windows Service through Stopping Status

You can also use PowerShell to force the business to speak. Using the adhering to command you have the right to get a list of services in the Stopping state:

Get-WmiObject -Class win32_organization | Where-Object $_.state -eq "speak pending"

*

The Stop-Process cmdlet allows to terminate the processes of all uncovered services. Let’s incorporate both operations right into a loop and also get a manuscript that immediately terminates all the procedures of the stuck services:

$Services = Get-WmiObject -Class win32_business -Filter "state = "soptimal pending""if ($Services) foreach ($company in $Services) try Stop-Process -Id $organization.processid -Force -PassThru -ErrorAction Stopcapture Write-Warning -Message " Error. Error details: $_.Exception.Message"else Write-Output "No services via "Stopping".status"

*

Identify a Hang Process Using Resmon

You have the right to detect the process that caused the service freeze utilizing the resmon (Reresource Monitor).

In the Resource Monitor window, go to the CPU tab and also find the hung business process;In the new home window, you will certainly the majority of likely see that your procedure is waiting for an additional procedure. End the procedure. If you are waiting for the svchold.exe or one more system procedure, you don’t must terminate it. Try to analyze the wait chain for this process. Find the PID of the procedure that your svchold.exe is waiting for and kill it.

See more: 0X80070490 Xbox One Error Code 0X80070490 Xbox One Error Code

Process Explorer: Killing a Hung Process Running in SYSTEM Context

Even the local administrator cannot terminate some processes that run in the SYSTEM context. The reality is that the admin account sindicate haven’t pergoals on some processes or solutions. To soptimal such a process (services), you need to approve perobjectives to the business (process) to the local Administrators group, and then terminate them. To do this, we will certainly need 2 little tools: psexec.exe and also ProcessExplorer (obtainable on the Microsoft website).

In the Process Explorer procedure list, find the stuck company process and open up its properties;