App-V Internet Explorer Add-on Conflict: Watch those Registry Keys
Students run into this problem in our App-V training classes every time.
In one of the labs we deal with creating and deploying a handful of browser plugins in a connection group. And everyone runs into an issue of some of them seemingly not working. The lab specifies a set of plug-ins to use, but I usually encourage students to work off-script and sequence from a bigger set I have available or download something they use at work. Typically, they sequence a bunch of add-ons, running a smoke test on each to verify operation. Then, when they place them in a connection group, some don’t appear in the browser.
The problem happens due to created registry keys. Add-ons to the Internet Explorer are registered via one of several registry keys, by adding in a subkey with the appropriate information. But out of the box, the naked OS does not have the base keys that you register under. Thus, when you install the plug-in it creates the base key along with its subkey, both of which are then marked as “Override Local” keys.
In particular, I have noticed the following keys (under HKLM or HKCU):
Read the entire article here, App-V Internet Explorer Add-on Conflict: Watch those Registry Keys