Taskbar buttons don't bring active window to the front

  • Thread starter Thread starter Guest
  • Start date Start date
I found the problem on my machine. I'm running a little utility called
"FreeRAM XP Pro",
Click to expand...

Why do you feel that you need this program at all?

Windows XP will use whatever ram it feels is necessary and does not need any
3rd party programs to help.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
I am no computer expert, but I tried this fix AND it stopped the
taskbar buttons problem BUT deleted all of my "startup notifications"
on my taskbar - which may not have been such a big deal, but I have to
access the DLInk button to "rescan" and activate my wireless
connection. I tried to activate DLink from the program file and
created a desktop shortcut - but was unable to activate.

I ended up having to system restore - it was during this restore that
I noticed that on April 17th Microsoft "Software Distribution Service
2.0" was apparently automatically installed. It was also around this
time that I encountered the taskbar button problem.

I restored to the system checkpoint immediately preceding April 17th
AND was able to restore my notifications AND it eliminated the taskbar
button problem.

I also found this link that discusses more problems created by "SDS
2.0":

http://www.computing.net/windowsxp/wwwboard/forum/132337.html
 
Now that you mention it, the fix did cause a side effect on the task bar. My
startup notifications were unaffected, but my quick launch task bar was
turned off. It was easy to turn it back on from the Toolbar option of the
task bar pop-up menu.

Regards,

Barry
 
I solved the problem of flashing orange buttons on the taskbar and windows not
getting to the front by changing the
HKCU\Control Panel\Desktop\ForegroundLockTimeout to 10 and loggged off /on
It had somehow been set to zero and not the default value of 200000

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/55199.mspx?mfr=true

However, something is setting it back to zero after it has been read at logon, so
next time you logon, the problem is back :(

- Jørgen

- Jørgen
 
Hi Guys,

I reckon I've got a fix - at least for me. It seems that my install of
Norton was intefering with XP somehow. How many of you are using Norton?
Anyway, if I de-activate the Norton stuff from startup services in MSConfig,
the problem is gone. I'm currently uninstalling Norton and will re-install
it to see if it fixes the problem.

I too had just done a complete system reinstall - it seems that the Norton
and Xp updates that were going crazy caused a conflict somewhere (registry??)
which caused the problem.

Another temporary fix for me was to do a system restore (didn;t matter if
the problem was current) and then restore to the point just created. That
always fixed the problem - for a little while....

I hop this has helped someone else besides me.
 
Back
Top