Is there a Windows equivalent to the Linux "xkill" command?

Hi,

You have a few options:

1. PsKill - http://technet.microsoft.com/en-us/sysinternals/bb896683.aspx

2. taskkill /im ProcessNameHere.exe /f

-- /f parameter implies 'force'.

Regards,

Patrick

Arnold

In Windows 7 use Ctrl+Shift+Esc and not Ctrl+Alt+Del. It's quicker.

Your system may be holding on to Standby memory and not releasing it to Free memory. You can force release by restarting your computer but often this is not very convenient. Another way to force the release of Standby memory is available using RAM Map (freeware from Microsoft):
http://technet.microsoft.com/en-gb/sysinternals/ff700229.aspx

Download and install, and create a shortcut on your Desktop to RAMMap and / or pin to your Taskbar. When you sense the system is becoming unresponsive use Ctrl+Shift+Esc to access Task Manager. Click the Performance tab and the Resource Monitor button. Click the Memory tab and check whether Free is near to Zero or is Zero. If it is, open RAMMap, click Empty on the Menu bar and Empty Standby list. This action instantly restores Free memory.

The procedure using RAMMap is an effective workaround but the true solution lies in discovering the source of the problem. Knowing the source you may be able to resolve the problem by contacting the provider of the software and / or updating the software.

Suggest you to try "win-xkill", a windows port of linux "xkill".

https://bitbucket.org/sta-ger/win-xkill
https://chocolatey.org/packages/win-xkill

Chears

I'm not sure why your reply was marked as an answer.  The solutions you suggested, and those suggested by other commenters, all failed to work with the same speed or efficiency as the UNIX version of xkill.  Even the version of xkill that's ported for windows exhibited freeze-ups of 8 to 10 seconds rather than the instant process kill that I was hoping for.  

Apparently there's nothing available for windows that has the same effectiveness as xkill. 

Windows xKill

Many of you miss the point that it's a kill version with graphical interface (historically x like Unix/OpenVMS x Window but the name remained unchanged for later GUIs). It is of use if one does NOT have the PID(s) of the process(es) belonging to a certain window.

Eg. you have 4 IE sessions, each in an own process and one crashes. You see visually which window has crashed, but you have no idea which of the 4 instances to shut down. In this case a graphical tool like xKill comes to the rescue.

Chilli