In this post I am going to explain how to virtualize Adobe PhotoShop CS5 using Microsoft App-V 5.0.

I face the following challenges:

  • Running a configuration script when the package starts to configure full control in the virtual environment (to prevent error: 16 from showing up).
  • Disabling the Adobe update feature.

Error :16 shows up if the package is packaged default and not modified:

Configuration errorPlease uninstall and reinstall the product.If this problem still occurs, please contact Adobe technical support for help, and mention the error code shown at the bottom of this screen.Error: 16


Let’s start.

Start the App-V 5 sequencer.Click on Create new Package

Enter the package name and the installation folder.Click Next
Start the Adobe PhotoShop CS5 installer. image
Click Accept image
Enter the serial number.Click Next image
Change the installation path to the Primary Virtual Directory path. image
Wait for the installation to finish. image
Click Done image
Under C:\Program Files\Common Files\Adobe\AAMUpdaterInventory\1.0 create a file AdobeUpdaterAdminPrefs.dat Enter the following code:<?xml version=”1.0″ encoding=”UTF-8″ ?>    <Preferences><Suppressed>1</Suppressed>


This will disable the update feature(s).

PasteBin URL

After the installation, Adobe Bridge becomes the default Explorer tool and every time I double clicked on a folder it would open with Adobe Bridge. This is not what I want so I removed the registry key:Open the registry editor and navigate to HCR\Directory\shell\Bridge Remove the Bridge folder.
Bridge is now removed as default Explorer tool and Explorer will be the default application to navigate through folders. image
Select I am finished installing. image
Wait for the system to collect the changes. image
Click Next image
Click Customize Click Next image
Select Force Applications to be fully downloaded before launching. Click Next image
Select the operating system where the package can be started. image
Select Continue Click Next image
Click Close image
This step is optional:Click on Package Files Remove the folder Package\Root\VFS\Windows\Installer  This is the MSI cache folder for repair.Removing the MSI cache will reduce the size of the App-V package and this will speed up streaming of the application to the client. image
There are a lot of articles and tips how to resolve error –16. The advice is to apply modify rights on folders. In App-V 5 the modify rights have changed and NTFS rights set during sequencing are not saved. So setting rights is not very easy to do. I was able to resolve error –16 to using the VFSCACLS.VBS from Packageology. This gives you full control on the folder: %localappdata%\Microsoft\AppV\Client\VFS\
I also tried this PowerShell script, but it would remove the read persmissions from the folder so it was unuseable.
In the Sequencer right-Click on Scripts Click on Add image
Select the file VFSCACLS.VBS.Click on Ok 22-10-2013 14-59-39
Click on File Click on Save
Open the ….DeploymentConfig.XML in Notepad.Go to<UserScripts>
Add the code;<Path>WSCRIPT.EXE</Path>
<Arguments>[{AppVPackageRoot}]\..\Scripts\VFSCACLS.vbs -guid 798f4668-a3ef-4849-a9d8-1933241dc39c -warn -name “Adobe PhotoShop CS5″</Arguments>
<Wait RollbackOnError=”false” />

This will start the VBS and set the folder permissions on %localappdata%\Microsoft\AppV\Client\VFS\*GUID* to full control for the logged on user.

The application needs to be restarted before the rights are applied. This is mandatory.

The parameter GUID is the GUID of the application, -warn will show a notification dialog that the enduser needs to restart the application because the rights are modified. The Name parameter is the name displayed in the notification window. Warn and Name are optional.


22-10-2013 14-59-3922-10-2013 14-59-391
Optional:For easy editing of the DeploymentConfig.XML file you can use ACE. 22-10-2013 15-08-075
Test the application by importing it into the App-V management console or by the powershell script:Add-AppVClientPackage -path “path to .AppV file” -DynamicDyploymentConfiguration “path to .XML” | Mount-AppVClientPackage | Publish-AppVClientPackage -globaland start it. 


Can’t get the solution to work? Contact me and let me do the trick.





Comments are closed