After update to 17.011.30142, crashes after clicking enable all feature

[uncleremus]

We have a pretty secure environment. Protected mode enabled, FIPS, no trusted sites, etc. After we upgraded to 17.011.30142 when we open a PDF and get the prompt to enable all features. Acrobat freezes and than crashes. This doesn't happen to all PDF's. Any created in house seem to work. Fillable PDFs that were created externally seem to be the culprit. If its an external document that's not fillable (like some saved a .docx as a pdf) it seems to work fine.

I confirmed that the issue was caused only by updating Acrobat to the noted version (no other updates or policy changes) as I could open any pdf before the update and as soon as I updated Acrobat the freeze happens.

Disabling protected mode and rolling back the patch are not in the cards... CTO/CIO does not want too.

[Meenakshi Negi]

Hi Uncleremus,

Sorry to hear that.

Could you please provide more details as asked below?

- You have mentioned that the issue occurs when you open fillable PDFs created externally. Does that mean those files are received from an external source?

- Would it be possible to share any sample PDF on which the issue occurs? How to share a file using Adobe Document Cloud

- Are those files saved on the machine or on a network drive?

- What is the OS version on the machine?

We will be waiting for your response.

Regards,

Meenakshi

[MyAdobeScreenName1]

I have the exact same problem with release 17.011.30142:

• Our OS is Windows 10 64bit build 1709 w/latest MS patches.
• ALL .pdf fillable forms 'hang' when opened with "Acrobat Pro 2017' after the Enable All Features button is pressed.
• These same forms will open and can be filled using 'Adobe Reader 2017' v.17.011.30142 on the same systems.
• The forms fail if opened from any location such as local drive, UNC path, etc.
• We are required to have the following policy/value set (which causes the prompt to 'Enable all Features':
  HKEY_LOCAL_MACHINE\Software\Policies\Adobe\Adobe Acrobat\2017\FeatureLockDown
  Value Name: iProtectedView
  Type: REG_DWORD
  Value: 2
• If I set the above registry value to "1", opening a fillable .pdf in Acrobat throws the message: "This form cannot be edited in Adobe Acrobat. Please use Adobe LiveCycle Designer to edit this form." - so is this a new change with this version release? Could this pop-up message not being displayed when the iProtectedView value being set to '2' be causing the hang?

[Meenakshi Negi]

Hello,

Sorry for the delay in response.

We have recently released an update for the application. Please update the applicaiton and check if you still experience the same behavior. You may refer to the following link to get more details on the update for the application.

- Release Notes | Adobe Acrobat, Reader

Please let us know if the issue persists.

Regards,

Meenakshi

[chrisniz99]

We have the same problem in my organization, also in a secure environment with the same settings. This only happens after we click "Enable All Features".  However, this doesn't affect only secure forms, and doesn't affect the same forms for the same users (which means FIPS and Protected View are not the culprits).  One form might work fine for me, but not for my neighbor or a handful of others.  And vice versa - a form that does lockup Adobe Pro for me may not cause that issue for my neighbor.  Same computer configuration, same Adobe Pro setup.  We found 2 workarounds - for Secured forms when this happens, disabling FIPS resolves the issue.  When disabling FIPS is not an option or when the PDF in question is not secured, there is another temp solution - open the PDF in question, open Task Manager, expand the "Adobe Acrobat 2017" process, select either of the Adobe Acrobat Reader 2017 sub-processes (doesn't matter which) and end the task.  Within a few seconds, Adobe Pro will start responding and function properly.

Watching Task Manager while using a form that doesn't lock up, those Reader sub-processes are supposed to end on their own after clicking "Enable All Features".  So it appears something is preventing that from happening.  But why only some forms and why different forms for different people, your guess is as good as mine.

Edit:  Also wanted to clarify that this is not only affecting externally developed PDF forms, it is impacting internally created forms as well. Doesn't seem to matter who created them or how they were sent.  Opening the PDFs in Adobe Reader does get around this as well, but since we are frequently editing the PDFs, using Reader isn't always an option.