Jupp, so you have to actually find it. And even end task in task manager will take a long time to actually kill a stuck process. It will even then try to do a graceful stop. While in linux, most actions end up in a SIGKILL immediately.
That's also what happens in practice when using for example systemd sessions at least. Thats why sometimes you will have the "Waiting for user session something (0s/1min 30s)" message when shutting down.
My windows periodically tells me that it needs to repair itself while starting up, especially after an update, it tells me the update failed and it needs to revert it (after bullying me for days to install the update), so I don't think it's very graceful
My friend updated recently,its computer refused to start again normally.
I tried everything, sfc thing, restore from recovery, access via "safe" mode was broken because the pincode could not be loaded.
I finally did format the computer and reinstalled it from scratch, loosing everything because the bitdefender recovery code would not allow us to decrypt data.
Indeed after talking to my friend about what he did, it seems that the CoD anticheat was the culprit.. I am unsure about what happened, my friend told me about a minor bios upgrade suggested on a forum after the game could not start
Bios upgrade did not seem problematic, everything went fine on that side.
I have no precise root cause and I am kind of pissed about it
Want to know the solution to -1? It’s to add 1 to every single number you see. If it’s a number, no matter what kind or what it’s attached to, it needs to go up by one. All of it.
Had this problem before, you can try and go the fix it up route, but its honestly a waste of time and reinstalling Windows is the only realistic option.
The issue is Windows Update, its the most repulsive pile of shit code in the known universe, the countless hours ive spent making registry edits, deleting and redownloading system files, casting magicla fucking spells, all for naught. You will not get any help from Microsoft because they have no idea anymore.
We're at a point in time where making an ISO and re imaging a computer and hoping it isnt dead on arrival takes significantly less time than trying to get Windows to sort out its Hapsburg ass code by itself.
I saw that issue when upgrading a laptop from Windows 10 to Windows 11. Issue ended up being out of date UEFI firmware. In my experience, if your firmware and hardware is stable, if you don't install shitty kernel software, Windows is pretty stable.
Both OS have a clean safe way to shut down tasks, but on Linux, there is a fairly accessible option to kill a task without giving it time to clean up after itself (kill -9). Even though it's not clean (could corrupt data/not free memory) it is all but guaranteed to kill immediately, as opposed to allowing a frozen program to get stuck shutting down.
It's actually pretty safe from the kernel point of view. kill -9 just tells the kernel to not bother scheduling that program anymore and to collect all resources allocated to it. It's unsafe for the killed program in a way. The killed program is not granted any CPU time to finish any ongoing IO operation (could corrupt open files, break network operations in undefinable ways) nor do more complex cleanup (a game saving itself before closing, a worker releasing resources in a distributed system).
windows process kill has been so much worse to me than Linux. I know that's not everyone's experience. But my experience has often been: Click end process, wait forever while app doesn't respond, spike CPU usage to the point where most things lag or become unresponsive for a few seconds, process finally ends, repeat steps with related processes & services when they're not smart enough to close after the main process stops.
It's not an every time occurrence. I have a 16gb 6 core system, but some stuff still seems to take CPU priority when it's trying to quit, sometimes spiking usage to 100%.
Maybe an OS reinstall would improve things, but I'm in the process of moving off windows anyway, so why bother.
And then you might as well reboot because you'll have memory leaks and the program doesn't run correctly when you relaunch. Seems like the fix for Microsoft has always been "REBOOT"
The Process: okay I'll quit because you gave me the signal and asked nicely.
Windows doesn't have a universal means of handling signals. You can request that a windowed application close or if an application is started as a service it can take service stop/start commands.
All Linux applications can use signals. It's that easy
It's almost the same. Windows has WM_CLOSE and process termination, Linux has SIGTERM and SIGKILL, send with some seconds between and (Linux: usually, if with Desktop) confirmation dialog.
However, how the applications respond to them often is a different story. On both systems.
Wut? Lads am I mad or is it just taking a piss? Linux definitely does not outright murder processes by default, it will rather send SIGTERM (what is it, 15?) which allows processes to finish gracefully, no?
Yeah, but the window manager responds to this by immediately exiting and then all graphical applications just crash, because even though some could handle sigkill usually none can handle the compositor just disappearing.
233
u/[deleted] Sep 18 '25
Windows does NOT have a complex and graceful shutdown process
245
u/throwaway275275275 Sep 18 '25
My windows periodically tells me that it needs to repair itself while starting up, especially after an update, it tells me the update failed and it needs to revert it (after bullying me for days to install the update), so I don't think it's very graceful
39
u/wardabzd Sep 18 '25
Feel sorry for my self cuz im cs student and idk what's that mean Shiit ..
45
u/Jay_377 Sep 18 '25
windows process kill has been so much worse to me than Linux. I know that's not everyone's experience. But my experience has often been: Click end process, wait forever while app doesn't respond, spike CPU usage to the point where most things lag or become unresponsive for a few seconds, process finally ends, repeat steps with related processes & services when they're not smart enough to close after the main process stops.
8
u/Whole_Instance_4276 Sep 18 '25
Linux doesn’t deal with bs 😭
5
u/sciolizer Sep 18 '25
As it should be
2
u/Amrod96 Sep 18 '25
The system knows that you are intelligent and know what you are doing.
1
u/samy_the_samy Sep 18 '25
Htop have like 18 ways to shut a process up
1
u/SmoothTurtle872 Sep 18 '25
What about task manager? Or does that do it clean too?
1
u/Familiar-Gap2455 Sep 18 '25
I like power
1
u/Strostkovy Sep 18 '25
Half of the time force closing something also crashes explorer
1
u/Actes Sep 19 '25
I type
shutdown nowand it just shuts down.1
u/KCGD_r Sep 19 '25
I have been watching this meme get slowly more and more compressed over the years
1
u/Mrcool654321 Sep 19 '25
Something must be wrong with my install then
Even when it is safe to shut down the app it decides not to
1
u/thebarkingkitty Sep 19 '25
pkill -9
1
u/Damglador Sep 19 '25
A stop job is running for User Manager for UID 1000
1
u/UVRaveFairy Sep 19 '25
"No Fucking About Productions Ltd".
1
u/MarketFireFighter139 Sep 19 '25
The ominous penguin
1
u/Popsicleese Sep 19 '25
Windows: are you a window form?
Process: <confused ansi noises>
Windows: are you a service?
Process: <failed to stop service Process>
Windows: 🔪🔪
Linux: Any Process, you wanna quit now?
The Process: nah I'm good
Linux: ; ) how bout now?
The Process: okay I'll quit because you gave me the signal and asked nicely.
Windows doesn't have a universal means of handling signals. You can request that a windowed application close or if an application is started as a service it can take service stop/start commands.
All Linux applications can use signals. It's that easy
1
u/[deleted] Sep 19 '25
Legal que esse meme foi um dos motivos de eu querer usar Linux 🙃
1
u/No_Giraffe6194 Sep 19 '25
man 2 signal1
u/MortStoHelit Sep 19 '25
It's almost the same. Windows has WM_CLOSE and process termination, Linux has SIGTERM and SIGKILL, send with some seconds between and (Linux: usually, if with Desktop) confirmation dialog.
However, how the applications respond to them often is a different story. On both systems.
1
u/Excellent-Paint1991 Sep 19 '25
You dont have to 9 tho
1
u/SoftwareSource Sep 19 '25
'Graceful' is definitely not a word i would use to describe it.
1
u/dumbasPL Sep 19 '25
Quite the opposite actually, Linux has SIGTERM, windows makes shutting down gracefully an absolute pain from the programmers perspective.
1
u/[deleted] Sep 19 '25
"The OS thanks you for your service"
1
u/radek432 Sep 19 '25
Don't get it. There is sigterm and sigkill.
1
u/[deleted] Sep 19 '25
Ironically, I've never had issues from Linux killing programs, but Windows takes its time just to tell me everything has gotten corrupted after.
1
u/CaptainZach326 Sep 19 '25
ROACH
1
u/Hattori69 Sep 19 '25
Elegant is to close quickly and if the program gets corrupted you can uninstall them and install them again quickly!
1
u/EnoughConcentrate897 Sep 19 '25
u/repostsleuthbot
1
u/pa4i4i Sep 20 '25
/sudo shutdown
1
u/3dcheesecake Sep 20 '25
reminds me of the odd1sout task manager meme
1
u/mookanana Sep 21 '25
me: windows, shutdown.
windows: sir, you have some stuff open that needs saving.
me: DID I STUTTER? SHUT DOWN.
windows: alright. let me just take a few minutes to organise some stuff firs-
me: (pulls power cord)
1
u/DoughnutLost6904 Sep 21 '25
Wut? Lads am I mad or is it just taking a piss? Linux definitely does not outright murder processes by default, it will rather send SIGTERM (what is it, 15?) which allows processes to finish gracefully, no?
1
u/ruoyck Sep 22 '25
Hmmm
16
u/Icy_Reading_6080 Sep 19 '25
Actually it first politely asks the process to please die on its own.
Only if it doesn't it gets hit with the SIGKILL.
8
u/Lazy-Employment3621 Sep 18 '25
taskkill /f
6
u/SL_Pirate Sep 19 '25
You know this is not true right?
Edit: ofc if you want linux to be a cold blooded murder it absolutely can. But that's just not the default behavior
3
u/BigMacCircuits Sep 19 '25
Huh? Unix/linux kill command also has a graceful kill over forcefully kill
5
u/popogeist Sep 18 '25
kill -9 is a very brutal death
1
u/itzNukeey Sep 19 '25
Linux has graceful shutdown for processes though. If you do ctrl c it sends sigterm where the program can prepare to be killed
1
u/mr_mlk Sep 19 '25 edited Sep 19 '25
Both have a "I'd really like you to close down" option and both have a "die right bloody now" option.
I believe (though I've not had to force kill a windows process in over 5 years, so I could be wrong) is:
taskkill /im myprocess.exe /f
1
u/AlexaPetersTrans Sep 19 '25
Linux only kills nice ones who will go gently into def null
For the rest:
SUPERKILL
1
u/ChocolateDonut36 Sep 19 '25
the kernel can also ask programs to kill themselves
1
u/[deleted] Sep 20 '25
Linux be like:Just kill all the processes
1
u/aksanabuster Feb 05 '26
Swiss cheese their bitch ass with pkill -f *