EnglishFrançaisDeutschEspañolItaliano日本語한국어NederlandsPortuguês (Brasil)中文 (简体)中文 (繁體, 台灣)
Skip to main content

August 24, 2026

Windows Command-Line Arguments for the App Volumes Application Capture Command-Line Program

This section lists the command line arguments that are used with appcapture.exe to achieve tasks such as starting a capture session, updating an existing application, ending a capture session, and so on, using the command-line capture program.

The following table in this page lists the commands and parameters which can be used with the capture command-line program:

Note:

  • To use the commands and parameters in the earlier format, see App Volumes Administration guide, versions 2503 or earlier, at Omnissa Product Documentation.

  • The command-line arguments for MSIX app attach format cannot be used in the current version of App Volumes. For information about these arguments, see Omnissa App Volumes Administration Guide version 2503 and earlier.

  • When using the /upgradecode parameter, either a custom GUID or the UpgradeCode of a native MSI installer is required. To generate a custom GUID, use the New-Guid PowerShell command.
    /upgradecode is used with commands such as appcapture.exe start and appcapture.exe packagemsix. For more information about this parameter, see the Options section in the table.

Description of Commands and Parameters

Command line ArgumentTaskExamples
Actions
helpThis command displays the list of appcapture.exe commands, options, and their descriptions.
appcapture.exe help
startThis command starts a capture session for a new application or updates an existing application.

appcapture.exe start /name name_of_the_package /upgradecode custom_GUID | native_MSI_application_installer_path

If additional parameters such as /format and /output are not provided, then by default, the .vhd and .json files are captured at this location, C:\ProgramData\Omnissa\AppVolumes\Packages.


  • The following parameters can be used with this command: /name, /author, /description, /format, /output, /source, /manualresume, /upgradecode, and /productversion.

  • /name and /upgradecode are mandatory parameters which must be used with the start command, whereas the remaining parameters are optional.

  • If the application to be captured has a product version format which is not compatible with the expected format, then capture fails. In such a scenario, using /productversion is mandatory at the time of capture.
Example: 
appcapture.exe start /name Notepad++ /upgradecode {867CAC46-AFDC-4462-8BE4-1F25861A5C55} /author John /description "This is Notepad++".

In this example, Notepad++, is the name of the package, captured in the VHD format. Author and description are added as capture details. As /output is not provided, the output files - Notepad++.vhd and Notepad++.json - are generated at this location: C:\ProgramData\Omnissa\AppVolumes\Packages by default.
{867CAC46-AFDC-4462-8BE4-1F25861A5C55} is the custom GUID which is set as the app_product_guid property in the Notepad++.json file. For more information about /upgradecode, see the corresponding description in this table.
metadataThis command extracts the .json metadata file for the captured application, which can either be a VMDK or VHD application package.

appcapture.exe metadata /file "path_of_the_captured_application_package"

/file can be either .vmdk or .vhd.

By default, the .json file is extracted to the same location as the captured application. If the /output parameter is provided, then the .json file is extracted to the location as specified in the parameter.		Example:
appcapture.exe metadata /file "C:\Users\TestUser\Desktop\Notepad++.vhd" /output "C:\Users\TestUser\Desktop\Test"

In this example, Notepad++.json for the Notepad++.vhd application package is extracted to the path as specified in the /output parameter, which is C:\Users\TestUser\Desktop\Test.
convert This command converts the format of an application package to another format.
  • The converted package can be in VHD, VMDK, or MSI format.
  • The source package can be a VHD, VMDK, or MSI. If the source is an MSI, then this can be converted only into a VHD package.
  • By default, the converted application package is located at the same path as the source application package and has the same file name as the source package.
  • A .json file is generated for every converted package. This file replaces any existing .json file if present at the same path as the converted package.

    • appcapture.exe convert /file "path_of_the_source_application_package" /format [VHD | VMDK | MSI]

    The application package located at the path specified by the /file parameter is converted to the application package format as mentioned in the /format parameter.

    This command can also be used to convert an App-V application package to an App Volumes package. For more information about converting an App-V application package, see Convert App-V Application Packages to App Volumes Application Packages.

    Note: To generate a .vhd application package from a .vmdk application package, which is captured using App Volumes Manager, the .vmdk package must be converted to a monolithic sparse .vmdk and then the appcapture.exe convert command can be used.
