Bizzarely specific alt-tab bug in Windows 10












1















I've had a very specific bug ever since I upgraded to Windows 10 that no one else I've spoken to has seen, and none of the other Windows 10 alt-tab questions or threads seem to cover.



I often find myself working with Word documents or Adobe-reader PDF's open, for reference, often quickly opening one to look up something, then alt-tabbing to another window to type or read something else. however, since the upgrade to 10, these two programs don't like me alt-tabbing and force their way back to the forefront, but only once. it will be simpler to explain with an example.



Lets say I'm writing something into Window A. I need to stop and reference something, so I quickly load a Word document to reference something, call this Window B. I find what I need in a few seconds, then alt-tab back to Window A and continue typing. 2-3 seconds later, Window B is suddenly in front, and my cursor has been set to it, so my typing is suddenly happening in window B. I backspace this out, alt-tab back to window A, and then that's it. It doesn't force it's way back front anymore.



Unless I need to open another word document, Window C, which will again force it's way back to the forefront the first time I alt-tab away from it, but only the first time I do so.



This multiplies endlessly, but only once per file. Word Window D, E, and F will all object to my alt-tabbing away from them and force thesmelves to the front a few seconds after doing so, but only the first time I do so while Word is open.



Adobe Acrobat displays the exact same behavior, forcing itself to the front after alt-tabbing away, but only the first time.



These stack upon themselves. if I read PDF window G, decide to look up something by loading PDF window H, I can only read a few seconds before G suddenly decides I should still be reading it.



but in each case, this only happens once per instance of having Word or Adobe in memory, per document. if I then go from H to I, then H will force it's way over I, but only once. ad infinitum.



however, if I close all Word and/or Adobe Reader windows, and then load the same document, it all starts again, each one forcing it's way to the front exactly once.



To avoid a commonly asked question in response, yes, the same thing happens if I click on another window in the taskbar instead of alt-tabbing.



However, it is not a case of the switch being forced behind all other windows. the window I alt-tab or click on comes to the front, and I can use it for 3-8 seconds before the word or adobe reader window I left forces it's way in front of it.



At first I tried to ignore it, because after forcing it's way up once it'll behave afterwards until the next time Word or Adobe Reader is loaded into memory, but every time I close them to clear up space on taskbar or memory the whole process starts over again and it's driving me nuts I can't find anything about it.










share|improve this question























  • What do you expect from Beta software.

    – Moab
    Apr 24 '16 at 18:51
















1















I've had a very specific bug ever since I upgraded to Windows 10 that no one else I've spoken to has seen, and none of the other Windows 10 alt-tab questions or threads seem to cover.



I often find myself working with Word documents or Adobe-reader PDF's open, for reference, often quickly opening one to look up something, then alt-tabbing to another window to type or read something else. however, since the upgrade to 10, these two programs don't like me alt-tabbing and force their way back to the forefront, but only once. it will be simpler to explain with an example.



Lets say I'm writing something into Window A. I need to stop and reference something, so I quickly load a Word document to reference something, call this Window B. I find what I need in a few seconds, then alt-tab back to Window A and continue typing. 2-3 seconds later, Window B is suddenly in front, and my cursor has been set to it, so my typing is suddenly happening in window B. I backspace this out, alt-tab back to window A, and then that's it. It doesn't force it's way back front anymore.



Unless I need to open another word document, Window C, which will again force it's way back to the forefront the first time I alt-tab away from it, but only the first time I do so.



This multiplies endlessly, but only once per file. Word Window D, E, and F will all object to my alt-tabbing away from them and force thesmelves to the front a few seconds after doing so, but only the first time I do so while Word is open.



Adobe Acrobat displays the exact same behavior, forcing itself to the front after alt-tabbing away, but only the first time.



These stack upon themselves. if I read PDF window G, decide to look up something by loading PDF window H, I can only read a few seconds before G suddenly decides I should still be reading it.



