R
Ron
If you're reading this, I presume you know about the GAC. (I didn't until a
few days ago
) Most references I find on the GAC talk about adding
libraries to it. My questions relate to removing some.
I have a problem installing the interface utility for a video driver
update - the utility (ATI's Catalyst Control Center) installs, but doesn't
run more than a second or two. (Using Sysinternals ProcMon), I think it's
because it can't find the dll's it wants. It's been a known issue for a few
users for years - discovered when they go to update ATI video drivers - and
I've found references where some users have in fact succeeded in getting the
utility to work by uninstalling, simply deleting all libraries from the GAC
that have the ATI (now AMD) public key, then reinstalling. But I have 190
such entries in there (many associated, presumably, with other AMD
functionality on my computer). I've learned how to unlock the
Windows\Assembly directory so it behaves normally in Windows Explorer, and
so I could in fact remove the libraries I believe are associated with just
the problematic installation - to see if it will then install and run
properly. I count five that are relevant. (If you know ATI video drivers,
the libraries appear related to CCC.exe and MOM.exe.) As mentioned, others
have reported success doing this. However, being cautious, I'm wondering:
1. Is the GAC one of the directories tracked by System Restore?
2. If I delete a particular library, using the win explorer context menu,
can it in fact be restored to its former functionality? (I've read a bit
about something called the "manifest" which apparently does bookeeping on
the GAC.)
3. If I manually move libraries from the GAC to a temp directory, can I
simply move them back to restore their functionality if my approach fails?
4. Is there an accepted method of testing whether a particular program
issue is in fact traceable to a rogue library in the GAC?
5. How royally could I pooch my computer by removing the wrong libraries?
The GAC is presumably a dangerous place to mess around - otherwise why would
they lock it in default configuration. Any comments or links about tweaking
it - insights, links, etc. - would be appreciated. If important, I'm
running Win7pro x64 with all updates, including the recent .NET 4.0.
Thanks for any help.
few days ago
libraries to it. My questions relate to removing some.
I have a problem installing the interface utility for a video driver
update - the utility (ATI's Catalyst Control Center) installs, but doesn't
run more than a second or two. (Using Sysinternals ProcMon), I think it's
because it can't find the dll's it wants. It's been a known issue for a few
users for years - discovered when they go to update ATI video drivers - and
I've found references where some users have in fact succeeded in getting the
utility to work by uninstalling, simply deleting all libraries from the GAC
that have the ATI (now AMD) public key, then reinstalling. But I have 190
such entries in there (many associated, presumably, with other AMD
functionality on my computer). I've learned how to unlock the
Windows\Assembly directory so it behaves normally in Windows Explorer, and
so I could in fact remove the libraries I believe are associated with just
the problematic installation - to see if it will then install and run
properly. I count five that are relevant. (If you know ATI video drivers,
the libraries appear related to CCC.exe and MOM.exe.) As mentioned, others
have reported success doing this. However, being cautious, I'm wondering:
1. Is the GAC one of the directories tracked by System Restore?
2. If I delete a particular library, using the win explorer context menu,
can it in fact be restored to its former functionality? (I've read a bit
about something called the "manifest" which apparently does bookeeping on
the GAC.)
3. If I manually move libraries from the GAC to a temp directory, can I
simply move them back to restore their functionality if my approach fails?
4. Is there an accepted method of testing whether a particular program
issue is in fact traceable to a rogue library in the GAC?
5. How royally could I pooch my computer by removing the wrong libraries?
The GAC is presumably a dangerous place to mess around - otherwise why would
they lock it in default configuration. Any comments or links about tweaking
it - insights, links, etc. - would be appreciated. If important, I'm
running Win7pro x64 with all updates, including the recent .NET 4.0.
Thanks for any help.