Examples:
  • In this example, Notepad++.vhd is converted to Notepad++.msi and the converted package is located at C:\Users\TestUser\Desktop\test.
    appcapture.exe convert /file "C:\Users\TestUser\Desktop\Notepad++.vhd" /format MSI /output "C:\Users\TestUser\Desktop\test"

  • In this example, Notepad++_workstation.vmdk is converted to Notepad++.vhd and the converted package is located at C:\Users\TestUser\Desktop\test.
    appcapture.exe convert /file "C:\Users\TestUser\Desktop\Notepad++_workstation.vmdk" /format VHD /output "C:\Users\TestUser\Desktop\test"

  • In this example, Notepad++.appv is converted to Notepad++.vhd and the converted package is located at C:\Users\TestUser\Desktop\test
    appcapture.exe convert /file "C:\Users\TestUser\Desktop\Notepad++.appv" /format VHD /output "C:\Users\TestUser\Desktop\test"
    .
    Notepad++.vhd is an App-V application package.

  • In this example, Notepad++.msi is converted to Notepad++.vhd. The VHD package is located at the same location as the MSI package.
    appcapture.exe convert /file "C:\Users\TestUser\Desktop\Notepad++.msi" /format VHD
cancelThis command cancels an ongoing capture session.

appcapture.exe cancel

The capture session gets canceled and the machine reboots. It is recommended that you revert to a clean snapshot before you start a new capture session.		Example:

appcapture.exe start /name Notepad++
.........................
.........................
appcapture.exe cancel
In this example, the capture session for Notepad++ gets canceled.
finalizeThis command ends a capture session.

appcapture.exe finalize

When finalize is used, the machine reboots and the command-line capture program automatically restarts. After the restart, the capture process is complete.

If no additional parameters are provided, then the .vhd and .json files are generated by default.

.vhd is the application package format and .json is the metadata file.
By default, these files are located at: C:\ProgramData\Omnissa\AppVolumes\Packages. 		Example:

appcapture.exe start /name Notepad++
.........................
.........................
appcapture.exe finalize
In this example, Notepad++.vhd and Notepad++.json are generated at C:\ProgramData\Omnissa\AppVolumes\Packages after the capture session completes.
resumeThis command resumes the command-line capture program after a machine reboot.

If you have used the /manualresume parameter at application capture, then you must use this command to resume the program.

appcapture.exe resume		Example:

appcapture.exe start /name Notepad++ /manualresume
...................................
...................................
appcapture.exe resume

In this example, the machine reboots after application capture, but the program does not automatically restart after the reboot as the /manualresume is provided. When the resume command is provided, the program restarts.
updateThis command uses /upgradecode to add or modify the app_product_guid property of a captured application package. If the package has an existing property, then the newly generated property replaces the existing one.
You can also use the /productversion parameter to add or update the product version of the captured application.

For information about the /upgradecode parameter, see the corresponding description and examples in this table.		 Examples:
  • appcapture.exe update /upgradecode {867CAC46-AFDC-4462-8BE4-1F25861A5C55} /format MSI /file "C:\Users\TestUsers\Desktop\7zip.msi"
    • In this command, {867CAC46-AFDC-4462-8BE4-1F25861A5C55} is set as the UpgradeCode property in the 7zip.msi package, which was captured earlier.

  • appcapture.exe update /upgradecode {867CAC46-AFDC-4462-8BE4-1F25861A5C55} /format VHD /file "C:\Users\TestUsers\Desktop\NPP.vhd"
    • In this command, {867CAC46-AFDC-4462-8BE4-1F25861A5C55} is set as the app_product_guid property for the NPP.vhd package. This property is present in the NPP.json file.

  • appcapture.exe update /upgradecode "C:\Users\TestUser\Downloads\7z920-x64.msi" /format MSI /file "C:\Users\TestUser\Desktop\7zip.msi"
    • In this command, the GUID generated using the UpgradeCode property of the native 7z920-x64.msi application installer is set as the UpgradeCode property in the 7zip.msi App Volumes application package, which was captured earlier.

  • appcapture.exe update /upgradecode "C:\Users\TestUser\Downloads\7z920-x64.msi" /format VHD /file "C:\Users\TestUser\Desktop\7zip.VHD"
    • In this command, the GUID generated using the UpgradeCode of the native MSI 7-zip application installer (7z920-x64.msi) is set as the app_product_guid property in the .json file of the 7zip.VHD package.
testThis command tests and validates the captured .vhd application package. When this command is used, the program attaches the package to the virtual machine and enables the application bundles in the package for testing.

