Fix - Catalyst Control Center - CCC - will not open/install

Description of problem: Ati Catalyst Control Center will not open or install in windows 7.

Resolution follows:


Preparation:
Note - As with anything that makes changes to your system it is suggested you create a restore point before proceeding. System Restore Point - Create


Before beginning:
First thing we are going to do is download the latest amd/ati driver and catalyst package and save it to your desktop for easy access later. http://support.amd.com/us/gpudownload/Pages/index.aspx the link provided there will direct you to the proper download for your hardware.

Once this is done
Remove your ATI software normally through programs and features in the Control Panel using the Catalyst Install Manager (CIM). (Also called AMD Catalyst Install Manager)




Reboot the system in Safe Mode (F8) and do the following:

1 - Delete all ATI folders in C:\programs files and C:\programs files (x86) as well as the temp ati folder usually located at c:\ati

2 - Go to C:\Windows\assembly and sort by "Public Key Token". Locate the following Public Key Token "90ba9c70f846762e" Usually there are only two entries. However, there can be many just be careful here we are only deleting/uninstalling entries tagged with the "90ba9c70f846762e" token. (if deletion will not work right click and uninstall)

3 - deleting these policies in safe mode may result in a permissions error. The entries will only show up in systems affected by this issue.
This means that searching for these entries on systems where CCC is loading properly, should result in none found *(as per ati's dev team)

4 - Shut down and re-start normally.

5 - Reinstall the ATI Catalyst package.

6 (optional) -Launch CCC from the right click context menu if it doesn't start automatically.

______________________________________________________________
Footnote: there should only be two policies, but 20 to 40 have been reported. Apparently the problem multiplies when you attempt multiple installations to get catalyst to appear.

Apparently the policies have a lot to do with the problem, and they start multiplying. It has something to do with a .net framework fault apparently. Once it occurs removing the policies is the only way to 'reset' the installation process.
I'm not going to pretend I understood everything in the dev log the ati guys shared, but driver sweeper doesn't go after those policies (it can't remove them has to be done manually, since it's a specific policy key perhaps it can be included in a future driver sweeper version)
I'm going to pretty this up so we can tutorial it.

notice the notes, the keys should NOT appear if catalyst is working properly. I'm still working on the post. It'll likely be sometime tomorrow when it's ready for open consumption. Needs some screens and other things to straighten it out. Only problem is now that I've fixed it on my system the policy is gone so I can't screen that.
Rage is actually one of the multiple sources I used for this, all those crazy steps and things people are suggesting and finally work, are just them trying to use various methods to clean the policy.

Yes, I've run into the problem on 2 more occasions since writing this fix, I found 39 and another with over 200, so the number of them does apparently vary significantly. Just so long as you are careful to only delete policies identified by the key token 90ba9c70f846762e everything should be good though.