but in each case, this only happens once per instance of having Word or Adobe in memory, per document. if I then go from H to I, then H will force it's way over I, but only once. ad infinitum.



however, if I close all Word and/or Adobe Reader windows, and then load the same document, it all starts again, each one forcing it's way to the front exactly once.



To avoid a commonly asked question in response, yes, the same thing happens if I click on another window in the taskbar instead of alt-tabbing.



However, it is not a case of the switch being forced behind all other windows. the window I alt-tab or click on comes to the front, and I can use it for 3-8 seconds before the word or adobe reader window I left forces it's way in front of it.



At first I tried to ignore it, because after forcing it's way up once it'll behave afterwards until the next time Word or Adobe Reader is loaded into memory, but every time I close them to clear up space on taskbar or memory the whole process starts over again and it's driving me nuts I can't find anything about it.










share|improve this question























  • What do you expect from Beta software.

    – Moab
    Apr 24 '16 at 18:51














1












1








1


0






I've had a very specific bug ever since I upgraded to Windows 10 that no one else I've spoken to has seen, and none of the other Windows 10 alt-tab questions or threads seem to cover.



I often find myself working with Word documents or Adobe-reader PDF's open, for reference, often quickly opening one to look up something, then alt-tabbing to another window to type or read something else. however, since the upgrade to 10, these two programs don't like me alt-tabbing and force their way back to the forefront, but only once. it will be simpler to explain with an example.



Lets say I'm writing something into Window A. I need to stop and reference something, so I quickly load a Word document to reference something, call this Window B. I find what I need in a few seconds, then alt-tab back to Window A and continue typing. 2-3 seconds later, Window B is suddenly in front, and my cursor has been set to it, so my typing is suddenly happening in window B. I backspace this out, alt-tab back to window A, and then that's it. It doesn't force it's way back front anymore.



Unless I need to open another word document, Window C, which will again force it's way back to the forefront the first time I alt-tab away from it, but only the first time I do so.



This multiplies endlessly, but only once per file. Word Window D, E, and F will all object to my alt-tabbing away from them and force thesmelves to the front a few seconds after doing so, but only the first time I do so while Word is open.



Adobe Acrobat displays the exact same behavior, forcing itself to the front after alt-tabbing away, but only the first time.



These stack upon themselves. if I read PDF window G, decide to look up something by loading PDF window H, I can only read a few seconds before G suddenly decides I should still be reading it.



but in each case, this only happens once per instance of having Word or Adobe in memory, per document. if I then go from H to I, then H will force it's way over I, but only once. ad infinitum.



however, if I close all Word and/or Adobe Reader windows, and then load the same document, it all starts again, each one forcing it's way to the front exactly once.



To avoid a commonly asked question in response, yes, the same thing happens if I click on another window in the taskbar instead of alt-tabbing.



However, it is not a case of the switch being forced behind all other windows. the window I alt-tab or click on comes to the front, and I can use it for 3-8 seconds before the word or adobe reader window I left forces it's way in front of it.



At first I tried to ignore it, because after forcing it's way up once it'll behave afterwards until the next time Word or Adobe Reader is loaded into memory, but every time I close them to clear up space on taskbar or memory the whole process starts over again and it's driving me nuts I can't find anything about it.










share|improve this question














I've had a very specific bug ever since I upgraded to Windows 10 that no one else I've spoken to has seen, and none of the other Windows 10 alt-tab questions or threads seem to cover.



I often find myself working with Word documents or Adobe-reader PDF's open, for reference, often quickly opening one to look up something, then alt-tabbing to another window to type or read something else. however, since the upgrade to 10, these two programs don't like me alt-tabbing and force their way back to the forefront, but only once. it will be simpler to explain with an example.



Lets say I'm writing something into Window A. I need to stop and reference something, so I quickly load a Word document to reference something, call this Window B. I find what I need in a few seconds, then alt-tab back to Window A and continue typing. 2-3 seconds later, Window B is suddenly in front, and my cursor has been set to it, so my typing is suddenly happening in window B. I backspace this out, alt-tab back to window A, and then that's it. It doesn't force it's way back front anymore.



