![]() Does anyone have any insight into how to solve this problem? Create a tool that can kill a locked process like that? It happens all too often and it almost always results in having to restart the computer for the dumbest reasons. I don't code desktop software so I don't think I can be the one to make that program. But there's no solution and no tool to fix it. So, now there's a topic about it somewhere on the internet (should be able to be identified by my use of the "Wait:Executive" term.). However, that's hit and miss - and if you miss, you're stuck with a computer that's locked at the "Preparing to stand by" screen and you can't do a **** thing about it - it's hopelessly frozen and you can't even save your work (I even forgot what I lost, but I know I had a full taskbar.).Ī thorough Google reveals that no such tool exists, and that the problem itself hasn't even been identified. Sometimes I can solve these by going into Standby, and resuming will kill the process by unlocking the locked I/O, which allows it to catch up to that "DIE ALREADY!" request I gave it much earlier. when you can't even kill them! It also doesn't respond to closing handles, and especially not to killing the process (which it doesn't). The thread can't be killed - you can try and try and try, but it just ignores your "kill" requests. by which point, killing the process is useless anyway because the reset button is arm's length away!īy "dead-locked" process, I mean a process that only has one thread (shown in Process Explorer), and is stuck in "Wait:Executive" state (from what I remember). However, what's sick is that Windows can end the process by means of the "process not responding" dialog box, during shutdown only! So that means it's obviously ABLE to kill it, but it just won't, unless you are in the process of rebooting. ![]() Not through any fault of permissions, but just because it refuses to die. ![]() So your only option is to reboot, because the process will never die. One that you can't kill, because it's waiting on some kind of I/O operation that will never complete. Windows Installer (I LOATHE Windows Installer) decided to hang and become one of those occasional "dead-locked processes". Is this even possible? Today I had to reboot my computer (an event in and of itself) for the dumbest reason.
0 Comments
Leave a Reply. |