Close unresponsive window without waiting for “… is not responding” dialog












0















Once a window becomes unresponsive to input (mouse clicks), OS first waits 10 seconds, then window contents lighten, and a dialog appears:




... is not responding



If you close the program, you might lose information.




With these options to choose from:




Close the program



Wait for the program to respond




A reason for windows to became unresponsive is not a problem I need to address. Applications work as expected, I just don't need to wait for them to complete what they are doing.



Killing a task with task manager is not a good way because this takes roughly the same time at least.



I would like to have options to close a window faster without waiting several seconds for this routine.



Is there a way to lower response timeout to, say, 2 seconds?



Is there a third-party utility to kill currently active window with a shortcut, like Ctrl+Alt+F4?










share|improve this question

























  • Usually you could just click a close button a couple of times and Windows will ask you about closing an unresponsive application.

    – montonero
    Jan 28 at 14:39











  • When a window is unresponsive, it seems that it doesn't matter if it's close button or any other part of the window that is clicked, This takes several seconds of waiting and clicking for it to show the dialog.

    – estus
    Jan 28 at 14:42








  • 1





    Well, I've just tried it myself. It takes about 5 seconds for me when Windows allowed to close an unresponsive application with the close button. And this seems like an answer: stackoverflow.com/questions/4586029/…

    – montonero
    Jan 28 at 14:56











  • @montonero Thanks for the hint, I'll try HungAppTimeOut, it looks like what I'm looking for (for the first part of the question).

    – estus
    Jan 28 at 15:05
















0















Once a window becomes unresponsive to input (mouse clicks), OS first waits 10 seconds, then window contents lighten, and a dialog appears:




... is not responding



If you close the program, you might lose information.




With these options to choose from:




Close the program



Wait for the program to respond




A reason for windows to became unresponsive is not a problem I need to address. Applications work as expected, I just don't need to wait for them to complete what they are doing.



Killing a task with task manager is not a good way because this takes roughly the same time at least.



I would like to have options to close a window faster without waiting several seconds for this routine.



Is there a way to lower response timeout to, say, 2 seconds?



Is there a third-party utility to kill currently active window with a shortcut, like Ctrl+Alt+F4?










share|improve this question

























  • Usually you could just click a close button a couple of times and Windows will ask you about closing an unresponsive application.

    – montonero
    Jan 28 at 14:39











  • When a window is unresponsive, it seems that it doesn't matter if it's close button or any other part of the window that is clicked, This takes several seconds of waiting and clicking for it to show the dialog.

    – estus
    Jan 28 at 14:42








  • 1





    Well, I've just tried it myself. It takes about 5 seconds for me when Windows allowed to close an unresponsive application with the close button. And this seems like an answer: stackoverflow.com/questions/4586029/…

    – montonero
    Jan 28 at 14:56











  • @montonero Thanks for the hint, I'll try HungAppTimeOut, it looks like what I'm looking for (for the first part of the question).

    – estus
    Jan 28 at 15:05














0












0








0








Once a window becomes unresponsive to input (mouse clicks), OS first waits 10 seconds, then window contents lighten, and a dialog appears:




... is not responding



If you close the program, you might lose information.




With these options to choose from:




Close the program



Wait for the program to respond




A reason for windows to became unresponsive is not a problem I need to address. Applications work as expected, I just don't need to wait for them to complete what they are doing.



Killing a task with task manager is not a good way because this takes roughly the same time at least.



I would like to have options to close a window faster without waiting several seconds for this routine.



Is there a way to lower response timeout to, say, 2 seconds?



Is there a third-party utility to kill currently active window with a shortcut, like Ctrl+Alt+F4?










share|improve this question
















Once a window becomes unresponsive to input (mouse clicks), OS first waits 10 seconds, then window contents lighten, and a dialog appears:




... is not responding



If you close the program, you might lose information.




With these options to choose from:




Close the program



Wait for the program to respond




A reason for windows to became unresponsive is not a problem I need to address. Applications work as expected, I just don't need to wait for them to complete what they are doing.



Killing a task with task manager is not a good way because this takes roughly the same time at least.



I would like to have options to close a window faster without waiting several seconds for this routine.



Is there a way to lower response timeout to, say, 2 seconds?



Is there a third-party utility to kill currently active window with a shortcut, like Ctrl+Alt+F4?







windows-7 windows window unresponsive






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 28 at 14:19









TDK

34713




34713










asked Jan 28 at 14:09









estusestus

5319




5319













  • Usually you could just click a close button a couple of times and Windows will ask you about closing an unresponsive application.

    – montonero
    Jan 28 at 14:39











  • When a window is unresponsive, it seems that it doesn't matter if it's close button or any other part of the window that is clicked, This takes several seconds of waiting and clicking for it to show the dialog.

    – estus
    Jan 28 at 14:42








  • 1





    Well, I've just tried it myself. It takes about 5 seconds for me when Windows allowed to close an unresponsive application with the close button. And this seems like an answer: stackoverflow.com/questions/4586029/…

    – montonero
    Jan 28 at 14:56











  • @montonero Thanks for the hint, I'll try HungAppTimeOut, it looks like what I'm looking for (for the first part of the question).

    – estus
    Jan 28 at 15:05



















  • Usually you could just click a close button a couple of times and Windows will ask you about closing an unresponsive application.

    – montonero
    Jan 28 at 14:39











  • When a window is unresponsive, it seems that it doesn't matter if it's close button or any other part of the window that is clicked, This takes several seconds of waiting and clicking for it to show the dialog.

    – estus
    Jan 28 at 14:42








  • 1





    Well, I've just tried it myself. It takes about 5 seconds for me when Windows allowed to close an unresponsive application with the close button. And this seems like an answer: stackoverflow.com/questions/4586029/…

    – montonero
    Jan 28 at 14:56











  • @montonero Thanks for the hint, I'll try HungAppTimeOut, it looks like what I'm looking for (for the first part of the question).

    – estus
    Jan 28 at 15:05

















Usually you could just click a close button a couple of times and Windows will ask you about closing an unresponsive application.

– montonero
Jan 28 at 14:39





Usually you could just click a close button a couple of times and Windows will ask you about closing an unresponsive application.

– montonero
Jan 28 at 14:39













When a window is unresponsive, it seems that it doesn't matter if it's close button or any other part of the window that is clicked, This takes several seconds of waiting and clicking for it to show the dialog.

– estus
Jan 28 at 14:42







When a window is unresponsive, it seems that it doesn't matter if it's close button or any other part of the window that is clicked, This takes several seconds of waiting and clicking for it to show the dialog.

– estus
Jan 28 at 14:42






1




1





Well, I've just tried it myself. It takes about 5 seconds for me when Windows allowed to close an unresponsive application with the close button. And this seems like an answer: stackoverflow.com/questions/4586029/…

– montonero
Jan 28 at 14:56





Well, I've just tried it myself. It takes about 5 seconds for me when Windows allowed to close an unresponsive application with the close button. And this seems like an answer: stackoverflow.com/questions/4586029/…

– montonero
Jan 28 at 14:56













@montonero Thanks for the hint, I'll try HungAppTimeOut, it looks like what I'm looking for (for the first part of the question).

– estus
Jan 28 at 15:05





@montonero Thanks for the hint, I'll try HungAppTimeOut, it looks like what I'm looking for (for the first part of the question).

– estus
Jan 28 at 15:05










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399271%2fclose-unresponsive-window-without-waiting-for-is-not-responding-dialog%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399271%2fclose-unresponsive-window-without-waiting-for-is-not-responding-dialog%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

Eduardo VII do Reino Unido