Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Skype got stuck, and Windows was unable to kill the process even when the UI had disappeared. I had to restart the computer to get Skype again working.

Running as administrator:

C:\Windows\system32>tasklist | find "Skype"
Skype.exe                     2708 Console                    1     92,328 K

C:\Windows\system32>taskkill.exe /pid 2708 /F /T
SUCCESS: The process with PID 2708 has been terminated.

C:\Windows\system32>tasklist | find "Skype"
Skype.exe                     2708 Console                    1     92,328 K

How can this be even possible?

Cheers.

share|improve this question
1  
I'm not sure what would cause this, but in the future you can use Process Explorer to kill it. Never fails for me even if Task Manager does. –  Oliver G Jul 24 '12 at 9:48
    
I don't know why this happens, maybe some system-wide lock or something. But this happened to me several times. The application was basically "unkillable", no matter what utility I tried. Even Process Explorer failed. Restart was the only way out. –  Shiki Jul 24 '12 at 11:05
2  
Skype is not shutting down. Looks like the problem with Skype is pervading in all platforms. Find the same problem in Ubuntu. –  vulcan raven Jul 24 '12 at 12:24
add comment

3 Answers 3

Try again Taskkill with these switches:

taskkill.exe /f /fi "status eq not responding"

You may also look in HKU\Control Panel\Desktop and change the value of WaitToKillAppTimeout from the default value of 16000 (milliseconds) to a lower value (but not 0!) and HungAppTimeout from the default value of 4000 (milliseconds) to a lower value (but not 0).

share|improve this answer
    
Oups! Thank you for the correction Gareth! :) –  climenole Jul 25 '12 at 22:43
add comment

Unkillable Skype is caused by one of the Skype threads trying to close a handle to the Ancillary Function Driver (/devices/AFD).

This close call hangs and never returns. When you try to kill the process, the I/O request gets cancelled, but the cancellation also hangs. The process cannot quit until its threads return, and the thread cannot return until the cancellation completes, hence process termination is impossible.

You can confirm this with a kernel mode debugger. See this TechNet blog article for details.

You need to use a remote debugger, because Skype causes some unhandled exceptions which will freeze windows otherwise.

The probable cause is some bug in some network filter driver.

share|improve this answer
add comment

Doesn't seem to be issue in my case either.

c:\Windows\System32>tasklist | find "Skype"
Skype.exe                     8380 Console                    1    133,628 K

c:\Windows\System32>taskkill /pid 8380 /f /t
SUCCESS: The process with PID 10296 (child process of PID 8380) has been termina
ted.
SUCCESS: The process with PID 8380 (child process of PID 3616) has been terminat
ed.

c:\Windows\System32>tasklist | find "Skype"

c:\Windows\System32>

However, in your case, it appears to me that the process' UI-thread is locked in closing state while the SUCCESS message was displayed.

Solution:

If that happen, click on (show hidden icons) arrow on taskbar, you will see that the app icon is still there. Hover over icon and you will see it disappear! Run the command again and you will not find the process again, which indicates that process was closing, unusable and inactive.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.