To Documentation Index

TMEdit  The Ultimate App-V Package Editor


AutoUpdatePackage Utility

In addition to the TMEdit GUI interface, the product also includes a command-line utility called AutoUpdatePackage.exe that can make many basic package changes without a GUI.

This is useful in scripting bulk or common changes to packages.

The command takes up to three parameters:

  • /File        A required parameter for the App-V file to be updated, followed by the path to the .AppV file. 
    • /Fixups   Optional for the controlling policy file. If specified it is followed by a path to the fixups.xml file.  If you do not specify the /Fixups parameter it will default to using the fixups.xml located in the current working directory.
  • /Rename An optional flag to indicate the package is to be renamed rather than updated as a new version. If specified, this parameter must be followed by the new PackageName (without any path or .appv).

This policy file allows you to define the types of fixes that you would like to apply. There is a template Fixups.xml file in the install folder to work from.  This file contains documentation on the currently available fixups, but with them all disabled.  Edit and save off a copy of this file for your scenario.  Some common scenarios include:

  • Removing unwanted OS tags which cause the package to not be allowed on Windows 10
  • Removing all Shortcuts, FTAs, and Shell Extensions from packages published via Citrix Storefront, Microsoft Remote App, or other application portal launchers. 
  • RES/Ivanti users that create their own shortcuts are also interested in disabling the shortcut publishing by App-V.
  • Connection Groups require matching package settings for COM and others.

Even using the provided fixups.xml file with all of the fixes disabled, you still get the following:

  • Improved compression of your package.
  • If /Rename is not specified, an updated package version GUIDand string and file is saved in a parallel folder with the _# syntax.  If Rename is specified, the package name is internally updated along with all GUIDs and the version is reset to, and the file is saved in a parallel folder using the rename value.

The syntax has been updated in version 1.6 as follows:

AutoUpdatePackage.exe /File \\server\share\apporiginal\apporiginal.appv [/Fixes fixups.xml] [/Rename apprenamed]


Here is a quick video that shows how this all works (before the /Rename option was added):

9-minute video showing you all this!