Taskbar button glow doesn't go away

[SubGum]

When I mouse over the taskbar buttons, the glow doesn't go away after I move the mouse away. This doesn't happen all the time, but seems to always pop up eventually on every boot, and persists until I restart.

It's done this across several gpu driver updates, so it must be something with Win7.

I found this old thread here but the link they had to fix it is no longer there, and I can't find any info elsewhere on this.

Anyone know how to fix this problem?

 

[James Colbert]

Hi SubGum,

Welcome to the forums. . Can't give you the sig link you refer, but if you've updated your video drivers, you may want to try adjusting Visual Effects settings, as per this post:

http://www.sevenforums.com/general-discussion/119865-right-mouse-click-bug.html#post1031656

The specified setting to the OP of that thread may not apply to you, but there are many other settings that may resolve your problem. Just try the ones that seem logical and click apply, then mouse over a button to see if it helps. Worth a try...

James

 

[SubGum]

Thanks for the welcome and the reply, James!

I'm not having any setting problems, but rather am experiencing a bug that persists regardless of the settings I choose.

In fact, by messing around with the visual performance settings as you suggested, I found that even with visual themes disabled completely (reverting to the old school gray taskbar look), the bevel on taskbar buttons that shows while the mouse is over them still doesn't go away, so it's not just the aero glow effect.

So yeah... I don't know what else to do about this...
Any other ideas?

 

[James Colbert]

Are you using any 3rd party themes or tweaks (StarDocker, WindowBlinds, Taskbar Tweaker, etc.)?

James

 

[SubGum]

No. I do use Rocket Dock but I do so independently of the taskbar.
My taskbar itself is completely vanilla.

EDIT: Also, this problem existed before I ever used Rocket Dock.

 

[FliGi7]

I find this sometimes happens to me, too. I just chalked it up to a bug.

 

[Totenschlaggh]

You can fix it by restarting the explorer.exe via task manager. However, this must be done every time the problem occurs.

 

[SubGum]

You can fix it by restarting the explorer.exe via task manager. However, this must be done every time the problem occurs.

Right, but that certainly doesn't seem like a real solution... :huh:

 

[Jacee]

There's a 'start button changer' app that you can download Change Windows 7 Start Orb with Windows 7 Start Button Changer | The Windows Club

 

[SubGum]

There's a 'start button changer' app that you can download Change Windows 7 Start Orb with Windows 7 Start Button Changer | The Windows Club

It doesn't effect the Start Button for me, only the taskbar buttons.

 

[James Colbert]

It seems to be a rather unique issue for which there isn't much info. Assuming this has been happening too long for a System Restore to be helpful, I think my next move, after creating a partition image (preferable) or creating a restore point would be to run SFC:

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

You may or may not be aware that if you've changed any system files yourself (via hack or workaround), allowing SFC to repair your system files may cause those changes to go away.

If this corrects your problem, if you find that some workarounds, etc need to be 're-asserted', do them one at a time, allowing enough time in-between for the problem to recur before moving to the next (same for any reinstalls).

James

 

[SubGum]

It seems to be a rather unique issue for which there isn't much info. Assuming this has been happening too long for a System Restore to be helpful, I think my next move, after creating a partition image (preferable) or creating a restore point would be to run SFC:

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

You may or may not be aware that if you've changed any system files yourself (via hack or workaround), allowing SFC to repair your system files may cause those changes to go away.

If this corrects your problem, if you find that some workarounds, etc need to be 're-asserted', do them one at a time, allowing enough time in-between for the problem to recur before moving to the next (same for any reinstalls).

James

Wow, that's sounds like a terrifyingly complicated solution.
I will certainly keep this as as a reference if I get really desperate to fix it, but I don't think I'm quite ready for that yet!

 

[James Colbert]

Wow, that's sounds like a terrifyingly complicated solution.
I will certainly keep this as as a reference if I get really desperate to fix it, but I don't think I'm quite ready for that yet!

It sounds more complicated than it actually is. You may feel a bit intimidated by option two, but the need for that may never arise. The only reason to do it is if SFC can't correct all errors, and even then, I've had systems in which all the errors couldn't be corrected (the errors are actually just changes in system files), but it had no ill effect on the machine.

IOW, option one is all you would really need to do, if you feel comfortable with it. Just input the one command, let it run and see if it had errors or if any were unable to be repaired. It may not even correct your problem. The truth is, your issue is not something that can't be lived with. If you get to the point where you feel that SFC is an option you would try, someone will be around here to help you through it.

In the interim, someone my come up with a viable solution.

James