Aero problem

[rgritton]

So, I have a Win7 Enterprise system that started with a WD Scorpio Black 500Gb hard drive. After having a couple of bad sector failures in the boot area and repairing these problems (chkdsk), I purchased a Seagate Momentus 500Gb hard drive with the same rpm and cache values. I used Acronis True Image to clone the WD drive to the Seagate. The Seagate has the Aero problem, the WD drive does not. If I go into Services and stop/start the Themes service, it is fine. The display response to a right click in either mode seems pretty darn slow with the Seagate. Don't know why either of these problems should be problems. Any help?

-- Update --
Right after posting (naturally), I had a handful of Configuration Management updates that needed installing. Most were .Net4 related. After restarting to install those updates, the Aero environment started up just fine. It seems like I saw a similar fix response to this problem on another forum somewhere today.

-- Yet another update --
So I rebooted this morning and the problem is back. I have disabled the LogMeIn services - no change, I have created a local user account which seems to work okay but I don't have a lot of start up stuff in it obviously as it was just created.

What I don't get is why changing hard drives would make this difference. I had researched the specs beforehand and both have similar specs. What in the cloning process would have messed things up?

 

[A Guy]

Welcome to Seven Forums rgritton. The drive should make no difference, so the cloning would be more suspect. Try running the System File Checker and see if that doesn't help.

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

A Guy

 

[rgritton]

I had run the System File Checker with no errors/warnings. The thing that I found/find most disconcerting is the difference in the registry hives, particularly the HKLM hive. It is almost twice the size after rebooting with the new drive versus the old with the same hardware (apart from the drive). I am not thinking the drive is the issue but nothing explains why a disk clone would wreak that much havoc on a setup. Unless something was corrupted in the registry or driver setup area of the drive that was cloned. But not enough to cause most everything to fail.

Thank you for your input.

I received a newly imaged drive from our IT group and am "busy" rebuilding the system that way...