Skip to main content
TomKaTom
Participant
December 30, 2018
Question

the preferences file is corrupt

  • December 30, 2018
  • 1 reply
  • 1890 views

Hi,

I've setup CC on a fresh install of win10 pro and every time I start illustrator I get this notification about the reset of my preferences.

I searched for some solutions but could not solve the problem.

What I#ve tried so far:

*) Illustrator preferences get corrupted frequently | Windows-only

This one was promising since I have multilanguage setup on my devices (DE & EN) Adobe and Windows are mainly running in the english version (en_US)

*) How to set preferences in Illustrator

Wasn't actually helpful. I did delete the two prefs files, but the error still appears

*) Preferences folder read-only error | Permissions issue

Despite there were no 'deny' settings applied I added extra write permission for users. Error still appears

*) I created my own workspace and saved it. After the next start the error appear again but I could find the saved workspace, selected it once again and restarted Illustrator and the error was gone - also on my 2nd workstation I use.

The workspace I saved was not synced to the other workstation.

So I solved the problem half way without knowing how...

This topic has been closed for replies.

1 reply

Bill Silbert
Community Expert
Community Expert
December 30, 2018

I would suggest uninstalling and reinstalling in the following manner:

In the app section of your Creative Cloud desktop app click on the “V” next to the app’s (Illustrator) name and choose the “Uninstall” option from the pull-down menu that appears. After you’ve run the uninstall then use the Creative Cloud Cleaner Tool Use the Creative Cloud Cleaner Tool to solve installation problems  . Then reinstall the program through the Desktop app. Before you reinstall, once again trash all preference files to make sure that your install is completely clean. Then launch Illustrator and see if the problem persists.

Hopefully, using the cleaner tool will delete whatever has been causing this warning to keep coming up.