I’ve been contacted regarding this issue more than once and it even happened to me a couple of weeks ago. This can be a very frustrating issue because the cause isn’t the Catalyst Control Center program itself and a uninstall/driver sweep will not fix it.
There are a few tutorials on the web about resolving this problem but it seems that people still don’t know where to turn when the issue hits. Just spreading the know-how.
- Catalyst Control Center will not start
- Usually (not necessarily) a error is thrown: Could not load file or assembly ‘CLI.Implementation
- Errors are thrown when trying to start CCC manually (CCC.exe)
Cause of the Problem:
The solution is rather simple but first let’s see what’s causing the issue in the first place. Microsoft’s .NET FrameWork is the cause of the problem, because Catalyst Control Center is a .NET app when DotNetFX installation gets corrupted CCC will not work properly if at all. Other .NET dependent software should also stop working but because just parts (assemblies) of .NET can get corrupted only a few apps (dependent on that assembly) will be affected.
Now that we now that Microsoft’s .NET FrameWork is the culprit, here’s how to fix it:
Basically what we need to do is uninstall the .NET FrameWork and reinstall it. There are a couple of ways to do this, one would be using the Windows Features but I won’t trust MS that this will completely wipe the app so we are going to use Aaron Stebner’s Automated Cleanup Tool which will do a proper job.
1. Download the above tool and run it.
2. Select the corresponding OS and make sure it says “All Versions”.
3. Hit the Cleanup Now button.
4. When the tool is finished restart and install DotNetFX 4.0 (or the latest version of the .NET FrameWork)
5. Uninstall any AMD Catalyst software, preferably using a Driver Sweeper.
6. Install whichever Catalyst you need/want.
7. Enjoy a fully functional Catalyst Control Center.