Resolved Icon in taskbar is brightened

I just reinstalled Windows 7 and I'm seeing behavior I've never noticed before. When I minimize a program to the taskbar, it is brightened a little bit--until I pass the cursor over to another program.

When I've mimized browsers in the past, and seen that highlighted icon, I've always thought that some action was completed, such as some new email in my inbox, or a page finished loading, or something. But I see that this effects all the icons, not just for my browser.

Is there a way to disable the brightening effect for the last used program, in the taskbar?

 

Thanks for the reply, Evan. I just did a pretty big update with Windows (thought I had already, but did another one and there were hundreds of megs). After a reboot I cannot see it. A similar problem (tooltips for icons on the taskbar that my cursor hovers over and leaves, will stay visible for several seconds after the cursor leaves) also at this point is no longer present.

I read online that this might be caused by out of date video drivers, but the AMD installation package insists that my video driver is up to date. I'll go ahead and reinstall it if the various Windows updates (that I just installed) don't work.

I'll post back in a day or two if this doesn't work.

 

Mine has always been that way on several PC's that I have. Kind of like a reminder that it is OPEN and not just sitting there.

 

Doesn't happen for me, but I'm using the Classic shell, so maybe that has something to do with it.

 

What advantage do you have using Classic Shell in Win 7? Win 8 I can understand as I use it there.

 

Because, in combination with other Win7 tweakers, it allows me to make Win7s UI look and behave the way I want it to.

IMHO, The best UI the Gnomes of Redmond ever produced was the one for Win9x. Those for subsequent versions of Windows have become increasingly complicated while, at the same time, dumbed down. Apparently, others feel the same.

 

I have yet to see this issue after my updates earlier this week, so I'm assuming it was somse Windows update that fixed this. Marking as solved.