none
Solution for Catalyst Control Center (CCC) CLI.Implementation PublicKey Token=90ba9c70f846762e issue RRS feed

  • Question

  • Mods, please move this if it belongs in the Hardware or Applications forums.

    I struggled with this problem for quite a bit before putting all the pieces together.  The AMD/ATI tech article has bogus advice to uninstall all .NET versions and reinstall them, which has nothing to do with the problem.  The guts of the solution come from user "Crossfire" at www.hardwareheaven.com.  I'm posting here in hopes of getting it together in a single post on a Microsoft forum that will turn up readily in a search.

    Symptom:  When trying to install, or perhaps run, a CCC update, the install or launch errors with "Assembly CLI.Implementation, Version=2.0.2589.34531, Culture=neutral, PublicKeyToken=90ba9c70f846762e".  In some contexts the reference may be to MOM.Implementation.  Same issue.

     

    Boot safe mode (this is important, in particular for the GAC purge in step 3).  Uninstall all ATI packages.  Then:

    1. Check that these registry locations are empty (delete all entries below them if found):
    a. HKCU/Software/ATI/ACE
    b. HKLM/Software/ATI/ACE
     
    2. Check that (Program Files folder )/ATI Technologies/ATI.ACE is empty. Delete any files/subfolders found.
     
    3. Check (Windows folder)/Assembly folder to see if there's any files with Public Key Token of "90ba9c70f846762e" (Sort by Public key token to get a easier view). All these tokens should be uninstalled by right clicking and uninstalling. You can highlight the range and right click the highlight, there may be hundreds.

    4. Check that (Document and Settings)/(User)/AppData/Local/ATI/ACE is emptyDelete any files/subfolders found.

    5. Reboot normal mode.  Reinstall CCC. You can use the ATI Installation Manager or just the *.dd.ccc.ocl.exe package that it downloads.

     

    This worked perfectly for me on a Windows 7 system recently express upgraded from Vista.  Judging from other posts, it should work with Vista as well.

    Thursday, December 29, 2011 11:16 PM

Answers

  • Hi,

     

    Thanks for sharing. We really appreciate your time and efforts. Hope your experience will help other community members facing similar problems.


    Leo Huang

    TechNet Community Support

    Wednesday, January 4, 2012 7:34 AM
    Moderator

All replies

  • Hi,

     

    Thanks for sharing. We really appreciate your time and efforts. Hope your experience will help other community members facing similar problems.


    Leo Huang

    TechNet Community Support

    Wednesday, January 4, 2012 7:34 AM
    Moderator
  • Mudgen,

    I also wanted to thank you personally for posting this solution.  I was having the identical problem involving a conflict that developed between AMD/ATI Catalyst/CCC update software and Windows XP.  It began following a recent Windows Update and an AMD driver update.  I also followed the recommended AMD advice to uninstall all .Net Framework versions before uninstalling AMD/ATI software to correct the problem.  This did not make a difference and I continued to experience the MOM.Implementation error message with every restart. 

    However, by following your step by step instructions, I was able to finally overcome solve this annoying problem which has perplexed me for a week despite research and trying a half-dozen recommendations by others.  Also wanted to let folks know this worked even on the long in the tooth XP OS. 

    Thanks again for posting what worked for you.  It is still helping folks 14 months later!

    Waldo

    Monday, April 1, 2013 12:44 PM
  • This worked perfectly for me on a Windows 7 system recently express upgraded from Vista.  Judging from other posts, it should work with Vista as well.
    Just to confirm this does work well for Vista, too.  I also was very frustrated in not finding a straight-forward remedy to this very problem until reading this post.  Thank you very much.

    • Edited by art.hart Sunday, November 10, 2013 4:31 AM
    Sunday, November 10, 2013 4:30 AM
  • Followed the .NET uninstall solution, but did not fix the problem untill cleaned everything as instructed above.

    Thank you very much!

    Tuesday, December 17, 2013 9:02 PM