I swear it's just in my head, but when my Windows computer hangs or freezes, I find that opening Task Manager (by either Ctrl-Alt-Del > Task Manager or Ctrl-Shift-Esc) sometimes seems to jog the computer and cause whenever program wasn't responding to start working again, or closes the window I've been furiously clicking X on. Am I making this up, or does simply opening Task Manager actually do something?

  • 7
    It could actually be the opposite: Task Manager cannot open until the system starts responding normally. Jan 22, 2012 at 19:37
  • 1
    @Sonic42 I am experiencing exactly the same behavior on every windows machine I ever owned... Even when some program hangs for minutes, opening the task manager would trigger the continuation of the process... Very strange. It's just in our head I think... ^_^ I am not statistfied with the accepted answer :-/ This can't be the reason, since my windows is running on an SSD.
    – ˈvɔlə
    Jul 5, 2019 at 15:06

1 Answer 1


I could see that happening if you were getting slow downs due to disk problems (as opening it may change how the disk is being accessed, making it skip or release a block it's fighting to use). It could also cause something eating all CPU to release some of it long enough to release a lock state. But neither of these scenarios would necessarily be Task Manager-specific.

One thing 'special' about Task Manager is that it's always launched with a "High" priority flag, giving it higher priority for CPU usage than other software (usually running with "Normal" priority). This increases the chance that it may rob enough resources that it may cause the locked program to unlock (by interrupting a file-system race condition, or thread spinlock for example).

A lot of it IS probably in your head as well. Sometimes Task Manager won't open until the pause has passed, making it SEEM like the Task Manager caused things to advance, when in reality it was just waiting in turn. Also, often things that are "not responding" for a long time actually finish what they were doing in the time it takes between you giving up waiting, and trying to kill the process with Task Manager. :)

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .