ActiveWndTrackTimeout Value Being Ignored
up vote
10
down vote
favorite
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:
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
edited Oct 26 '13 at 7:12
harrymc
248k10257548
asked Oct 23 '13 at 17:09
Idle_Mind
10116
add a comment |
up vote
10
down vote
favorite
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:
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
edited Oct 26 '13 at 7:12
harrymc
248k10257548
asked Oct 23 '13 at 17:09
Idle_Mind
10116
add a comment |
up vote
10
down vote
favorite
up vote
10
down vote
favorite
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:
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
edited Oct 26 '13 at 7:12
harrymc
248k10257548
asked Oct 23 '13 at 17:09
Idle_Mind
10116
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:
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
windows-8
edited Oct 26 '13 at 7:12
harrymc
248k10257548
asked Oct 23 '13 at 17:09
Idle_Mind
10116
edited Oct 26 '13 at 7:12
harrymc
248k10257548
asked Oct 23 '13 at 17:09
Idle_Mind
10116
edited Oct 26 '13 at 7:12
harrymc
248k10257548
edited Oct 26 '13 at 7:12
harrymc
248k10257548
edited Oct 26 '13 at 7:12
harrymc
248k10257548
248k10257548
asked Oct 23 '13 at 17:09
Idle_Mind
10116
asked Oct 23 '13 at 17:09
Idle_Mind
10116
asked Oct 23 '13 at 17:09
Idle_Mind
10116
10116
add a comment |
add a comment |
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.
answered Aug 28 '14 at 9:52
Nicolau
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
add a comment |
up vote
7
down vote
Maybe try ActiveWndTrkTimeout. http://technet.microsoft.com/en-us/library/cc957203.aspx
answered Oct 25 '13 at 23:41
Maciej Stachowski
1712
I've added in anActiveWndtrkTimeoutentry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the oldActiveWndTrackTimeoutbut 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
add a comment |
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.
answered Nov 22 at 8:59
tukan
776213
add a comment |
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.
answered Aug 28 '14 at 9:52
Nicolau
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
add a comment |
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.
answered Aug 28 '14 at 9:52
Nicolau
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
add a comment |
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.
answered Aug 28 '14 at 9:52
Nicolau
10112
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.
answered Aug 28 '14 at 9:52
Nicolau
10112
answered Aug 28 '14 at 9:52
Nicolau
10112
answered Aug 28 '14 at 9:52
Nicolau
10112
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
add a comment |
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
add a comment |
up vote
7
down vote
Maybe try ActiveWndTrkTimeout. http://technet.microsoft.com/en-us/library/cc957203.aspx
answered Oct 25 '13 at 23:41
Maciej Stachowski
1712
I've added in anActiveWndtrkTimeoutentry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the oldActiveWndTrackTimeoutbut 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
add a comment |
up vote
7
down vote
Maybe try ActiveWndTrkTimeout. http://technet.microsoft.com/en-us/library/cc957203.aspx
answered Oct 25 '13 at 23:41
Maciej Stachowski
1712
I've added in anActiveWndtrkTimeoutentry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the oldActiveWndTrackTimeoutbut 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
add a comment |
up vote
7
down vote
up vote
7
down vote
Maybe try ActiveWndTrkTimeout. http://technet.microsoft.com/en-us/library/cc957203.aspx
answered Oct 25 '13 at 23:41
Maciej Stachowski
1712
Maybe try ActiveWndTrkTimeout. http://technet.microsoft.com/en-us/library/cc957203.aspx
answered Oct 25 '13 at 23:41
Maciej Stachowski
1712
answered Oct 25 '13 at 23:41
Maciej Stachowski
1712
answered Oct 25 '13 at 23:41
Maciej Stachowski
1712
answered Oct 25 '13 at 23:41
Maciej Stachowski
1712
1712
I've added in anActiveWndtrkTimeoutentry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the oldActiveWndTrackTimeoutbut 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
add a comment |
I've added in anActiveWndtrkTimeoutentry but it makes no difference, the windows switch immediately and ignore the value in the registry. I also tried removing the oldActiveWndTrackTimeoutbut 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
add a comment |
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.
answered Nov 22 at 8:59
tukan
776213
add a comment |
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.
answered Nov 22 at 8:59
tukan
776213
add a comment |
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.
answered Nov 22 at 8:59
tukan
776213
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.
answered Nov 22 at 8:59
tukan
776213
answered Nov 22 at 8:59
tukan
776213
answered Nov 22 at 8:59
tukan
776213
answered Nov 22 at 8:59
tukan
776213
776213
add a comment |
add a comment |
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%2f664351%2factivewndtracktimeout-value-being-ignored%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
