If necessary, use Folder Options (Windows) or Option key Go (Mac OS) to view hidden folders. For more information, see Show hidden files and folders in Windows 10 and earlier or Can't see user library files in Mac OS X 10.7 and later. Windows XP: Documents and Settings user name Local Settings Temp.
Photoshop CC 14.1.1 Update Now Available Introducing Adobe Generator for Photoshop CC (14.1) Photoshop CS6 (13.0.5/Mac 13.0.1.2/Win) Perpetual License Updates Now Available By Ralph Berrett - 11:32 AM on October 23, 2013.
A new malware is targeting Macs with new tactics to sniff out antivirus and virtual machines. Never-before-seen Mac malware, dubbed OSX/CrescentCore, has been discovered in the wild. The trojan, spotted on various websites masquerading as an Adobe Flash Player installer, drops malicious applications and browser extensions on victims’ systems wh.
Adobe Premiere Elements (PRE) and Photoshop Elements (PSE) record their actions during the install process in log files. When an installation fails, these log files can be useful in determining the reason why. For silent installations, the log file is the only place where error messages are reported.
Note: To troubleshoot PRE/PSE errors that occurred before you click Install in the installer user interface, see Analyze the PDapp log.
If the Adobe Support Advisor couldn't provide a solution automatically, troubleshoot an installation issue for PRE/PSE by manually analyzing the Main Installation Log (MIL). Analyzing the MIL can consist of the following four steps. Proceed through each until you have located an installation error to troubleshoot.
The PRE/PSE installer reports most of the errors in the Summary section of your installation log file.
Navigate to the log files in one of the following folders:
Windows 32 bit (XP, Vista, 7): C:Program FilesCommon FilesAdobeInstallers
Windows 64 bit (XP, Vista, 7): C:Program Files(x86)Common FilesAdobeInstallers
Mac OS: //Library/Logs/Adobe/Installers/
The log filename includes the product name and install date, followed with '.log.gz.' An example for a log filename is 'Elements STI Installer 1.0 01-12-2011.log.gz.'
Note: The extension .gz indicates a compressed format.
Use a decompression utility such as Winzip (Windows) or StuffIt (Mac) to uncompress the .gz file. Once uncompressed, you have a new file without the .gz extension. The filename could now be something like 'Elements STI Installer 1.0 01-12-2011.log.'
Open the .log file using WordPad (Windows) or TextEdit (Mac OS).
Note: By default, .log files open in Console on Mac OS. Select all of the text by pressing Command+A, and then copy and paste it into a text editor before continuing.
Scroll to the bottom of the log and look at the Summary section for lines that start with 'Error' or 'FATAL.'
If you find any of the following, see Visual Studio runtimes install fail | CS5, CS5.5 | Windows.
For all other errors, search the Adobe knowledgebase for a documentation that provides a solution. When you search, omit file paths and machine-specific information from search strings. For a list of possible errors that can appear, see Installation and launch errors in Creative Suite 5.
The PRE/PSE installer uses a few Windows installers. These installers can produce error codes that don't appear in the Summary section of the log file.
Note: These steps continue from Solution 1 above, working with the Main Installation Log (MIL).
Search the Adobe Knowledgebase for any errors found. Omit any file or registry paths from the search.
Repeat the search until you have reached the end of the log file.
The PSE/PRE installer creates multiple application components and logs each separately in the Main Installation Log (MIL).
The log for each component installation starts with the following text:
Once you have identified the component installation that failed, scroll to the top of that component's log and read each line to check for errors.
Search the Adobe Knowledgebase for any errors found.
If the component installation that failed is 'Search for Help,' 'Adobe Media Player (AMP),' or 'Adobe AIR,' see AIR component fails when installing Creative Suite 5 products.
If no error messages are found, determine what the component is trying to install, then search the Adobe Knowledgebase for specific troubleshooting. For example, if the failed component is a font pack, see Troubleshoot font problems | Windows or Troubleshoot fonts | Mac OS X.
4. Analyzing the supplemental log (Windows only)
Depending on which of the Elements products you are installing, you can have an additional installation log to check for error codes.
Navigate to the Temp folder:
Windows XP: C:Documents and Settings[User Name]Local SettingsTemp
Windows Vista or 7: C:Users[User Name]LocalTemp
Note: You can also get to this folder by going to Start > Run and type in '%temp%' (without quotes), then clicking OK.
Find one of the following files:
PRE[Version Number]Installer.log
PSE[Version Number]Installer.log
Elements[Version Number]Organizer.log
Search the Adobe knowledgebase for a TechNote that provides a solution to each error message. Omit paths and machine-specific information from search strings.
If you are troubleshooting install errors for PRE/PSE and the error occurred before you clicked Install, analyze the PDapp.log file.
Navigate to the PDapp.log file in one of the following folders:
Note: Some of the following folders are hidden by default. If necessary, see Show hidden files, folders, filename extensions | Windows XP, Vista, Windows 7.
Windows XP: C:Documents and Settings[User Name]Local SettingsTemp
Windows Vista and Windows 7: C:Users[User Name]AppDataLocalTemp
Mac OS: //Users/[User Name]/Library/Logs/
Open PDapp.log in a text editor such as WordPad (Windows) or TextEdit (Mac OS).
PDapp.log records installation attempts sequentially. Each line in the log starts with a date and time stamp, which indicates when the installation was attempted. Each attempt starts with a Build Version number.
Analyze only the most recent attempt. If you can’t determine which build attempt is the most recent, delete PDapp.log and run the installer again.
In the most recent installation attempt, look for lines identified with [Error] or [FATAL]. For example:
5/1/2010 13:49:48.847 [Error] DWA.SystemRequirement SystemRequirements check FAILED for payload - Adobe Premiere Elements PCI wrapper
5/1/2010 13:49:20 [FATAL] PIM - Error could not create PIM Common FolderPath.. F:Program Files (x86)Common FilesAdobeOOBEPDApp
Type
Error Message
Solution
FATAL
End Adobe Setup. Exit Code: -5
Replace the setup.xml file
FATAL
Failed to create backup folder [File path]
Replace the setup.xml file
Copy the Adobe Photoshop Elements or Adobe Premiere Elements folder from the disc to the desktop.
NOTE: If you have downloaded Elements, skip this step.
Open the Photoshop Elements or Adobe Premiere Elements folder on the desktop.
Copy setup.xml to the following folders, replacing the existing file:
Double-click the Setup.exe file in the root installation folder, and follow the onscreen instructions.
If there are no TechNotes in the knowledgebase for your errors, contact Adobe support.
You can also visit the Adobe product forums.
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
Legal Notices | Online Privacy Policy
What are log files and what do they do?
Log files are a journal of system parameters and entries describing everything that takes place on your Mac. Any operation that is being performed at any time is noted down in the form of logs, much like a “black box” on an airplane.
For the most part, logs contain crash reports and app errors. To us, regular users, this information bears no sense because it’s unreadable. But when you need to diagnose a problem, log files are an indispensable invention.
How to delete user log files?
Why would anyone want to delete user logs on Mac? First, deleting outdated logs may speed up some of your apps. Second, however small they are, logs still take space on your disk. And lastly, outdated logs could potentially cause software conflicts.
User logs are a part of your user profile. They are stored at: ~/Library/Logs
You should know that deleting user logs is not an everyday operation. It may backfire if you don’t know what you’re deleting. But since you asked, here is how it’s done.
We've got two ways to do it: the manual way and the CleanMyMac X way.
How to clear log files on a Mac manually
Open Finder and select 'Go to Folder' in the Go menu.
Type in ~/Library/Logs and hit Enter to proceed to this folder (pay attention to the use of “~” — this will ensure that you’re cleaning user log files, not the system log files).
Optional step: You can highlight & copy everything to a different folder in case anything goes wrong.
Select all files and press Command+backspace.
Restart your Mac. Note: We recommend that you remove the insides of these folders, but not the folders themselves. Also note that some system applications, like Mail, have their own logs stored elsewhere.
Remember, if you want the additional space from cleaning these log files, be sure to empty your Trash. To do this, Control+click on the Trash icon in the dock and select “Empty Trash.”
In addition, some log files can be found in the /var/log folder, but not all the items contained therein are safe to remove. That’s why it is safer to remove log files using a Mac cleaning utility like CleanMyMac X.
How to clear log files with CleanMyMac X
Rather than searching all over your Mac for log files yourself, you can clean up logs with CleanMyMac X in just 4 steps. And that’s not all it does! Anyway, to clean them up with CleanMyMac X:
Mac Os /library/logs/adobe/installers/
Download CleanMyMac X (free version) and launch it.
Choose System Junkin the left menu.
Click Scan at the bottom of CleanMyMac X.
Hit Clean.
Done! If you’d like to remove only log files and nothing else, click on Review Details before clicking Clean. Deselect everything except for System Log Files and User Log Files, and then click Clean.
Make sure that once you have finished clearing out these logs for additional hard drive space, you empty out your Trash. To do this, Control-click on the Trash icon in the dock and select “Empty Trash.” Restart your Mac afterward so your Mac can begin to create new log files.
Is it safe to delete log files?
Many experienced users prefer to clean their user logs as part of their Mac cleaning routine on Mac. Though it doesn’t directly translate into speed, there is some benefit in keeping your disk clean. Some apps have notoriously large log files, especially media apps. For example, writing this article I’ve found a single log file by Elmedia player that weighted 325 MB.
Adobe Install Log
As a word of caution, you shouldn’t delete the entire Logs folder, only delete what’s contained inside. As we have said, log files serve for diagnostic purposes. If your Mac is doing well, there’s nothing particularly harmful in deleting logs.
Cleaning up log files with CleanMyMac X is as easy as can be. And, like we said before, it can do so much more, too! With CleanMyMac X, you can clean up outdated apps, language packs, universal binaries, and gigabytes of useless junk you didn’t even know you had. Download CleanMyMac X now and feel what it’s like to have a faster, cleaner Mac.