appcapture.exe test /package path_of_the_VHD_package

Note: Before using the test command, you must revert to a clean snapshot, which is different from the one used for application capture. 		Example:
appcapture.exe test /package C:\ProgramData\Omnissa\AppVolumes\Packages\test_dir\Notepad++.vhd
In this example, Notepad++.vhd is attached to the virtual machine and enabled for testing.
testendThis command ends the test session.
If you intend to test and validate another application, then revert to the snapshot taken before you started the test session for this application.		Example:
appcapture.exe testend
packagereportThis command is used to generate a .json file from which a read-only, HTML package report is generated for an existing application package.

The report contains package content such as registry entries, files, and folders detected during packaging. Such information helps in maintaining, updating, and troubleshooting packages.

For information about package report, see the About the App Volumes Application Package Report section in Capture an App Volumes Application.

appcapture.exe packagereport /file path_of_the_captured_application_package /output report_output

/file - indicates the path of the captured package. The captured package can be either VHD or VMDK.

/output - indicates the location at which the package report files must be generated (package_name.report.html and package_name.report.json). If an output path is not provided, then the files are generated at the same path as the captured package.
Example:
appcapture.exe packagereport /file "C:\Users\localadmin\Documents\emeditor.vhd" /output "C:\Users\localadmin\Desktop"

In this example, the package report files are generated for emeditor.vhd which is an existing application package. After the command runs, the report files - emeditor.report.html and emeditor.report.json - are generated at C:\Users\localadmin\Desktop.
securityscanThis optional command performs a security scan on a VHD application package using Microsoft Defender.

When the command runs, a securityscan.bat script is triggered which runs Microsoft Defender and the VHD package is scanned. After the scan finishes, a .json file is generated which contains information such as the time stamp of the scan, scan command, scan result, scan output, path of the VHD package for which the scan is run, volume ID, app ID, and so on. Some of this information is also added to the metadata file (.json) of the captured VHD package in a section called securityscan.

appcapture.exe securityscan /path VHD_file_path /output scan_output_json_path

/path - indicates path of the captured VHD package
Note: Ensure that the captured .json file is at the same path as the captured VHD package.

/output - indicates the location at which the scan result (.json) must be generated
This location can be different from /path

For the securityscan command to run successfully, it is mandatory to provide the /output parameter.

When the same VHD package is scanned subsequently, scan results are overwritten in the .json file. To retain the earlier scan results for the package, a different .json file name can be provided in the /output parameter. However, the metadata file (.json) of the package contains only the latest scan results.

Here are some considerations when using this command:
  • Microsoft Defender must be installed and must be up to date on the virtual machine where the scan is run.
    Note: Currently, this command can be used only for the Microsoft Defender solution.

  • Administrator privileges are required to run this command.

  • This command can be used only for VHD packages.


    • Note: For information about a failed scan, see the output field in the .json file generated as an output of the securityscan command. Before importing the package to App Volumes Manager, ensure that the scan is successful.

    A scan summary can be generated on the console for a single file or multiple files (in the same folder) using the /summary parameter. For more information about this parameter, see one of the rows in the Options section of this table.     		Example:
    appcapture.exe securityscan /path "C:\Users\localadmin\Desktop\ScanVHD\Notepad++.vhd" /output "C:\Users\localadmin\Desktop\scannotepad++.json"

    In this example, the securityscan command scans Notepad++.vhd and scan results (scannotepad++.json) are generated at the path as specified in the /output parameter. The scan results are also added to the securityscan section of Notepad++.json.
    packagemsixThis command is used to generate an App Volumes application package for an MSIX application.
    The MSIX application can be converted to any of the App Volumes package formats: VHD, VHD+MSI, or VMDK.

    Using this command removes the need for manual steps such as creating and mounting a new VHD and unpacking the MSIX application into the VHD, when generating the package. .

    Before using the packagemsix command, ensure that you have the following:
    • MSIXMGR tool (msixmgr.exe) must be downloaded and the executable placed in the capture virtual machine.
      The MSIXMGR tool can be downloaded from this location.
    • MSIX installer of the application, for which the App Volumes package is generated.

    The command is as follows:
    appcapture.exe packagemsix /name AppVolumes_package_name /upgradecode custom_GUID | native_MSI_application_installer_path /source path_of_the_MSIX_application_installer /msixmgr location_of_MSIXManagertool_executable /format AppVolumes_package_format

    Here are a few considerations when using the command:
    • appcapture.exe runs the executable of the MSIXMGR tool to unpack the MSIX application into a VHD.
    • After the command runs, .json and .vhd files are generated at C:\ProgramData\Omnissa\AppVolumes\Packages by default.
      If VMDK and MSI formats are specified, *_workstation.vmdk and .msi are generated respectively.
      To customize the location, /output option can be used.
    • When the command is run for the first time, the path of the MSIXMGR tool executable is stored in an svservice registry value, MSIXMgrToolPath.
      When the command is run subsequently:
      • If the path of the executable is not provided in the command, then the command uses the executable location stored in the registry value.
      • If the path of the executable is provided, then the command uses this location and the registry value gets updated with the new location.
      For more information about this registry value, see Configuration of svservice.

    You can deliver the generated package to a Windows endpoint either using App Volumes Manager or a device management tool such as Workspace ONE UEM.
    To use App Volumes Manager as the delivery mechanism, you must first import the files into App Volumes Manager.

    If the generated package is a VHD or VMDK, see the What To Do Next section in Capture an App Volumes Application. If the generated package is an MSI, see Deliver App Volumes Applications to Windows Endpoints.    		Example:
    
