Tool
Last updated on
Aug 3, 2026
Log file paths for Adobe deployment and packaging tools to troubleshoot installation and update issues.
When troubleshooting deployment, packaging, or installation issues, you can locate and review log files generated by Adobe administrative tools. Use this reference to find the exact location and filename for each tool's diagnostic logs.
Deployment and packaging tool logs
|
|
Log filename |
|
Adobe Update Server Setup Tool (AUSST) |
AdobeUpdateServerSetupTool.log |
|
Exception Deployer |
ExceptionDeployer.log |
|
Remote Update Manager (RUM) |
RemoteUpdateManager.log |
|
Creative Cloud Packager – PDApp |
PDApp.log |
|
Creative Cloud Packager – Package Builder |
AdobePBhhmmss_ddmmyy.log |
Note
In the filename AdobePBhhmmss_ddmmyy.log, hhmmss_ddmmyy = hour|minute|second_date|month|year
Licensing logs
|
Platform |
Location |
|
Windows |
%temp%\oobelib.log |
|
macOS |
/tmp/oobelib.log |
Creative Cloud download and installation logs
Creative Cloud Packager creates a log file if a file named asu.trace is placed at:
Platform |
Location |
Windows |
%temp% |
macOS |
~/Library/Logs/ |
DLM.log file locations
The resulting DLM.log file is created at:
Platform |
Location |
Windows |
%temp%\AdobeDownload |
macOS |
~/Library/Logs/AdobeDownload |
For Windows errors in the DLM.log, refer to Windows Dev Error Messages on Microsoft Learn. For example, error 12150.
