Clicking through windows
Approximately after last big creator update, I noticed that some windows become "click-through", that is, when I try to click something in a window, what is actually clicked is behind it (which is invisible until you click it).
If it's another window that was behind it comes to the top, if it's desktop and you manage to double click an icon - that app will come up, etc. The click to the visible window on top do not register.
So far it happened to Google Chrome and Steam. It happens appropriately once a day, I was not able to determine what causes it. If you close the affected app and re-open it the effect goes away.
Any idea how I could track down, why this keeps happening?
Update: Just to avoid answer that suggest to "reboot" or "reinstall windows", here is what I tried:
- Antivirus check - pass
- chkdsk check - pass
- SFC /Scannow - pass
- Windows Update - latest
PC is being re-booted regularly.
windows-10
add a comment |
Approximately after last big creator update, I noticed that some windows become "click-through", that is, when I try to click something in a window, what is actually clicked is behind it (which is invisible until you click it).
If it's another window that was behind it comes to the top, if it's desktop and you manage to double click an icon - that app will come up, etc. The click to the visible window on top do not register.
So far it happened to Google Chrome and Steam. It happens appropriately once a day, I was not able to determine what causes it. If you close the affected app and re-open it the effect goes away.
Any idea how I could track down, why this keeps happening?
Update: Just to avoid answer that suggest to "reboot" or "reinstall windows", here is what I tried:
- Antivirus check - pass
- chkdsk check - pass
- SFC /Scannow - pass
- Windows Update - latest
PC is being re-booted regularly.
windows-10
1
I have the same issue. It happens to my Battle.net client and is extremely irritating.
– Dois
Dec 15 '17 at 3:44
I'm still getting this. No obvious fix. Pain in the ass.
– darylknight
Mar 28 at 9:21
add a comment |
Approximately after last big creator update, I noticed that some windows become "click-through", that is, when I try to click something in a window, what is actually clicked is behind it (which is invisible until you click it).
If it's another window that was behind it comes to the top, if it's desktop and you manage to double click an icon - that app will come up, etc. The click to the visible window on top do not register.
So far it happened to Google Chrome and Steam. It happens appropriately once a day, I was not able to determine what causes it. If you close the affected app and re-open it the effect goes away.
Any idea how I could track down, why this keeps happening?
Update: Just to avoid answer that suggest to "reboot" or "reinstall windows", here is what I tried:
- Antivirus check - pass
- chkdsk check - pass
- SFC /Scannow - pass
- Windows Update - latest
PC is being re-booted regularly.
windows-10
Approximately after last big creator update, I noticed that some windows become "click-through", that is, when I try to click something in a window, what is actually clicked is behind it (which is invisible until you click it).
If it's another window that was behind it comes to the top, if it's desktop and you manage to double click an icon - that app will come up, etc. The click to the visible window on top do not register.
So far it happened to Google Chrome and Steam. It happens appropriately once a day, I was not able to determine what causes it. If you close the affected app and re-open it the effect goes away.
Any idea how I could track down, why this keeps happening?
Update: Just to avoid answer that suggest to "reboot" or "reinstall windows", here is what I tried:
- Antivirus check - pass
- chkdsk check - pass
- SFC /Scannow - pass
- Windows Update - latest
PC is being re-booted regularly.
windows-10
windows-10
edited Dec 11 '17 at 23:37
asked Dec 11 '17 at 23:21
Andrew Savinykh
91731728
91731728
1
I have the same issue. It happens to my Battle.net client and is extremely irritating.
– Dois
Dec 15 '17 at 3:44
I'm still getting this. No obvious fix. Pain in the ass.
– darylknight
Mar 28 at 9:21
add a comment |
1
I have the same issue. It happens to my Battle.net client and is extremely irritating.
– Dois
Dec 15 '17 at 3:44
I'm still getting this. No obvious fix. Pain in the ass.
– darylknight
Mar 28 at 9:21
1
1
I have the same issue. It happens to my Battle.net client and is extremely irritating.
– Dois
Dec 15 '17 at 3:44
I have the same issue. It happens to my Battle.net client and is extremely irritating.
– Dois
Dec 15 '17 at 3:44
I'm still getting this. No obvious fix. Pain in the ass.
– darylknight
Mar 28 at 9:21
I'm still getting this. No obvious fix. Pain in the ass.
– darylknight
Mar 28 at 9:21
add a comment |
5 Answers
5
active
oldest
votes
I have that bug too. Only fix afaik is downgrading to a pre 1709 version. A temporary workaround is hitting Win+D twice or reloading the vga driver with CTRL+Shift+Win+B or minimizing and maximizing the affected windows.
1
I've recently been experiencing this as well - your double win+d solution fixed the immediate symptom. Thanks for the workaround until a real answer appears.
– Big Luke
Feb 15 at 12:03
Thank you, CTRL+Shift+Win+B worked for me. Great advice!
– Andrew Savinykh
Mar 2 at 5:29
That's the command to restart the GPU. Have y'all checked for updated graphics drivers for your systems?
– music2myear
May 17 at 21:31
This seems to happen after my son plays Fortnite - only solution previously was a reboot - double Win+D seems to have solved it.
– jmc
Nov 10 at 21:17
add a comment |
Try to use DISM.EXE to check/repair system files:
- Scan to check for corruption:
Dism /Online /Cleanup-Image /ScanHealth
- Check to see whether any corruption has been dethatched:
Dism /Online /Cleanup-Image /CheckHealth
- If it is repairable, type below command(make sure that system built-in Windows Update is working as below command using Windows Update to provide the files that are required to fix corruptions):
DISM.exe /Online /Cleanup-image /Restorehealth
>So far it happened to Google Chrome and Steam.
If it happens on specific software/program, try to have an reparation installation, or re-installation and check the result.
add a comment |
Have had the same issue recently on Win 10 1803 with a Logitech G403 mouse on a Surface Book 2 - sometimes touch input would work nevertheless, sometimes it wouldn't. Win+L, then signing back in works for me to restore functionality - so does Ctrl+Alt+Del, then simply dismissing the screen that opens.
add a comment |
I just now had this happen to me in audacity and was able to make it start responding again by alt-tabbing through all my programs a couple times and ending up in audacity again. Not a very good solution, but it worked in a pinch.
add a comment |
You might have to do a fresh re-installation of Windows to fix the error. Or you can run chkdsk (check disk) which checks your system for errors. To do this, press (Win Key + R), type cmd and press enter. As soon as the Command Prompt window pops up, type chkdsk and press enter. It might take a while for the utility to check your whole system.
Obviously he knows about reinstalling windows, and as for chkdsk, If you had had that problem or heard of that problem and heard of that solution working then mention it but you have not. And it's not the kind of thing that a hard drive or data corruption issue causes at all.
– barlop
Dec 12 '17 at 1:10
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1276270%2fclicking-through-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have that bug too. Only fix afaik is downgrading to a pre 1709 version. A temporary workaround is hitting Win+D twice or reloading the vga driver with CTRL+Shift+Win+B or minimizing and maximizing the affected windows.
1
I've recently been experiencing this as well - your double win+d solution fixed the immediate symptom. Thanks for the workaround until a real answer appears.
– Big Luke
Feb 15 at 12:03
Thank you, CTRL+Shift+Win+B worked for me. Great advice!
– Andrew Savinykh
Mar 2 at 5:29
That's the command to restart the GPU. Have y'all checked for updated graphics drivers for your systems?
– music2myear
May 17 at 21:31
This seems to happen after my son plays Fortnite - only solution previously was a reboot - double Win+D seems to have solved it.
– jmc
Nov 10 at 21:17
add a comment |
I have that bug too. Only fix afaik is downgrading to a pre 1709 version. A temporary workaround is hitting Win+D twice or reloading the vga driver with CTRL+Shift+Win+B or minimizing and maximizing the affected windows.
1
I've recently been experiencing this as well - your double win+d solution fixed the immediate symptom. Thanks for the workaround until a real answer appears.
– Big Luke
Feb 15 at 12:03
Thank you, CTRL+Shift+Win+B worked for me. Great advice!
– Andrew Savinykh
Mar 2 at 5:29
That's the command to restart the GPU. Have y'all checked for updated graphics drivers for your systems?
– music2myear
May 17 at 21:31
This seems to happen after my son plays Fortnite - only solution previously was a reboot - double Win+D seems to have solved it.
– jmc
Nov 10 at 21:17
add a comment |
I have that bug too. Only fix afaik is downgrading to a pre 1709 version. A temporary workaround is hitting Win+D twice or reloading the vga driver with CTRL+Shift+Win+B or minimizing and maximizing the affected windows.
I have that bug too. Only fix afaik is downgrading to a pre 1709 version. A temporary workaround is hitting Win+D twice or reloading the vga driver with CTRL+Shift+Win+B or minimizing and maximizing the affected windows.
edited Feb 18 at 14:39
Dom42
866
866
answered Feb 15 at 0:07
dude
8112
8112
1
I've recently been experiencing this as well - your double win+d solution fixed the immediate symptom. Thanks for the workaround until a real answer appears.
– Big Luke
Feb 15 at 12:03
Thank you, CTRL+Shift+Win+B worked for me. Great advice!
– Andrew Savinykh
Mar 2 at 5:29
That's the command to restart the GPU. Have y'all checked for updated graphics drivers for your systems?
– music2myear
May 17 at 21:31
This seems to happen after my son plays Fortnite - only solution previously was a reboot - double Win+D seems to have solved it.
– jmc
Nov 10 at 21:17
add a comment |
1
I've recently been experiencing this as well - your double win+d solution fixed the immediate symptom. Thanks for the workaround until a real answer appears.
– Big Luke
Feb 15 at 12:03
Thank you, CTRL+Shift+Win+B worked for me. Great advice!
– Andrew Savinykh
Mar 2 at 5:29
That's the command to restart the GPU. Have y'all checked for updated graphics drivers for your systems?
– music2myear
May 17 at 21:31
This seems to happen after my son plays Fortnite - only solution previously was a reboot - double Win+D seems to have solved it.
– jmc
Nov 10 at 21:17
1
1
I've recently been experiencing this as well - your double win+d solution fixed the immediate symptom. Thanks for the workaround until a real answer appears.
– Big Luke
Feb 15 at 12:03
I've recently been experiencing this as well - your double win+d solution fixed the immediate symptom. Thanks for the workaround until a real answer appears.
– Big Luke
Feb 15 at 12:03
Thank you, CTRL+Shift+Win+B worked for me. Great advice!
– Andrew Savinykh
Mar 2 at 5:29
Thank you, CTRL+Shift+Win+B worked for me. Great advice!
– Andrew Savinykh
Mar 2 at 5:29
That's the command to restart the GPU. Have y'all checked for updated graphics drivers for your systems?
– music2myear
May 17 at 21:31
That's the command to restart the GPU. Have y'all checked for updated graphics drivers for your systems?
– music2myear
May 17 at 21:31
This seems to happen after my son plays Fortnite - only solution previously was a reboot - double Win+D seems to have solved it.
– jmc
Nov 10 at 21:17
This seems to happen after my son plays Fortnite - only solution previously was a reboot - double Win+D seems to have solved it.
– jmc
Nov 10 at 21:17
add a comment |
Try to use DISM.EXE to check/repair system files:
- Scan to check for corruption:
Dism /Online /Cleanup-Image /ScanHealth
- Check to see whether any corruption has been dethatched:
Dism /Online /Cleanup-Image /CheckHealth
- If it is repairable, type below command(make sure that system built-in Windows Update is working as below command using Windows Update to provide the files that are required to fix corruptions):
DISM.exe /Online /Cleanup-image /Restorehealth
>So far it happened to Google Chrome and Steam.
If it happens on specific software/program, try to have an reparation installation, or re-installation and check the result.
add a comment |
Try to use DISM.EXE to check/repair system files:
- Scan to check for corruption:
Dism /Online /Cleanup-Image /ScanHealth
- Check to see whether any corruption has been dethatched:
Dism /Online /Cleanup-Image /CheckHealth
- If it is repairable, type below command(make sure that system built-in Windows Update is working as below command using Windows Update to provide the files that are required to fix corruptions):
DISM.exe /Online /Cleanup-image /Restorehealth
>So far it happened to Google Chrome and Steam.
If it happens on specific software/program, try to have an reparation installation, or re-installation and check the result.
add a comment |
Try to use DISM.EXE to check/repair system files:
- Scan to check for corruption:
Dism /Online /Cleanup-Image /ScanHealth
- Check to see whether any corruption has been dethatched:
Dism /Online /Cleanup-Image /CheckHealth
- If it is repairable, type below command(make sure that system built-in Windows Update is working as below command using Windows Update to provide the files that are required to fix corruptions):
DISM.exe /Online /Cleanup-image /Restorehealth
>So far it happened to Google Chrome and Steam.
If it happens on specific software/program, try to have an reparation installation, or re-installation and check the result.
Try to use DISM.EXE to check/repair system files:
- Scan to check for corruption:
Dism /Online /Cleanup-Image /ScanHealth
- Check to see whether any corruption has been dethatched:
Dism /Online /Cleanup-Image /CheckHealth
- If it is repairable, type below command(make sure that system built-in Windows Update is working as below command using Windows Update to provide the files that are required to fix corruptions):
DISM.exe /Online /Cleanup-image /Restorehealth
>So far it happened to Google Chrome and Steam.
If it happens on specific software/program, try to have an reparation installation, or re-installation and check the result.
answered Dec 12 '17 at 2:45
eve wang
27212
27212
add a comment |
add a comment |
Have had the same issue recently on Win 10 1803 with a Logitech G403 mouse on a Surface Book 2 - sometimes touch input would work nevertheless, sometimes it wouldn't. Win+L, then signing back in works for me to restore functionality - so does Ctrl+Alt+Del, then simply dismissing the screen that opens.
add a comment |
Have had the same issue recently on Win 10 1803 with a Logitech G403 mouse on a Surface Book 2 - sometimes touch input would work nevertheless, sometimes it wouldn't. Win+L, then signing back in works for me to restore functionality - so does Ctrl+Alt+Del, then simply dismissing the screen that opens.
add a comment |
Have had the same issue recently on Win 10 1803 with a Logitech G403 mouse on a Surface Book 2 - sometimes touch input would work nevertheless, sometimes it wouldn't. Win+L, then signing back in works for me to restore functionality - so does Ctrl+Alt+Del, then simply dismissing the screen that opens.
Have had the same issue recently on Win 10 1803 with a Logitech G403 mouse on a Surface Book 2 - sometimes touch input would work nevertheless, sometimes it wouldn't. Win+L, then signing back in works for me to restore functionality - so does Ctrl+Alt+Del, then simply dismissing the screen that opens.
answered Nov 4 at 23:16
Michael Jess
1011
1011
add a comment |
add a comment |
I just now had this happen to me in audacity and was able to make it start responding again by alt-tabbing through all my programs a couple times and ending up in audacity again. Not a very good solution, but it worked in a pinch.
add a comment |
I just now had this happen to me in audacity and was able to make it start responding again by alt-tabbing through all my programs a couple times and ending up in audacity again. Not a very good solution, but it worked in a pinch.
add a comment |
I just now had this happen to me in audacity and was able to make it start responding again by alt-tabbing through all my programs a couple times and ending up in audacity again. Not a very good solution, but it worked in a pinch.
I just now had this happen to me in audacity and was able to make it start responding again by alt-tabbing through all my programs a couple times and ending up in audacity again. Not a very good solution, but it worked in a pinch.
answered Dec 13 '17 at 3:05
Sparrowhawk
1
1
add a comment |
add a comment |
You might have to do a fresh re-installation of Windows to fix the error. Or you can run chkdsk (check disk) which checks your system for errors. To do this, press (Win Key + R), type cmd and press enter. As soon as the Command Prompt window pops up, type chkdsk and press enter. It might take a while for the utility to check your whole system.
Obviously he knows about reinstalling windows, and as for chkdsk, If you had had that problem or heard of that problem and heard of that solution working then mention it but you have not. And it's not the kind of thing that a hard drive or data corruption issue causes at all.
– barlop
Dec 12 '17 at 1:10
add a comment |
You might have to do a fresh re-installation of Windows to fix the error. Or you can run chkdsk (check disk) which checks your system for errors. To do this, press (Win Key + R), type cmd and press enter. As soon as the Command Prompt window pops up, type chkdsk and press enter. It might take a while for the utility to check your whole system.
Obviously he knows about reinstalling windows, and as for chkdsk, If you had had that problem or heard of that problem and heard of that solution working then mention it but you have not. And it's not the kind of thing that a hard drive or data corruption issue causes at all.
– barlop
Dec 12 '17 at 1:10
add a comment |
You might have to do a fresh re-installation of Windows to fix the error. Or you can run chkdsk (check disk) which checks your system for errors. To do this, press (Win Key + R), type cmd and press enter. As soon as the Command Prompt window pops up, type chkdsk and press enter. It might take a while for the utility to check your whole system.
You might have to do a fresh re-installation of Windows to fix the error. Or you can run chkdsk (check disk) which checks your system for errors. To do this, press (Win Key + R), type cmd and press enter. As soon as the Command Prompt window pops up, type chkdsk and press enter. It might take a while for the utility to check your whole system.
answered Dec 11 '17 at 23:32
Jacob M.
217
217
Obviously he knows about reinstalling windows, and as for chkdsk, If you had had that problem or heard of that problem and heard of that solution working then mention it but you have not. And it's not the kind of thing that a hard drive or data corruption issue causes at all.
– barlop
Dec 12 '17 at 1:10
add a comment |
Obviously he knows about reinstalling windows, and as for chkdsk, If you had had that problem or heard of that problem and heard of that solution working then mention it but you have not. And it's not the kind of thing that a hard drive or data corruption issue causes at all.
– barlop
Dec 12 '17 at 1:10
Obviously he knows about reinstalling windows, and as for chkdsk, If you had had that problem or heard of that problem and heard of that solution working then mention it but you have not. And it's not the kind of thing that a hard drive or data corruption issue causes at all.
– barlop
Dec 12 '17 at 1:10
Obviously he knows about reinstalling windows, and as for chkdsk, If you had had that problem or heard of that problem and heard of that solution working then mention it but you have not. And it's not the kind of thing that a hard drive or data corruption issue causes at all.
– barlop
Dec 12 '17 at 1:10
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1276270%2fclicking-through-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
1
I have the same issue. It happens to my Battle.net client and is extremely irritating.
– Dois
Dec 15 '17 at 3:44
I'm still getting this. No obvious fix. Pain in the ass.
– darylknight
Mar 28 at 9:21