Open the process list in your system monitor of choice, right click, signal, sigkill.

You can also open a monitor and use top or any variant to detect the process number and manually kill -KILL number

I dunno; I sadly can’t use Wayland yet bc I have Nvidia

At that point you can just hard restart as well. Most motherboards accept 10 to 15 seconds of power button as “my OS is fucked please help” and restart the machine for you.

Wait until you find out about taskill /F /IM explore.exe

I haven’t seen that in a while. When you see that it means either that the service didn’t handle the terminate signal correctly or that is is busy doing something. (Sometimes both)

It’s awesome Linux can STOP and CONT processes ngl

Taskkill /f is reasonably close to sudo kill -9

Hitting the X in Windows and hitting the X in Linux both cause the application to start a save yourself routine. From the OS standpoint they’re not far off.

The problem is we have a lot of confirmation bias in windows because every time we want to close an application that’s not working, that save yourself call has to sit around for a hellaciously long time out followed by a telemetry call so that Microsoft can track that it happened.

It’s pretty rare that Linux apps don’t just close.

League of Legends captures and discards the ALT-F4 keystroke combination.

Microsoft trusts app developers to use Microsoft’s standards (such as terminating the process when a close message is received) and they shouldn’t. App developers like Riot have taken advantage of this trust and tuned their apps to act differently than expected, and include code which makes the app minimize to the system tray instead, or force the user to answer questions (“Are you SURE you want to close?”), or do nothing at all.

It should be punishable by death.

You can easily make a program unkillable (or to be more precise untermable) on Linux. Here’s a simple bash script that will do that.

#!/bin/bash                                                                                                     function finish {
  while true
  do                                                              
    echo "Can't kill me."                                   
    sleep 10                                        
  done                                            
}                                                                                                               trap finish EXIT                                        
trap finish TERM                                        
trap finish INT                                                                                                 

while true                                              
do                                                              
  echo "Still alive."                                     
  sleep 10                                        
done

I’ve seen that on Linux as well. Funnily enough also with faulty file systems. I think NFS with spotty wifi for one.

Oh, and once with a dying RAID controller. That was a pain in the ass. At that point I swore to only ever do RAID in software.

Linux has that issue too. A process in an uninterruptible blocking syscall stays until that syscall finishes, which can be never if something weird’s going on.

I’ve heard those quick keys a thousand times but my brain has determined that it is not necessary information for me to retain.

That’s what I don’t get about what they said above. If the Windows desktop freezes up, Task Manager won’t open either (happened to me quite some times over the years - less so since they moved to the NT kernel though). What you mentioned always works short of kernel panic.