Choose Visual C++ runtime versions to install

Last updated on Dec 16, 2024

Applies to enterprise & teams.

Choose the Visual C++ runtime versions to be installed on end-user computers when a package is deployed

Introduction

Caution:

Use the procedure described in this document with caution and only if there is a very strict requirement to not deploy specific Visual C++ runtime versions in your enterprise.

When a package created with Creative Cloud Packager is deployed on an end-user computer, all available Visual C++ (VC) runtime versions are installed along with the products specified in the package.

Currently, this is the list of runtime versions that will be installed:

VC2005
VC2008
VC2010
VC2012
VC2013
VC2015
VC2017

By default, all the above runtime versions are installed on an end-user computer. However, enterprise administrators can select the runtime versions that are installed on the end-user computers when a package is deployed.

Note:

This document is applicable only to Creative Cloud Packager administrators who are creating packages to be deployed on Windows computers.

Create and deploy package with selected runtime versions

Use the following procedure to ensure that Creative Cloud Packager, installs only specified runtime versions:

Create an Offline XML file in which you define the runtime versions that you want to install when the package is deployed in the following location:

<UserName>\AppData\Local\Adobe\CCP\OfflineVCRedistributablesInfo.xml

The following is a sample of the Offline file:
```
<?xml version="1.0" encoding="UTF-8"?>
<vcRedistributablesInformation>
 <products>
  <product sapCode="PHSP" version="19.0">INSTALLVC2010</product>
  <product sapCode="KBRG" version="7.0.1">INSTALLVC2005,INSTALLVC2008</product>
  <product sapCode="CPTL" version="8.6">INSTALLVC2005,INSTALLVC2013,INSTALLVC2015</product>
  <product sapCode="DRWV" version="17.6">INSTALLVC2005,INSTALLVC2008</product>
 </products>
</vcRedistributablesInformation>
```
Each product node defines a product that is included in the package you are creating.

sapCode:

Identifies the product that is included in the package.

version:

The version of the product that is included in the package.

Note:

For each product, the value that you specify in the version attribute, is the version number of the product that is included in the package you are creating. For example, if you are packaging Photoshop version 20.0.1, specify the version as 20.0.1.

You can get the list of Sap Codes for Adobe products here.

In the text for each product node you need to include a comma-separated list of the VC runtime versions that are required for that product in the following format:

INSTALLVC<Runtime version>

Note:

The Offline file needs to be created on the computer on which you are creating the packages.

When you deploy a package that is created using the Offline file, a union of all the runtime versions that are defined in the Offline file are installed on the end-user computer.

For example, if you create the following Offline file when you create your package, the VC 2008, VC 2010, and VC 2012 are installed on the end-user computer:
```
<?xml version="1.0" encoding="UTF-8"?>
<vcRedistributablesInformation>
 <products>
  <product sapCode="PRLD" version="5.0">INSTALLVC2010,INSTALLVC2012</product>
  <product sapCode="PHSP" version="18.0">INSTALLVC2008,INSTALLVC2010</product>
  <product sapCode="PHSP" version="19.0">INSTALLVC2010</product>
  <product sapCode="KBRG" version="6.5">INSTALLVC2008</product>
 </products>
</vcRedistributablesInformation>
```
Caution:

If your Offline file does not include all the products that are included in your package, the deployment of the package succeeds but the products may not run properly. This happens because of the required runtime versions that are not defined in the offline file and are therefore not installed on end-user computers.

See the following FAQ for more cases and exceptions that you need to be aware of when defining the Offline file.
Use Creative Cloud Packager to create the package that needs to be deployed.
Deploy the package on the end-user computer.

FAQ

The following FAQ covers the corners cases that you need to be aware of when defining the Offline file:

Yes. However, if you do not include an Offline file when creating a package, all available runtime versions are installed on the end-user computers.

Currently, this is the list of runtime versions that will be installed:

VC2005
VC2008
VC2010
VC2012
VC2013
VC2015
VC2017

If you create an Offline file that does not include runtime versions that are required by the products that are defined in the package, the products are installed successfully on the end-user but will not launch. This happens because of the required runtime versions that are not defined in the offline file and are therefore not installed on end-user computers.

If you have not included products in the Offline file, a union of the runtime versions that are defined in the products that you have included will be installed.

Take the following example:

If you create a package that includes:

After Effects CC (AEFT) version15.0.0
Bridge CC (KBRG) version 8.0
Illustrator CC (ILST) version 22.0.0

And your Offline file is defined as follows:

<?xml version="1.0" encoding="UTF-8"?>
<vcRedistributablesInformation>
<products>
<product sapCode="KBRG" version="8.1.1">INSTALLVC2005,INSTALLVC2008,INSTALLVC2012</product>
<product sapCode="AEFT" version="15.0">INSTALLVC2005,INSTALLVC2008</product>
</products>
</vcRedistributablesInformation>

The Offline file does not include a definition for Illustrator. In this case, the following runtime versions are installed along with the products defined in the package:

VC 2005
VC 2008
VC 2012

Note that these runtime versions are the union of the versions defined in the sample Offline file above.

Yes. You will need to quit and re-launce Creative Cloud Packager to use this functionality.

Get help faster and easier

New user?