New
#11
Last edited by Brink; 20 Jan 2010 at 23:27. Reason: removed unneeded comment in quote
I'm probably going to end up formatting the disk and reinstalling Windows 7 from scratch... but I'd still like to find a fix for this, because it is quite irritating.
Your processes are full of crapware - have you cleaned out the rubbish HP put on it, and from your msconfig tab? You can use Autoruns too for the startup entries.
hmm...
I don't know if this helps but, go in the Start Menu then search Aero.
The 3rd entry should be "Find and fix problems with transparency and other visual effects". Click on that entry. Click next. Windows will now search for Aero problems. If it finds some, the window will show the problems. Accept the changes. Report back if it's working or not. :P
(more in depth article here : How to Turn On and Enable Aero in Windows 7 (Enable Aero Peek) My Digital Life )
Unfortunately, that did not work, it reports "issue not present" for everything.
I ran sfc /scannow and it returned that it found corrupt files and that they would be repaired when I reboot. It output CBS.log but I seem to be denied access to it (I am the administrator though...).
I'm gonna do a reboot in a sec.
EDIT:
Nope, I rebooted but nothing is different. Should I post the log file? It's around 4 MB...
Any ideas on how to track what is causing Desktop Composition to become disabled immediately, or never become enabled? As in, I check the "Enable Desktop Composition" box and click Okay, and then view the settings again and it is immediately disabled.
Last edited by Gumgo; 21 Jan 2010 at 04:44.
Well, I did a system restore, which "worked" I suppose... still don't love the idea of this being the only solution, but whatever... I'm probably going to reinstall windows without all the HP stuff pretty soon anyway, once I get a CD drive.
Never mind. System restore worked for a little bit, but only restored the transparency effects and such, and flip 3d, not the actual look of the windows.
And just now I tried switching back to basic and then back to aero, and the same problem occurred. So it seems that it ins't a program causing this, but rather there's a bug which prevents ever returning to aero!