Skip to main content
Participant
May 20, 2024
Question

Color Settings File not available in Acrobat

  • May 20, 2024
  • 1 reply
  • 1061 views

I have used Bridge to synchronize the color settings across InDesign, Illustrator and PhotoShop. This works fine. It is a color settings file I have created myself.

But Acrobat is not synchronized with the same color settings file and it is not available in the list of available color settings.

Also, it looks like Acrobat cannot see or find any of the color settings files I have made from PhotoShop.

- When using synchronize from Bridge this should also work for Acrobat?

- Why can't I see any of the color setting files I have made from PhotoShop in Acrobat?

Please help and advise.

Thank you.

This topic has been closed for replies.

1 reply

Brad @ Roaring Mouse
Community Expert
Community Expert
May 20, 2024

It should (does in my case). What System and versions are you running?

Participant
May 20, 2024

On my Mac (MacBook Pro M2 Ventura 13.6.6) it seems fine, but on my Win 11 laptop is where the problem lies.

That is Acrobat 24.2.20736.0. All the other apps, PShop etc are 2024 latest versions.

Brad @ Roaring Mouse
Community Expert
Community Expert
May 20, 2024

I just checked a WIn 10 & 11 system, and yes, I see the same thing.

However, I did a search on this and, from another thread, it seems to be an issue with Protected Mode disallowing the ability to select a custom setting. If you go to Acrobat > Preferences > Security [Enhanced] and turn off Enable Protected Mode, (restart Acrobat), custom .csf should then appear in the Color Mangement settings and will also report your Synchronized status. This, of course, defeats the benefit of Protected Mode, so tread carefully. I'm guessing their thinking is, since a custom .csf could possibly be crafted into a malicious agent, Protected Mode is preventing all but the ones part of the default installation from loading. Someone else may know more on this and chime in, but that's my best answer to you right now. Apparently, Protected Mode used to be shipped OFF by default in previous versions of Acrobat, but lately it ships ON by default, which might explain a change in behaviour in your situation. (btw, this same setting in Mac Acrobat does not cause this issue).