Taskbar button glow doesn't go away

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:

SFC /SCANNOW Command - System File Checker

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

James Colbert said:

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:

SFC /SCANNOW Command - System File Checker

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!

SubGum said:

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