appcapture.exe packagemsix /name Teams /upgradecode {64E3DF12-93EB-4567-9EA7-A3656026E549} /source "C:\Users\localadmin\Downloads\Microsoft Teams_25332.1210.4188.1171_X64_msix_en-US.msix" /msixmgr C:\MSIXMGR\x64\msixmgr.exe /format VHD,VMDK,MSI
    In this example, the MSIXMGR tool is placed at C:\MSIXMGR\x64\msixmgr.exe. After the command runs, the following files Teams.vhd, Teams_workstation.vmdk, Teams.msi, and Teams.json are generated at C:\ProgramData\Omnissa\AppVolumes\Packages.

    This path C:\MSIXMGR\x64\msixmgr.exe is stored in the MSIXMgrToolPath registry value.
    Options
    /descriptionThis parameter adds a description for a captured application either during a new capture session or when updating an existing application.

    When the package is imported to App Volumes Manager, this description can be viewed in the admin UI as part of package description.

    This parameter is optional.    		Example: 
    appcapture.exe start /name Notepad++ /description "This is a Notepad++ application package."
    /formatThis parameter can be used to choose the output format of an application package during a new capture session or when converting an already-captured application to a different format. Hence, this parameter can be used with start and convert commands. The output formats can be VHD, VMDK, or MSI.
    • appcapture.exe start /name name_of_package /format [VHD | VMDK | MSI]

    • appcapture.exe convert /file path_of_the_source_application_package /format [VHD | VMDK | MSI]

    Note: If this parameter is not provided, then by default, the generated output is in the VHD format.

    You can use this parameter with the start command in the following ways :
    • /format [MSI | VMDK ]: This indicates that the application package is first captured in the VHD format, converted to the output format as specified in the parameter value, and the VHD format is deleted.
    • /format VHD, [MSI | VMDK ]: After package capture, VHD format is converted to the output format as specified in the parameter value. The VHD format is also retained.
    • /format VHD,MSI,VMDK: This indicates that after package capture, VHD format is converted to both MSI and VMDK formats and the VHD format is also retained.
    • /format VMDK,MSI: This indicates that the VHD format is converted to VMDK and MSI and the VHD format is deleted.
    		Example: 
    appcapture.exe start /name Notepad++ /format VMDK,MSI

    In this example, the generated Notepad++.vhd format is converted to Notepad++.vmdk and Notepad++.msi formats. Later, the Notepad++.vhd format is deleted.
    /manualresumeThis parameter prevents the command-line capture program from an automatic restart after a machine reboot. The program must be manually restarted after the reboot using the resume command.

    This parameter is optional and can be used only with the start command.

    Sometimes during capture completion or application installation, the machine reboots. In either case, the command-line capture program automatically restarts on its own.
    Sometimes, you might want to perform some custom initialization task and prevent the automatic restart of the program. In such cases, this parameter can be used.
    After the machine reboots, the resume command must be used to restart the program and complete the capture session.    		Examples: 
    appcapture.exe start /name Notepad++ /manualresume


    If the machine reboots after application capture, then the program does not automatically restart after the reboot. The resume command must be provided for the program to restart.
    /norebootThis optional parameter can be used to prevent the agent machine from rebooting when finalizing an application capture. As a result, the agent machine completes the capture process successfully without undergoing a reboot.

    If the application getting captured has a requirement for machine reboot during the installation process, this reboot is not affected.

    Note: This parameter can be used only when capturing an application into VHD format.

    Using this parameter is optional as skipping the agent machine reboot depends on your packaging requirements. When the parameter is not used, the current behavior continues where the capture machine reboots to complete the packaging process.    		Examples: 
    appcapture.exe start /name Notepad++ /upgradecode {867CAC46-AFDC-4462-8BE4-1F25861A5C55} /noreboot


    At the time of finalizing the capture, agent machine does not reboot and the capture process continues to completion.
    /outputThis parameter specifies the location of output files. For example, this parameter can be used when starting a capture session

    Using this parameter is optional.
    If this parameter is not provided, then by default, the output files are located at C:\ProgramData\Omnissa\AppVolumes\Packages.

    Note: This parameter can be used only with the following commands: start,metadata, and convert.    		Example: 
    appcapture.exe start /name Notepad++ /output C:\ProgramData\Omnissa\AppVolumes\Packages\Test
    In this example, the Test folder contains Notepad++.vhd and Notepad++.json after the capture session.
    /prerequisitepackagesThis parameter specifies the prerequisite packages required for capturing an application.

    Any package designated as a prerequisite is delivered and virtualized in the capture virtual machine before the intended application is captured, ensuring that all necessary dependencies are present during the capture process.
    For a better understanding of the prerquisite packages capability, see Understand the Role of Prerequisite Packages in Application Capture

    Note:
    • This parameter can be used only for capturing VHD packages.
    • If the prerequisite packages need to be virtualized in a specific order, then these packages must be listed in the same order of virtualization in the parameter.

    You can use the parameter with appcapture.exe start in the following ways:
    • appcapture.exe start /name name_of_the_package /upgradecode custom_guid /prerequisitepackages [\\share\folderA];[file1.vhd];[file2.vhd];[file3.vhd][\\share\folderB];[file4.vhd]
      • file1.vhd, file2.vhd, file3.vhd, and file4.vhd are virtualized in the same order as they are listed.
      • file1.vhd, file2.vhd, and file3.vhd are files from folderA and file4.vhd is from folderB. The same folder can be specified multiple times. Multiple prerequisite packages can be added from multiple folders.

    • appcapture.exe start /name name_of_the_packcage /upgradecode custom_guid /prerequisitepackages [full-path-to-file1.vhd];[file2.vhd];
    • Example: 
      appcapture.exe start /name Notepad++ /prerequisitepackages \\mymachineA\share;myapp1.vhd;myapp2.vhd;\\mymachineB\anothershare;myapp3.vhd;\\mymachineA\share;myapp4.vhd /output C:\ProgramData\Omnissa\AppVolumes\Packages\Test


      In this example, myapp1.vhd, myapp2.vhd, myapp3.vhd, and myapp4.vhd are prerequisite packages required for capturing Notepad++. These prerequisite packages are virtualized in the order of listing, that is, myapp1.vhd is virtualized first followed by myapp2.vhd and so on. Notepad++ is captured only after all these primary applications are installed in the capture virtual machine. Test folder contains Notepad++.vhd and Notepad++.json after the capture session.

    • Example:
      appcapture.exe start /name 7zip /prerequisitepackages \\mymachineA\share\myapp1.vhd;myapp2.vhd;myapp3.vhd;myapp4.vhd /output C:\ProgramData\Omnissa\AppVolumes\Packages\Test

      In this example, to capture 7 zip application, prerequisite packages are required. The entire file path is specified for one of the prerequisite packages, myapp1.vhd. The other prerequisite packages specified are myapp2.vhd, myapp3.vhd, and myapp4.vhd which are also present at \\mymachineA\share. These packages are virtualized in the same order as they are listed: myapp1.vhd, myapp2.vhd, myapp3.vhd, and myapp4.vhd.
    /productversionIf the version is missing from the application or needs a correction, this parameter generates or updates the product version for an application.
    • The value of the parameter must be in this format: x.x, x.x.x, or x.x.x.x, where x can be any number between 0 to 9.
    • If the product version is missing in an application, then it is mandatory to provide the product version either when the package capture starts or before capture is finalized.
    • If the product version is not specified even at the time of finalize, the capture fails after the pre-configured timer elapses.
    • This parameter can be used with the appcapture.exe start command for new packages and appcapture.exe update command for existing application packages.

      Note: If the application already has a product version and this parameter is not used, then the capture command-line program uses the existing product version even if the version is incorrectly specified for the application.
    		Examples:
    • In the following example, the specified product version is added to the application at the time of finalizing the capture. If the application already has a product version, then 5.3.3 replaces the existing product version:
      appcapture.exe start /name /npp /upgradecode {64E3DF12-93EB-4567-9EA7-A3656026E549} /productversion 5.3.3

    • You can use the /productversion parameter for existing application packages which have no product version:
      appcapture.exe update /name /npp /upgradecode {64E3DF12-93EB-4567-9EA7-A3656026E549} /productversion 5.3.3
    /sourceThis parameter updates an existing VHD application package using the .vhd file as the source.
    This argument is optional.

    Note: Using this parameter is optional; however, this parameter must not be used when capturing a new application.     		Example: 
    appcapture.exe start /name Notepad++_update /source C:\ProgramData\Omnissa\AppVolumes\Packages\Notepad++.vhd
    In this example, Notepad++_update is the name of the updated package. This name must be different from the name given to the application package captured at first, which is Notepad++.vhd. The command-line capture program uses Notepad++.vhd as the source file to capture the updated package.
    /summaryThis optional parameter generates a summary of the scan result of a single VHD file or multiple VHD files in the same folder on the console.
    Scan summary contains the name of the file and scan status (success, failure, and not scanned). For files that are not scanned, the securityscan command must be run again.

    appcapture.exe securityscan /summary folder path | filepath

    folder path - indicates the folder which contains multiple .vhd files
    Scan summary is displayed for all the files in this folder.

    file path - file for which the scan summary is generated and displayed     		Example: 
    appcapture.exe securityscan /summary "C:\Users\localadmin\Desktop\ScanVHD"
    In this example, ScanVHD is the folder that contains multiple VHD files. When this parameter is used, scan results of all the files in the ScanVHD folder are displayed.

    appcapture.exe securityscan /summary "C:\Users\localadmin\Desktop\ScanVHD\Notepad++.vhd"

    In this example, the scan result of Notepad++.vhd is displayed as follows:
    Security scan summary for file
    C:\Users\localadmin\Desktop\TestVHDtoVMDK\Notepad++.vhd success    .
    /upgradecode This parameter sets the app_product_guid property for a captured application package. app_product_guid links different versions of the same application together.

    During application capture, /upgradecode can use a custom GUID or the UpgradeCode of a native MSI installer of the application being captured to generate the app_product_guid property.

    At the time of application capture:
    • If an MSI installer of the application being captured is used, provide the path of the native MSI installer. The UpgradeCode of this MSI installer is automatically used as the app_product_guid
    • If an EXE installer of the application being captured is used, provide a custom GUID.
      To generate a custom GUID, use the PowerShell New-Guid command

    It is mandatory to use the /upgradecode parameter with the appcapture.exe start command. To add or modify the app_product_guid property of an existing application package, the appcapture.exe update command can be used.

    Ensure the following:
    • custom_GUID must be a unique GUID for every application.
    • For a successful upgrade, this parameter must use the MSI installer of the same application or the same custom GUID depending on what is used in the earlier capture session.

    If the custom GUID is the same as the application GUID of an application in App Volumes Manager, then this package is automatically associated with the existing application after import.     		Examples of using UpgradeCode with the appcapture.exe start and appcapture.exe update commands respectively:
    • appcapture.exe start /name 7zip /upgradecode "C:\Path\7z920-x64.msi” /format MSI
      In this example, the UpgradeCode of the 7zip MSI installer is used to generate the app_product_guid property for the captured package in MSI format.

    • appcapture.exe start /name Notepad++ /upgradecode {867CAC46-AFDC-4462-8BE4-1F25861A5C55}
      In this example, a custom GUID is used to generate the app_product_guid property of the captured package. By default, the package is captured in the VHD format.

    • appcapture.exe update /upgradecode {867CAC46-AFDC-4462-8BE4-1F25861A5C55} /format MSI /file "C:\Packages\Notepad++.msi"
      In this example, a custom GUID is used to generate the app_product_guid property. If the MSI package does not have the property, then the generated app_product_guid is set in the package. If the MSI package already has the property, then the generated app_product_guid updates the existing property.

    Was this page helpful?

    Provide feedback for this topic

    Was this topic helpful?

    Please do not include any personal or confidential information.

    Generating link…