locked
App-V 5.1 HF2 & HF3 - Winzip 19.5 (x64) crashes if Office 2013 (x86) is also published RRS feed

  • Question

  • Just wondering if anyone has managed to sequence Winzip 19.5 x64 and run it successfully with Visio or Project 2013, published globally?

    The x86 version of Winzip doesn't crash (on exit), so this is the solution we've run with.

    OS: Windows 2008 R2. RDS Client

    Log Name:      Application
    Source:        Application Error
    Date:          15/06/2016 11:38:39
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mycomputer.com
    Description:
    Faulting application name: WINZIP64.EXE, version: 30.0.11532.0, time stamp: 0x55805045
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x00000000373b0838
    Faulting process id: 0x21c4
    Faulting application start time: 0x01d1c6f205ac6782
    Faulting application path: C:\ProgramData\Microsoft\AppV\Client\Integration\FFFFFFFF-E15F-4AE5-B301-C2E585C7E3DF\Root\WINZIP64.EXE
    Faulting module path: unknown
    Report Id: 520cf270-32e5-11e6-873f-00155d299e2c



    • Edited by TenBob Friday, June 17, 2016 2:40 PM
    Thursday, June 16, 2016 2:39 PM

All replies

  • Does this also occur with HF3?

    Simon Dettling | msitproblog.com | @SimonDettling

    Friday, June 17, 2016 4:54 AM
    Moderator
  • Does this also occur with HF3?

    Simon Dettling | msitproblog.com | @SimonDettling

    Thanks - I've just tried but no, it doesn't work either.
    • Edited by TenBob Friday, June 17, 2016 8:17 AM
    Friday, June 17, 2016 8:15 AM
  • Both hook in explorer if I'm correct. Try merging them in a connectiongroup.

    Roy Essers

    Friday, June 17, 2016 2:56 PM
  • Both hook in explorer if I'm correct. Try merging them in a connectiongroup.

    Roy Essers

    Thanks - that stopped the crashing.

    However, in my client's case, we can't group them up in a CG, so will have to use the x86 version as this doesn't exhibit the same behavior.

    Wednesday, June 22, 2016 11:28 AM