Acrobat Reader DC processes remains in Task Manager after you view a PDF file

[il_yap64944289]

Hello. I have the same issue Acrobat.exe and Acrord32.exe Windows processes are open after closing browser

I have an application, which preview *.pdf files and processes remains in Task Manager after I closed the preview windows. How can I fix this issue?

[AnandSri]

Hello IL,

We're sorry for the trouble you had with Adobe Reader, please sign out from Adobe Reader, reboot the machine. Launch Adobe Reader back and sign in and check if this brings any difference.

Make sure that you have the latest version of Adobe Reader installed, check for any pending updates of Adobe Reader from help>check for updates, reboot the machine after updating Adobe Reader.

Have you tried the solution provided in the help article Acrobat.exe and Acrord32.exe Windows processes are open after closing browser

Reset the Adobe Reader's Preferences once and reboot the machine, to reset the preferences, take help from the help article How to reset Acrobat Preference settings to default.

If the issue persists, please use Acrobat cleaner tool to remove Adobe Reader Download Adobe Reader and Acrobat Cleaner Tool - Adobe Labs

Reboot the machine and install the latest version of Adobe Reader from Adobe - Adobe Acrobat Reader DC Distribution

If you still experience any issue, please create a test user profile with full admin rights and install Adobe Reader and check.

Let us know how it goes and share your findings.

Thanks,

Anand Sri.

[il_yap64944289]

- Make sure that you have the latest version of Adobe Reader installed, check for any pending updates of Adobe Reader from help>check for updates, reboot the machine after updating Adobe Reader.

I already have the latest version 18.011.20058

- Have you tried the solution provided in the help article Acrobat.exe and Acrord32.exe Windows processes are open after closing browser

No. Problem on multiple computers. Users can't use task manager every minutes, when application hung.

- Reset the Adobe Reader's Preferences once and reboot the machine, to reset the preferences, take help from the help article How to reset Acrobat Preference settings to default.

I havn't had Preferences folder in this path (Windows 10, 7/Vista) !C:\Users\[username]\AppData\Roaming\Adobe\Acrobat\[version])

[AnandSri]

Hello IL,

Install the latest patch of Adobe Reader from help>check for updates or manually from DC Release Notes — Release Notes for Acrobat DC Products

For testing purpose, create a test user profile with full admin rights and install Adobe Reader and check.

Let us know how it goes.

Thanks,

Anand Sri.

[Massimo23701767wkqo]

Apparently with the new 64bit branch of Adobe Reader, this old issue has come back to do some new damage. This is what is happening, according to my validation.

Each time "Adobe (Acrobat) Reader DC 64bit" is started, it appears to require a "minimum stay open time" that is between 40 s and 1 minute. Whatever you do, if you close the program with traditional methods before those ~40 s are gone, one process will stay there, and will prevent the user to initiate any other activity with the program till the "minimum stay open time" has passed by.

Performing exactly the same actions on the 32bit flavor, does not show the same behavior: in that case the process closes a couple of seconds after closing the program, which gives the user a proper experience.

The problem in adopting the 64bit flavor would be that a normal user would assume that "the program does not work", as trying to open a PDF file a few seconds after closing the previous one, will not succeed.

This has been verified on 22.001.20085 on Win10 21H2 clean install.

Hopefully Adobe will provide a fix to this issue in a reasonable timeframe.

[Paul27201727p7rg]

Hello,

I know this thread is now about four years old, but none the less I have finally found a solution which worked for me to fix this issue.

You have to grant access in your FW to the URL cc-api-data.adobe.io.

Ive found the URL when I was checking some Logs under the path C:\Users\xUserx\AppData\Local\Temp\NGL.

If you take a look at the log file, you most likely will find the said URL.

After releasing the URL on the FW, everything seems to work normally again.

I hope this helps some users which are still experiencing this issue.

BR
Paul