Unless I need to open another word document, Window C, which will again force it's way back to the forefront the first time I alt-tab away from it, but only the first time I do so.



This multiplies endlessly, but only once per file. Word Window D, E, and F will all object to my alt-tabbing away from them and force thesmelves to the front a few seconds after doing so, but only the first time I do so while Word is open.



Adobe Acrobat displays the exact same behavior, forcing itself to the front after alt-tabbing away, but only the first time.



These stack upon themselves. if I read PDF window G, decide to look up something by loading PDF window H, I can only read a few seconds before G suddenly decides I should still be reading it.



but in each case, this only happens once per instance of having Word or Adobe in memory, per document. if I then go from H to I, then H will force it's way over I, but only once. ad infinitum.



however, if I close all Word and/or Adobe Reader windows, and then load the same document, it all starts again, each one forcing it's way to the front exactly once.



To avoid a commonly asked question in response, yes, the same thing happens if I click on another window in the taskbar instead of alt-tabbing.



However, it is not a case of the switch being forced behind all other windows. the window I alt-tab or click on comes to the front, and I can use it for 3-8 seconds before the word or adobe reader window I left forces it's way in front of it.



At first I tried to ignore it, because after forcing it's way up once it'll behave afterwards until the next time Word or Adobe Reader is loaded into memory, but every time I close them to clear up space on taskbar or memory the whole process starts over again and it's driving me nuts I can't find anything about it.







windows-10 microsoft-word-2007 adobe-reader alt-tab






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Apr 24 '16 at 16:39









NekiraNekira

62




62













  • What do you expect from Beta software.

    – Moab
    Apr 24 '16 at 18:51



















  • What do you expect from Beta software.

    – Moab
    Apr 24 '16 at 18:51

















What do you expect from Beta software.

– Moab
Apr 24 '16 at 18:51





What do you expect from Beta software.

– Moab
Apr 24 '16 at 18:51










2 Answers
2






active

oldest

votes


















0














Adobe has been known to intercept the keyboard hook. For example the escape key won't work in other programs if adobe photoshop elements 10 (and other versions) is open.



Immediate thoughts - use autohotkey to override it back to normal? Or investigate what if anything is hooking it/responsible, by shutting down processes and services until it works, or trying to find what leads to it not working?



But my 1st reaction to "key not behaving as expected" and "anything about adobe software on board" is to look hard at adobe ;-)






share|improve this answer
























  • The problem with that is that Word continues to exhibit the same behavior even if Adobe is uninstalled, so clearly the issue isn't with adobe itself.

    – Nekira
    Apr 25 '16 at 16:36



















0














While the cause of the bug remains unkown, it appears a patch of windows 10 eventually fixed it.






share|improve this answer
























  • Any idea which update fixed it? How certain are you this was the solution? Keep in mind the goal here includes to help someone else with the same problem.

    – Twisty Impersonator
    Dec 23 '18 at 2:56











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%2f1069225%2fbizzarely-specific-alt-tab-bug-in-windows-10%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Adobe has been known to intercept the keyboard hook. For example the escape key won't work in other programs if adobe photoshop elements 10 (and other versions) is open.



Immediate thoughts - use autohotkey to override it back to normal? Or investigate what if anything is hooking it/responsible, by shutting down processes and services until it works, or trying to find what leads to it not working?



But my 1st reaction to "key not behaving as expected" and "anything about adobe software on board" is to look hard at adobe ;-)






share|improve this answer
























  • The problem with that is that Word continues to exhibit the same behavior even if Adobe is uninstalled, so clearly the issue isn't with adobe itself.

    – Nekira
    Apr 25 '16 at 16:36
















0














Adobe has been known to intercept the keyboard hook. For example the escape key won't work in other programs if adobe photoshop elements 10 (and other versions) is open.



