First some background: I have worked with MSI-packaging for a few years now and now I thought it was about time to look at appV.

I downloaded the sequencer and that I would give a go at sequence Gimp 2.6.11 on Windows 10 X64.
I used the standard exclusion list and installed in standard path. But when I try to launch the "AppV:d" Gimp on the same computer or another Windows 7 x64 the launcher complains about the file libgimpui-2.0-0.dll is missing.
I checked under C:\ProgramData\App-V\389DE69C-A6B4-47AF-A012-1E8CACE5E6BE\2A3E64FA-5171-4950-B45E-9E53E868461E\Root\VFS\ProgramFilesX86\GIMP-2.0\bin and there the file is in the correct path. I also renamed the .appv file to .zip and checked and the file is there as well.

If I copy this file to the "real" location under c:\\Program Files (x86)\... and launch the appv program again the launcher complains about another file in the same path. And so on ...
If I copy the whole "bin" folder to c:\Program Files (x86)\... the appv-package launches just fine. So it seems as if some files cant be read from the virtual directory even though they are there.

Does someone have a suggestion? Remember I´m totally new to appV and this is my first go at it. So go easy on me :)
0 Comments   [ + ] Show Comments


Please log in to comment



that sounds quite unusual.

When you did the sequencing did you read the info boxes displayed about files excluded from the package?? Was there a warning about any d COM??


If you are sure the files are there, trying launching a CMD from the virtual environment. then run the GIMP exe from the 'virtual CMD' and see what happens.

Answered 03/14/2016 by: Badger
Red Belt

  • Yes running the gimp exe from a cmd from the virtual environment worked fine. Like this: cmd.exe /appvve:ProductID_VersionID. Can I create a shortcut that works or what is the final "solution" so to speak. I don´t really understand why it works if I launch it using a command line as "man in the middle".
    • So i did this last night and got the same result, somehow my reply got lost. Running it from the virtual CMD made no difference for me.
    • I would re sequence this, and during sequencing, create a shortcut to cmd.exe /c "C:\Program files(x86)\GIMP\gimp.exe. The sequencer will then create a shortcut that will load the virt env then launch your app. You will however see the CMD pop up briefly. You can do this in the XML file. If you comfortable with XML and App-V.
      • I reverted the snapshot of the virtual machine that hosts the sequencer and redid the sequencing process creating the shortcut as you suggested. However now it doesn´t work. Same error messages and manually opening up a cmd window in the bubble and executing gimp.exe-process renders the same errors.
        Last time I didn´t revert the snapshot and created another sequencing of Gimp. Perhaps something i did there made it work when executing gimp from command line from within the bubble. Very strange.
        Oh well ... It´s not cruicial that I get this to work. I just want to start packaging using AppV and thought Gimp would be a good application to practice on.
      • I tried sequencing again with the latest version of Gimp 2.8.X and it worked just fine without hassle. The installer choosed the x64 version so there is a difference from the older x86-2.6 version I tried before. It that could have an impact of some sort.
      • my comment that got lost did say, maybe try another app, or a newer version. Glad to hear the newer version worked ok.
        Have fun
  • Just to be clear: In the "bubble" I ran "C:\Program filex (x86)\GIMP\gimp.exe". (outside of the bubble the "real" folder is renamed into "GIMP - copy")
Please log in to comment

Try launching the shortcut inside the virtual bubble and see (Like Badger said)

For reference see here - http://app2pack.blogspot.com/2016/03/issue-with-sequenced-sap-gui-740-unable.html

Answered 03/15/2016 by: apptopack
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity