When you are logged on to a particular user account on a computer running Windows 7 or Vista, an Adobe application exhibits unexpected behavior. For example, the application doesn't start, executes commands incorrectly, returns errors, or closes unexpectedly. The issues don't occur when you log in to a new or different user account.
Make a backup of your system drive before you begin doing the tasks in this document.
These tasks sometimes initiate a User Account Control dialog box that asks for your permission to continue. Read the details in the dialog box to determine if you want to continue. If you choose to cancel the dialog box, then you can't continue with that task.
Some of the tasks in this document mention hidden folders. By default, Windows Explorer does not display hidden folders. To make hidden folders visible, see Show hidden files folders, filename extensions | Windows XP, Vista, Windows 7.
There are many possible causes of account-specific unexpected behavior. This document addresses only the most common causes. For additional assistance with troubleshooting user accounts, contact the manufacturer of your computer or go to the Microsoft Help and Support site at http://support.microsoft.com.
Log on to the user account in which the Adobe application is exhibiting the unexpected behavior. Then do the following tasks in order:
Ensure that the user account has read-write permissions on the following folders:
- C:\Program Files\Adobe
- C:\Program Files\Common Files\Adobe
- C:\Program Files (x86)\Adobe
- C:\Program Files (x86)\Common Files\Adobe
- C:\Users\<user_name>\AppData\Local\VirtualStore\Program Files\Common Files\Adobe
Adobe applications store a user's custom settings in preferences files. Each user account has its own set of preferences files.
When an Adobe application exhibits unexpected behavior only in a particular user account, the cause could be that one of the application's preferences files is damaged. You can force an Adobe application to create undamaged preferences files by renaming the folder that contains the preferences files.
For example, Adobe Premiere Pro CS4 saves preferences files in a folder named 4.0, which is located in C:\Users\[user name]\AppData\Roaming\Adobe\Premiere Pro. To force Adobe Premiere Pro CS4 to re-create the preferences files, rename the 4.0 folder (for example, rename it to Old 4.0).
Generally, Adobe applications store preferences files and folders in one or both of these locations:
- C:\Users\[user name]\AppData\Roaming\Adobe
- C:\Users\[user name]\AppData\Local\Adobe
Some Adobe applications store additional preferences files in other locations. For example, Adobe Premiere Pro CS4 stores additional preferences files in folders named Styles and Layouts, which are located in C:\Users\[user name]\Documents\Adobe\Premiere Pro\4.0.
To determine the exact names and locations of the preferences folders for the Adobe application that you are troubleshooting, go to www.adobe.com/support. Search the Support Knowledgebase for the search term "preferences" plus the name and version of the application. Then, look in the "System Errors or Freezes" document or other documents that are listed in the search results.
To re-create the preferences files for an Adobe application, do the following:
After you have re-created the preferences files, try to reproduce the issue.
If the issue still occurs, then a damaged preferences file is not the cause. To restore the user account's custom settings for the Adobe application, delete the new preferences folders. Then restore the original names of the folders that you had renamed.
If the issue no longer occurs, then a damaged preferences file was the cause. (The user account doesn't have custom settings associated with the previous preferences files.)
Some Adobe applications store data in temporary files. An Adobe application can exhibit unexpected behavior if the account-specific temporary files are excessive, outdated, or damaged.
To delete temporary files, use the Disk Cleanup utility. See Delete temporary files using the Disk Cleanup utility (Windows 7 and Vista).
By default, the Disk Cleanup utility does not delete files in the account-specific Temp folder that have been accessed within the last seven days. You can perform a more thorough removal of temporary files by manually deleting the contents of the Temp folder.
Disclaimer: Applications from publishers other than Adobe can be adversely affected if you manually delete the contents of the Temp folder. Use caution if you choose to do this additional task. Adobe doesn't provide support for problems that arise from manually deleting files in the Temp folder.
To manually delete the contents of the account's Temp folder, do the following:
- In the Command Prompt window, type the following command exactly as its appears below, and then press Enter:
del %temp%\*.* /s /q
Note: del is the command to delete files. %temp%\*.* is a combination of the "environment variable" for the location of the account's Temp folder plus wildcard characters that indicate all files. /s extends the command to include all files within any subfolders. /q prevents Windows from prompting for confirmation of each file to delete.
After you have deleted temporary files, open the Adobe application and try to reproduce the issue.
If the issue still occurs, then proceed to the next task.
Startup items are applications or documents that open automatically when you log in to a user account. When an Adobe application behaves unexpectedly in one account, it's possible that one of the account's startup items is malfunctioning, damaged, or incompatible with the application.
To determine whether any of the user account's startup items are causing the issue in the Adobe application, do the following:
- Do one of the following:
- If the Startup folder is empty, or if there is no Startup folder, then this account does not have any account-specific startup items. Skip the rest of these steps and proceed to Task 4.
- If there is at least one item in the Startup folder, then create a folder on the Desktop. Name that new folder Holding Folder.
If the issue still occurs, then an account-specific startup item is not the cause. You can move all of the items that are in the Holding Folder back into C:\Users\[user name]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. Proceed to Task 4.
If the issue no longer occurs, then an account-specific startup item is the cause. To identify the exact startup item that is causing the issue, do the following:
- Open the Adobe application and try to reproduce the issue. Then do one of the following:
- If the issue still occurs, then repeat Steps 1 through 5.
- If the issue no longer occurs, then the startup item that you most recently reenabled is the cause. Remove it from the Startup folder, and contact the publisher of that startup item for information about the availability of updated version. Move all the remaining items from the Holding Folder back into C:\Users\[user name]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup.
Complete this task only if the account that you are troubleshooting is an administrator account and is not on a network domain.
Account-specific errors can occur if the account doesn't have full read/write access to the folders with the Adobe application preferences files and account-specific data files. You can use the icacls command to reset the access settings. Do the following:
- In the command-line window, type each of the following commands exactly as they appear below. Press Enter after each command.
Important: Type a space before and after each of the switches -- /T, /C, and /grant -- in every command.
icacls "%userprofile%\AppData\Local" /T /C /grant "%username%":F
icacls "%userprofile%\AppData\Roaming" /T /C /grant "%username%":F
icacls "%userprofile%\AppData\Local" /T /C /grant system:F
icacls "%userprofile%\AppData\Roaming" /T /C /grant system:F
Disclaimer: This task requires you to modify the Windows registry. The registry contains system-related information that is critical to your computer and applications. Before you modify the registry, make a backup copy of it. Adobe doesn't provide support for problems that arise from improperly modifying the registry. For more information about the Windows registry or the Registry Editor, see the Microsoft Help and Support site at http://support.microsoft.com.
If the issue still occurs, then a damaged registry entry is not the cause. You can restore the backup copy of the Adobe key by doing the following:
Disk damage that affects only a particular user account can cause an Adobe application to malfunction in that account.
To repair the system hard drive, see Repair and defragment hard disks (Windows 7 and Vista).
After you have repaired the drive, open the Adobe application and try to reproduce the issue. If the issue still occurs, then proceed to the next task.
If the application still behaves unexpectedly in a particular account, then copy (or move) all personal files into an account in which the behavior doesn't occur. Use the new account as your regular account.
For assistance with copying personal files to a new user account, contact the manufacturer of your computer. Or, go to the Microsoft Help and Support site at http://support.microsoft.com.