Immediate thoughts - use autohotkey to override it back to normal? Or investigate what if anything is hooking it/responsible, by shutting down processes and services until it works, or trying to find what leads to it not working?



But my 1st reaction to "key not behaving as expected" and "anything about adobe software on board" is to look hard at adobe ;-)






share|improve this answer
























  • The problem with that is that Word continues to exhibit the same behavior even if Adobe is uninstalled, so clearly the issue isn't with adobe itself.

    – Nekira
    Apr 25 '16 at 16:36














0












0








0







Adobe has been known to intercept the keyboard hook. For example the escape key won't work in other programs if adobe photoshop elements 10 (and other versions) is open.



Immediate thoughts - use autohotkey to override it back to normal? Or investigate what if anything is hooking it/responsible, by shutting down processes and services until it works, or trying to find what leads to it not working?



But my 1st reaction to "key not behaving as expected" and "anything about adobe software on board" is to look hard at adobe ;-)






share|improve this answer













Adobe has been known to intercept the keyboard hook. For example the escape key won't work in other programs if adobe photoshop elements 10 (and other versions) is open.



Immediate thoughts - use autohotkey to override it back to normal? Or investigate what if anything is hooking it/responsible, by shutting down processes and services until it works, or trying to find what leads to it not working?



But my 1st reaction to "key not behaving as expected" and "anything about adobe software on board" is to look hard at adobe ;-)







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 25 '16 at 13:26









StilezStilez

7531920




7531920













  • The problem with that is that Word continues to exhibit the same behavior even if Adobe is uninstalled, so clearly the issue isn't with adobe itself.

    – Nekira
    Apr 25 '16 at 16:36



















  • The problem with that is that Word continues to exhibit the same behavior even if Adobe is uninstalled, so clearly the issue isn't with adobe itself.

    – Nekira
    Apr 25 '16 at 16:36

















The problem with that is that Word continues to exhibit the same behavior even if Adobe is uninstalled, so clearly the issue isn't with adobe itself.

– Nekira
Apr 25 '16 at 16:36





The problem with that is that Word continues to exhibit the same behavior even if Adobe is uninstalled, so clearly the issue isn't with adobe itself.

– Nekira
Apr 25 '16 at 16:36













0














While the cause of the bug remains unkown, it appears a patch of windows 10 eventually fixed it.






share|improve this answer
























  • Any idea which update fixed it? How certain are you this was the solution? Keep in mind the goal here includes to help someone else with the same problem.

    – Twisty Impersonator
    Dec 23 '18 at 2:56
















0














While the cause of the bug remains unkown, it appears a patch of windows 10 eventually fixed it.






share|improve this answer
























  • Any idea which update fixed it? How certain are you this was the solution? Keep in mind the goal here includes to help someone else with the same problem.

    – Twisty Impersonator
    Dec 23 '18 at 2:56














0












0








0







While the cause of the bug remains unkown, it appears a patch of windows 10 eventually fixed it.






share|improve this answer













While the cause of the bug remains unkown, it appears a patch of windows 10 eventually fixed it.







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 23 '18 at 2:24









NekiraNekira

62




62













  • Any idea which update fixed it? How certain are you this was the solution? Keep in mind the goal here includes to help someone else with the same problem.

    – Twisty Impersonator
    Dec 23 '18 at 2:56



















  • Any idea which update fixed it? How certain are you this was the solution? Keep in mind the goal here includes to help someone else with the same problem.

    – Twisty Impersonator
    Dec 23 '18 at 2:56

















Any idea which update fixed it? How certain are you this was the solution? Keep in mind the goal here includes to help someone else with the same problem.

– Twisty Impersonator
Dec 23 '18 at 2:56





Any idea which update fixed it? How certain are you this was the solution? Keep in mind the goal here includes to help someone else with the same problem.

– Twisty Impersonator
Dec 23 '18 at 2:56


















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%2f1069225%2fbizzarely-specific-alt-tab-bug-in-windows-10%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

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

Origin of the phrase “under your belt”?