ActiveWndTrackTimeout Value Being Ignored











up vote
10
down vote

favorite
5












I normally have Active Window Tracking (XMouse) turned on in my Windows 8 machine. I wrote a small .Net utility to turn it on/off and adjust the delay. Works great!



After installing Windows 8.1, however, the ActiveWndTrackTimeout delay is being ignored no matter what value is in there. The window switch is occurring immediately regardless of the value in the registry:



ActiveWndTrackTimeout entry in my Registry



Has anyone else experienced this bug or have a fix for me? I can easily turn the feature on/off, but I'd rather leave it on with a reasonable delay.



I'm running Windows 8.1 Pro on a 64-bit machine.










share|improve this question




























    up vote
    10
    down vote

    favorite
    5












    I normally have Active Window Tracking (XMouse) turned on in my Windows 8 machine. I wrote a small .Net utility to turn it on/off and adjust the delay. Works great!



    After installing Windows 8.1, however, the ActiveWndTrackTimeout delay is being ignored no matter what value is in there. The window switch is occurring immediately regardless of the value in the registry:



    ActiveWndTrackTimeout entry in my Registry



    Has anyone else experienced this bug or have a fix for me? I can easily turn the feature on/off, but I'd rather leave it on with a reasonable delay.



    I'm running Windows 8.1 Pro on a 64-bit machine.










    share|improve this question


























      up vote
      10
      down vote

      favorite
      5









      up vote
      10
      down vote

      favorite
      5






      5





      I normally have Active Window Tracking (XMouse) turned on in my Windows 8 machine. I wrote a small .Net utility to turn it on/off and adjust the delay. Works great!



      After installing Windows 8.1, however, the ActiveWndTrackTimeout delay is being ignored no matter what value is in there. The window switch is occurring immediately regardless of the value in the registry:



      ActiveWndTrackTimeout entry in my Registry



      Has anyone else experienced this bug or have a fix for me? I can easily turn the feature on/off, but I'd rather leave it on with a reasonable delay.



      I'm running Windows 8.1 Pro on a 64-bit machine.










      share|improve this question















      I normally have Active Window Tracking (XMouse) turned on in my Windows 8 machine. I wrote a small .Net utility to turn it on/off and adjust the delay. Works great!



      After installing Windows 8.1, however, the ActiveWndTrackTimeout delay is being ignored no matter what value is in there. The window switch is occurring immediately regardless of the value in the registry:



      ActiveWndTrackTimeout entry in my Registry



      Has anyone else experienced this bug or have a fix for me? I can easily turn the feature on/off, but I'd rather leave it on with a reasonable delay.



      I'm running Windows 8.1 Pro on a 64-bit machine.







      windows-8






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Oct 26 '13 at 7:12









      harrymc

      249k10257550




      249k10257550










      asked Oct 23 '13 at 17:09









      Idle_Mind

      10116




      10116






















          3 Answers
          3






          active

          oldest

          votes

















          up vote
          8
          down vote













          I had Win8 and "ActiveWndTrackTimeout" was working fine, but when I updated to Win8.1 it stopped working. I had to RENAME "ActiveWndTrackTimeout" to "ActiveWndTrkTimeout", sign out and in, and now it works in Win8.1 too.






          share|improve this answer





















          • I had same problem with Windows 7 and this solution of renaming + restarting worked for me! Thanks!
            – J.D.
            May 10 '15 at 20:10


















          up vote
          7
          down vote













          Maybe try ActiveWndTrkTimeout. http://technet.microsoft.com/en-us/library/cc957203.aspx






          share|improve this answer





















          • I've added in an ActiveWndtrkTimeout entry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the old ActiveWndTrackTimeout but still no change either.
            – Idle_Mind
            Oct 26 '13 at 5:19










          • My registry started with a value called "ActiveWndTrackTimeout" which had no effect. When I renamed it to "ActiveWndTrkTimeout" it worked for me (Windows 7).
            – Dave L.
            Dec 26 '13 at 17:53


















          up vote
          1
          down vote













          Such an old question but still appears to be valid even for windows 10 (Seriously Microsoft you should fix it once and for all)



          I started window 10 with Windows 10 1703 (15063.1387 - I don't think these minors are important).



          I had configured:
          At path: HKEY_CURRENT_USERControl PanelDesktop
          value: ActiveWndTrackTimeout to 2000 (ms)



          After upgrade to Windows 10 1709 (16299.461) everthing stopped working again.
          I haved added a registry DWORD key ActiveWndtrkTimeout with the same value (leaving the old key there) and the raise delay started to work again.



          From the MSDN:




          ActiveWndTrkTimeout



          HKCUControl PanelDesktop



          REG_DWORD

          Milliseconds

          0




          0 is the default value.



          Note: I want to get one disinformation corrected



          There is also a registry entry MouseHoverTime at HKEY_CURRENT_USERControl PanelMouse. This entry does not change the window raise delay. It changes how fast are the taskbar information & preview shown.






          share|improve this answer





















            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',
            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%2f664351%2factivewndtracktimeout-value-being-ignored%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            8
            down vote













            I had Win8 and "ActiveWndTrackTimeout" was working fine, but when I updated to Win8.1 it stopped working. I had to RENAME "ActiveWndTrackTimeout" to "ActiveWndTrkTimeout", sign out and in, and now it works in Win8.1 too.






            share|improve this answer





















            • I had same problem with Windows 7 and this solution of renaming + restarting worked for me! Thanks!
              – J.D.
              May 10 '15 at 20:10















            up vote
            8
            down vote













            I had Win8 and "ActiveWndTrackTimeout" was working fine, but when I updated to Win8.1 it stopped working. I had to RENAME "ActiveWndTrackTimeout" to "ActiveWndTrkTimeout", sign out and in, and now it works in Win8.1 too.






            share|improve this answer





















            • I had same problem with Windows 7 and this solution of renaming + restarting worked for me! Thanks!
              – J.D.
              May 10 '15 at 20:10













            up vote
            8
            down vote










            up vote
            8
            down vote









            I had Win8 and "ActiveWndTrackTimeout" was working fine, but when I updated to Win8.1 it stopped working. I had to RENAME "ActiveWndTrackTimeout" to "ActiveWndTrkTimeout", sign out and in, and now it works in Win8.1 too.






            share|improve this answer












            I had Win8 and "ActiveWndTrackTimeout" was working fine, but when I updated to Win8.1 it stopped working. I had to RENAME "ActiveWndTrackTimeout" to "ActiveWndTrkTimeout", sign out and in, and now it works in Win8.1 too.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Aug 28 '14 at 9:52









            Nicolau

            10112




            10112












            • I had same problem with Windows 7 and this solution of renaming + restarting worked for me! Thanks!
              – J.D.
              May 10 '15 at 20:10


















            • I had same problem with Windows 7 and this solution of renaming + restarting worked for me! Thanks!
              – J.D.
              May 10 '15 at 20:10
















            I had same problem with Windows 7 and this solution of renaming + restarting worked for me! Thanks!
            – J.D.
            May 10 '15 at 20:10




            I had same problem with Windows 7 and this solution of renaming + restarting worked for me! Thanks!
            – J.D.
            May 10 '15 at 20:10












            up vote
            7
            down vote













            Maybe try ActiveWndTrkTimeout. http://technet.microsoft.com/en-us/library/cc957203.aspx






            share|improve this answer





















            • I've added in an ActiveWndtrkTimeout entry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the old ActiveWndTrackTimeout but still no change either.
              – Idle_Mind
              Oct 26 '13 at 5:19










            • My registry started with a value called "ActiveWndTrackTimeout" which had no effect. When I renamed it to "ActiveWndTrkTimeout" it worked for me (Windows 7).
              – Dave L.
              Dec 26 '13 at 17:53















            up vote
            7
            down vote













            Maybe try ActiveWndTrkTimeout. http://technet.microsoft.com/en-us/library/cc957203.aspx






            share|improve this answer





















            • I've added in an ActiveWndtrkTimeout entry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the old ActiveWndTrackTimeout but still no change either.
              – Idle_Mind
              Oct 26 '13 at 5:19










            • My registry started with a value called "ActiveWndTrackTimeout" which had no effect. When I renamed it to "ActiveWndTrkTimeout" it worked for me (Windows 7).
              – Dave L.
              Dec 26 '13 at 17:53













            up vote
            7
            down vote










            up vote
            7
            down vote









            Maybe try ActiveWndTrkTimeout. http://technet.microsoft.com/en-us/library/cc957203.aspx






            share|improve this answer












            Maybe try ActiveWndTrkTimeout. http://technet.microsoft.com/en-us/library/cc957203.aspx







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Oct 25 '13 at 23:41









            Maciej Stachowski

            1712




            1712












            • I've added in an ActiveWndtrkTimeout entry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the old ActiveWndTrackTimeout but still no change either.
              – Idle_Mind
              Oct 26 '13 at 5:19










            • My registry started with a value called "ActiveWndTrackTimeout" which had no effect. When I renamed it to "ActiveWndTrkTimeout" it worked for me (Windows 7).
              – Dave L.
              Dec 26 '13 at 17:53


















            • I've added in an ActiveWndtrkTimeout entry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the old ActiveWndTrackTimeout but still no change either.
              – Idle_Mind
              Oct 26 '13 at 5:19










            • My registry started with a value called "ActiveWndTrackTimeout" which had no effect. When I renamed it to "ActiveWndTrkTimeout" it worked for me (Windows 7).
              – Dave L.
              Dec 26 '13 at 17:53
















            I've added in an ActiveWndtrkTimeout entry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the old ActiveWndTrackTimeout but still no change either.
            – Idle_Mind
            Oct 26 '13 at 5:19




            I've added in an ActiveWndtrkTimeout entry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the old ActiveWndTrackTimeout but still no change either.
            – Idle_Mind
            Oct 26 '13 at 5:19












            My registry started with a value called "ActiveWndTrackTimeout" which had no effect. When I renamed it to "ActiveWndTrkTimeout" it worked for me (Windows 7).
            – Dave L.
            Dec 26 '13 at 17:53




            My registry started with a value called "ActiveWndTrackTimeout" which had no effect. When I renamed it to "ActiveWndTrkTimeout" it worked for me (Windows 7).
            – Dave L.
            Dec 26 '13 at 17:53










            up vote
            1
            down vote













            Such an old question but still appears to be valid even for windows 10 (Seriously Microsoft you should fix it once and for all)



            I started window 10 with Windows 10 1703 (15063.1387 - I don't think these minors are important).



            I had configured:
            At path: HKEY_CURRENT_USERControl PanelDesktop
            value: ActiveWndTrackTimeout to 2000 (ms)



            After upgrade to Windows 10 1709 (16299.461) everthing stopped working again.
            I haved added a registry DWORD key ActiveWndtrkTimeout with the same value (leaving the old key there) and the raise delay started to work again.



            From the MSDN:




            ActiveWndTrkTimeout



            HKCUControl PanelDesktop



            REG_DWORD

            Milliseconds

            0




            0 is the default value.



            Note: I want to get one disinformation corrected



            There is also a registry entry MouseHoverTime at HKEY_CURRENT_USERControl PanelMouse. This entry does not change the window raise delay. It changes how fast are the taskbar information & preview shown.






            share|improve this answer

























              up vote
              1
              down vote













              Such an old question but still appears to be valid even for windows 10 (Seriously Microsoft you should fix it once and for all)



              I started window 10 with Windows 10 1703 (15063.1387 - I don't think these minors are important).



              I had configured:
              At path: HKEY_CURRENT_USERControl PanelDesktop
              value: ActiveWndTrackTimeout to 2000 (ms)



              After upgrade to Windows 10 1709 (16299.461) everthing stopped working again.
              I haved added a registry DWORD key ActiveWndtrkTimeout with the same value (leaving the old key there) and the raise delay started to work again.



              From the MSDN:




              ActiveWndTrkTimeout



              HKCUControl PanelDesktop



              REG_DWORD

              Milliseconds

              0




              0 is the default value.



              Note: I want to get one disinformation corrected



              There is also a registry entry MouseHoverTime at HKEY_CURRENT_USERControl PanelMouse. This entry does not change the window raise delay. It changes how fast are the taskbar information & preview shown.






              share|improve this answer























                up vote
                1
                down vote










                up vote
                1
                down vote









                Such an old question but still appears to be valid even for windows 10 (Seriously Microsoft you should fix it once and for all)



                I started window 10 with Windows 10 1703 (15063.1387 - I don't think these minors are important).



                I had configured:
                At path: HKEY_CURRENT_USERControl PanelDesktop
                value: ActiveWndTrackTimeout to 2000 (ms)



                After upgrade to Windows 10 1709 (16299.461) everthing stopped working again.
                I haved added a registry DWORD key ActiveWndtrkTimeout with the same value (leaving the old key there) and the raise delay started to work again.



                From the MSDN:




                ActiveWndTrkTimeout



                HKCUControl PanelDesktop



                REG_DWORD

                Milliseconds

                0




                0 is the default value.



                Note: I want to get one disinformation corrected



                There is also a registry entry MouseHoverTime at HKEY_CURRENT_USERControl PanelMouse. This entry does not change the window raise delay. It changes how fast are the taskbar information & preview shown.






                share|improve this answer












                Such an old question but still appears to be valid even for windows 10 (Seriously Microsoft you should fix it once and for all)



                I started window 10 with Windows 10 1703 (15063.1387 - I don't think these minors are important).



                I had configured:
                At path: HKEY_CURRENT_USERControl PanelDesktop
                value: ActiveWndTrackTimeout to 2000 (ms)



                After upgrade to Windows 10 1709 (16299.461) everthing stopped working again.
                I haved added a registry DWORD key ActiveWndtrkTimeout with the same value (leaving the old key there) and the raise delay started to work again.



                From the MSDN:




                ActiveWndTrkTimeout



                HKCUControl PanelDesktop



                REG_DWORD

                Milliseconds

                0




                0 is the default value.



                Note: I want to get one disinformation corrected



                There is also a registry entry MouseHoverTime at HKEY_CURRENT_USERControl PanelMouse. This entry does not change the window raise delay. It changes how fast are the taskbar information & preview shown.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 at 8:59









                tukan

                781213




                781213






























                    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.





                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f664351%2factivewndtracktimeout-value-being-ignored%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

                    AnyDesk - Fatal Program Failure

                    How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

                    QoS: MAC-Priority for clients behind a repeater