Deploy the package to your test system using the same method you'll use for target systems.
Last updated on
Aug 3, 2026
Test your packages before deploying them to verify they install correctly in your environment.
Before you begin
Make sure you've created your Named User Licensing or Shared Device Licensing packages.
Deploy your packages using any of these platform-specific tools:
Install test package
Test your package on a test system that meets the performance and system requirements for the applications you'll install from these packages.
Ensure the product install folder and the deployment package references are in the correct locations.
Invoke the MSI or PKG package directly if you haven't created an SCCM or ARD installer.
Use the following command lines to perform a silent installation.
- Windows: msiexec.exe /i <pkg_name>.msi /quiet
- Windows ARM: setup.exe /i <pkg_name>.msi /silent
- macOS: sudo installer -pkg <install_pkg_name> -target /
To run the installer with a user interface:
- Windows: double-click the setup.exe file.
- macOS: double-click the PKG file.
Check the log files.
The installer creates a log file that records the installation steps and exit codes.
Check the installation location for the applications and invoke each one.
Uninstall the test package
After testing the installed package, proceed to uninstall it from the test system using the platform-specific uninstaller.
Run the package uninstaller program on the test system for an installation package.
Run the MSI or PKG uninstall command for your platform if you don't have a platform-specific uninstaller.
- Windows: msiexec /uninstall <pkg_name>.msi /quiet
- macOS: sudo installer -pkg <uninstall_pkg_name> -target /
Check the installation location to verify that the applications were removed.
Note
Uninstall packages are not created for the update package.
Installation logs
When you install a package, the deployment tool (such as SCCM or ARD) generates log files for that tool. The package installs an Application Manager client version on the user’s machine. Upon installation of the package, the application manager and other processes are initiated that add the following logs to the client’s machine, as follows:
After a silent deployment, review the zipped deployment log for installation status and errors. The log file is named after the package and is zipped in a platform-specific format. The following table lists the location of log files for each package type on Windows and macOS:
|
Log file |
Package type |
Windows location |
macOS location |
|
<product_name><time_stamp>.log |
Installation package |
<Adobe Common Files>\installer\ |
/Library/Logs/Adobe/Installers/ |
|
<patch_name><version><time_stamp>.log |
Update package |
<Adobe Common Files>\installer\ |
/Library/Logs/Adobe/Installers/ |
|
Deployment engine log (zipped) |
All packages (silent deployment) |
Generated during install; saved as a package-named zip file |
Generated during install; saved as a package-named zip file |
|
oobelib.log |
All packages |
%temp% |
~/Library/Logs/ |
|
PDApp.log |
All packages |
Admin (SCCM): %windir%\Temp\CreativeCloud\ACC\ User (SCCM): %temp%\CreativeCloud\ACC\ |
~/Library/Logs/CreativeCloud/ACC/ |
Error messages
The following are the error codes that the deployment manager component can write to the PDApp.log file.
|
Error code |
Description |
|
0 |
Application installed successfully |
|
1 |
Unable to parse command line |
|
2 |
Unknown user interface mode specified |
|
3 |
Unable to initialize ExtendScript |
|
4 |
User interface workflow failed |
|
5 |
Unable to initialize user interface workflow |
|
6 |
Silent workflow completed with errors |
|
7 |
Unable to complete the silent workflow |
|
8 |
Exit and restart required |
|
9 |
Unsupported operating system version |
|
10 |
Unsupported file system |
|
11 |
Another instance running |
|
12 |
CAPS database integrity error |
|
13 |
Media optimization failed |
|
14 |
Insufficient privileges |
|
15 |
Media DB sync failed |
|
16 |
Failed to load deployment file |
|
17 |
EULA acceptance failed |
|
18 |
Application Manager bootstrap failed |
|
19 |
Conflicting processes running |
|
20 |
Invalid or missing install source path |
|
21 |
Unsupported payload version |
|
22 |
Install directory check failed |
|
23 |
System requirements check failed |
|
24 |
User cancelled workflow |
|
25 |
File path exceeds OS limit |
|
26 |
Media swap required in silent mode |
|
27 |
Keyed files detected in target |
|
28 |
Base product not installed |
|
29 |
Base product moved |
|
30 |
Insufficient disk space (completed with errors) |
|
31 |
Insufficient disk space (failed) |
|
32 |
Patch already applied |
|
33 |
Product not installed; cannot uninstall |
|
34 |
Payload info missing in Media db |
|
35 |
Missing or invalid installer files |
|
36 |
Another MSI installation running |
|
37 |
Validation failed |
|
38 |
Unknown error |
|
9999 |
Catastrophic error |
Bootstrapper Error Codes
|
Status name |
Error code |
Description |
|
BS_STATUS_SUCCESS |
0 |
Bootstrapper ran successfully |
|
BS_STATUS_ERROR_SELF_UPDATE |
1 |
Error in self-update mode |
|
BS_STATUS_ERROR_INIT_OBJ |
-1 |
Failed to initialize bootstrapper object |
|
BS_STATUS_ERROR_MULT_INST |
-2 |
More than one instance is running |
|
BS_STATUS_ERROR_SYSTEM_CHECK |
-3 |
Operating system check failed |
|
BS_STATUS_ERROR_REGISTER_CALLBACK |
-4 |
Failed to register callback |
|
BS_STATUS_ERROR_INSTALL_PACKAGE |
-5 |
Installing packages failed |
|
BS_STATUS_ERROR_COPY_FILE |
-6 |
Copying file failed after installation |
|
BS_STATUS_ERROR_LAUNCH_APP |
-7 |
Application launch failed |
|
BS_STATUS_ERROR_INVALID_COMMAND_LINE |
-8 |
Invalid command-line arguments |
|
BS_STATUS_ERROR_FILE_MISSING |
-9 |
Deployment or manifest file missing |
|
BS_STATUS_NO_ADMIN_PRIVILEGE |
-10 |
Admin privileges required but not available |
|
BS_STATUS_ERROR_PARSE_MANIFEST |
-11 |
Error parsing manifest |
|
BS_STATUS_ERROR_PIM |
-12 |
PIM library error |
|
BS_STATUS_ERROR_SYSTEM_CHECK_SOFT_STOP |
-13 |
Soft system checks failed |
|
BS_STATUS_ERROR_INSTALLATION_CANCELLED |
-14 |
Installation cancelled |
|
BS_STATUS_ERROR_LAUNCHPATH_LONG |
-15 |
Launch path exceeds 200 characters |
|
BS_STATUS_ERROR_OTHER |
-999 |
Other error |
