How to get context menu for 7-zip in App-V 5.0

1. Sequencing 7-zip version 9.2(64-bit) on App-v 5.0 SP2
2. unable to get context menu after publishing package.
3. installed hotfix for sequencer provided by Microsoft. but same results.
4. Is any way to sequence context menu.

2 Comments   [ + ] Show comments
  • When you use App-V 5.0 SP2,
    Shell extensions are embedded in the package automatically during the sequencing process. When the package is published, the shell extension gives users the same functionality as if the application were locally installed. Requirements for using shell extensions are already mentioned by Dunnpy - jagadeish 8 years ago
  • Thanks for the inputs.

    Using 64-bit sequencer.

    I have checked registry, its installed correctly.

    Inprocserver (Default) location is set to "7-zip.dll" with exact location.

    For App-V Client 5.0, is there any other registry need to configure before publishing package ? Which might be reason of not showing context menu. - akashrayban 8 years ago

Answers (3)

Answer Summary:
Posted by: dunnpy 8 years ago
Red Belt
Your sequence must be published globally and the 'bitness' of everything must match.

Therefore, if you're sequencing a 64bit application your Sequencer and App-V client on the target computer must also be 64bit (and of course the OS).

The AppxManifest.xml will have entries for the shell extensions  - you could verify they were picked up during sequencing to see whether you're experiencing a sequencing or a publishing issue.

Hope that helps,
Posted by: jagadeish 8 years ago
Red Belt
Can you check whether the following option is checked in your sequenced application

Start Menu-> Programs->7-Zip->7-Zip File Manager->Tools->Options->7-Zip

Integrate 7-Zip to shell context menu
Posted by: pratikpawar 8 years ago
Senior Yellow Belt

Top Answer

I believe you dont have to do anything special in app-v 5.0 for context menu.

refer the below link for 7zip recipe



  • Yes, followed same process. but I might be missing some other thing thus not getting proper output.

    It might be App-v client 5.0 configuration before publishing package. - akashrayban 8 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