App-V package with Excel plugin, howto make the plugin available in Excel (physical package)? RRS feed

  • Question

  • Hi,

    Users have this application which we sequenced. However, this App-V package has an Excel plugin. When users work in Excel, NOT via App-V package, it won’t launch but throw an error. Is there a way to solve this so the plugin is available at any time?


    Jan Hoedt

    Thursday, March 10, 2016 4:58 PM


All replies

  • You can create an extra shortcut for excel so that addin will be loaded.

    If you don't want to create an extra shortcut, you can use Run Virtual or /appvve: for local excel to load in the App-V package virtual environment.



    (Please click on Vote as Helpful and/or Mark as Answer, if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    • Proposed as answer by Roy Essers Thursday, March 10, 2016 10:02 PM
    • Marked as answer by janhoedt Monday, March 14, 2016 12:31 PM
    Thursday, March 10, 2016 5:08 PM
  • You can check my blog link below for reference.


    (Please click on Vote as Helpful and/or Mark as Answer, if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    Tuesday, March 15, 2016 4:38 AM
  • General method:

    1. Create a dummy empty package (I think it needs at least one empty folder in order to work).
    2. Configure RunVirtual to launch Excel (and maybe other Office apps) in the bubble of that dummy package.
    3. Create a connection group to link your Excel add-in with the dummy package.


    1. The connection group can be mixed user/global targeted, and RunVirtual can be HKLM or HKCU. However the dummy package must be published to the user if using HKCU RunVirtual, and globally id using HKLM RunVirtual.
    2. If your add-in is an automation add-in that is launched via the OPEN1/OPEN2/etc keys then you will need to take extra steps to make sure these don't clash with other add-ins. One method is to put a config package higher up in the priority order so that it overwrites the values from the other packages, and set the correct order of keys in there.
    3. All your packages in the group need to have the same COM / Named Object virtualisation settings (those checkboxes in the advanced tab). You can leave them as default if you accept the risk that one day you might find an add-in that needs those settings changed which forces you to go back and modify all the previous packages.
    4. If you are running Excel in a virtual environment but none of the other Office apps, you may experience some integration issues that might be solved by adding other Office apps to the same RunVirtual bubble.

    Dan Gough
    Microsoft MVP (Windows and Devices for IT)

    Blog | Twitter | LinkedIn

    Tuesday, March 15, 2016 10:31 AM
  • Thanks but that's quite a big workaround as approach. Can you clarify where you got it from (official procedure/reference)?

    Jan Hoedt

    Wednesday, March 16, 2016 12:13 PM