Acrobat closes instantly in Citrix session

[fbiermann90]

Hello,

we are trying to use Adobe Acrobat DC in our Citrix sessions.

Unfortunately the application instantly closes without error messages (not even in eventlog).

Adobe Acrobat Reader on the other hand works perfectly fine.

We already tried to troubleshoot the issue and even consulted the Citrix support.

Environment:

Windows Server 2016 1607

Adobe Acrobat DC 19.012.20035

Citrix Virtual Apps and Desktops 7 1808.2

Troubleshooting done:

-setting bProtectedMode 0 in registry

-delete C:\ProgramData\Adobe\SLStore

-delete ..\Roaming\Adobe, ..\Local\Adobe, ..\LocalLow\Adobe

-run as adminstrator

-run in compatibility mode

-disabled antivirus

-connecting via remote desktop connection to terminal server (in this scenario adobe acrobat works)

-uninstall remote desktop services (in this scenario adobe acrobat works)

[Amal.]

Hi Fbiermann

I am sorry to hear that, you are experiencing issues with the Adobe Acrobat DC as it keeps on closing without any error message.

As the application is with the latest version 19.012.20035, you may try to repair the installation. Go to Help>Repair Installation

Please try to reset the preferences of Adobe Acrobat DC and reboot the machine. To reset the preferences you may follow the help article here-How to reset Acrobat Preference settings to default. 

You may also follow the troubleshooting steps in the help article in the link - Troubleshoot Windows system errors, freezes | Adobe software

Let us know if that works for you.

Regards,

Amal

[fbiermann90]

Hello Amal,

thank you for your suggestions.

I deleted all acrobat preference settings already, but the behavior did not change.

I tried and followed the troubleshooting suggestions in your posted link, but unfortunately these did not fix the issue.

The very first startup of the application on the other hand is working fine (for example: after rebooting the terminal servers, the servers are reset to their base image and therefore the application is in its freshly installed state) but all following startups have the issue mentioned above.

So I tried to use 'Repair Installation' on the first successful startup but this also did not fix the issue.

I tried to comprehend which files are getting modified at the first startup so that all following startups are broken but I lost track.

Regards,

Florian