kill windows service stuck at stopping

Posted on 14/06/2020 by Deviprasad Panda

Every infracture admin need to know the steps to force stop or kill windows service stuck at stopping by pid using taskkill or powershell. Think about a situation, you are trying to stop a windows service but its stuck at stopping status. Means service stopping hung and not responding. In this case we need to force kill windows service either by using taskkill in command line (cmd) or by powershell. Follow the step by step commands to apply in cmd for force stop service windows server.

Advertisements

Run command prompt as an administrator and type taskkill help command as below. That will display parameter list like /S, /U, /P, /FI, /PID, /IM, /T, /F, /? and why these are used. You will find these parameters in the commands below.

Advertisements

kill windows service command line

taskkill /?

kill windows service using taskkill windows command line

Advertisements

kill process id using taskkill windows command line

Advertisements

First step is to identify the “Service name” of windows service stuck at stopping. Let’s say windows update service stuck at stopping, then right click on the service and click on properties will show you the service name “wuauserv”. Alterenatively, you can run powershell command “Get-Service” to get windows service details. Run the below command in command prompt to get the PID of service.

sc queryex <service name>
sc queryex wuauserv

Advertisements

You can check the PID in “Task manager” under the the tab “Services”.

Advertisements

Next step is to kill windows service PID running below cmd in command prompt.

taskkill /f /pid [PID]
taskkill /f /pid 996

Advertisements

You will find the service is stopped after applying the command above. You can disable the serivce else apply the state as per your requirement.

windows update service stopped how to disable

Advertisements

You can kill processes from command prompt without knowing the PID by running the below command.

taskkill /F /FI "SERVICES eq wuauserv"

taskkill /F /FI "SERVICES eq wuauserv" — taskkill /F /FI “SERVICES eq wuauserv”

Advertisements

You can force stop a service running with particular user id using below cmd.

taskkill /F /FI "USERNAME eq Deviprasad"

cmd to task kill all windows services not respnding running as below.

taskkill /F /FI "status eq not responding"

Advertisements

You can kill services consuming more then a limit of memory usage following the command below.

taskkill /FI "memusage gt value"
taskkill /FI "memusage gt 220600"

Advertisements

Run the cmd as below to get list of tasks running in server.

tasklist

Advertisements

we can run the below cmd to kill task running in the server.

taskkill /F /IM taskmgr.exe

Advertisements

End task using powershell

We can use below powershell commands to kill windows service.

Stop-Process -ID ProcessID - Force
Stop-Process -ID 6196 - Force

Stop-Process -Name ProcessName -Force
Stop-Process -Name iexplorer -Force

Advertisements

powershell command to force kill services not responding.

Get-WmiObject -Class win32_service | Where-Object {$_.state -eq 'stop pending'}

Advertisements

Watch the video to get details step by step for better understanding.

Advertisements

Delete cbs.log file its growing large

Posted on 19/02/2017 by Deviprasad Panda

Delete cbs.log file its growing large

This post describes about cbs.log file which is growing large and how you can delete. System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. Run the System File Checker tool (SFC.exe) to scan your system files and to repair missing or corrupted system files. CBS.Log file is generated by the Microsoft Windows Resource Checker (SFC.exe).

The SFC.exe program writes the details of each verification operation and of each repair operation to the CBS.log file. The CBS.persist.log is generated when the CBS gets to be around 50 meg in size. CBS.log is copied to cbs.persist.log and a new cbs.log file is started.

Solution 1 :

you can try compressing the file:

Right click on the CBS.log file.
Click on Properties.
On the General tab, click Advanced.
Check “Compress contents to save disk space” and click on OK.

Solution 2 :

Another Workaround is to turn off unnecessary services that may calling into CBS;

To disable CBS log, you may change registry key in

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Component
Based Servicing] EnableLog=dword:00000000

In addition,also recommended to run sfc/scannow to check the health of system files.

Solution 3 :

If you are sure your system is running fine, you can delete this file. SFC.exe will create a new one, next time it is run.

Please follow below method to delete:

Stop TrustedInstaller.exe (Windows Module Installer) in Taskmanager Services tab. Additionally if you cannot, open the Taskmanager Processes tab and End Task the same process.
Delete or move all the .log files in the C:\Windows\Logs\CBS directory, you can delete the .persist and .cab files as well.
Start Windows Module Installer service (TrustedInstaller.exe) again