Prefilght window will not open

[janej15867342]

Just installed Adobe CC on a new windows 11 PC.   When I try to open the preflight panel from Acrobat DC the preflight window is greyed out with the message "Please wait while Preflight is loading profiles",  then a dialog box appears saying: "Unable to copy the user specific preferences" (See attached screen shot)  After that acrobat is unresponsive and I must kill it through the task manager.

I have tried removing the preference folder under appdata/roaming that I have seen in some other postings.  I have also tried reinstalling Acrobat.   Neither resolved the problem.   Does anyone have a recommendation?

[nicohirsch]

Sorry, I don't have a recommendation as I have the exact same problem on both of my PCs and none of the suggested solutions has worked for me either. I also run Adobe Acrobat Pro on windows 11.

[300nm]

Same issues past few weeks, really frustrating and hindering my workflow. At least it works on Mac for me so i check my files there.

Please fix it.

[janej15867342 · Accepted solution]

With the help of an Adobe technical support agent we have fixed the problem.   Under Preferences-> Security(Enhanced)  he unchecked "Enable Protected Mode at startup" and he unchecked "Enable Enhanced Security".   These two changes seemed to be the key.    At this point the preflight panel quit locking up and he then used the "Options" menu under preflight to import the default preflight profiles from the adobe directories under program files.   

It has resolved my problem and thankyou to the Adobe support folks!

[nicohirsch]

Thank you so much for sharing this solution here! It has fixed the problem on my PCs, too.

[Isaac5CB4]

Thanks so much, I've spent hours trying to fix this.

Why would Adobe not fix something like this!!!

[JAAGUP]

Thank you for this, finally fixed it! 

[AkanchhaS]

Hi everyone,

Glad to hear that the workaround has helped. 

And sorry to hear about your experience. This issue has already been escalated to the engineering team and reported as a Bug. Our team is currently working on it, and a fixed version will be released soon. 

As soon as we hear from the team, we will keep you posted. 

Thanks,

Akanchha