Participant

Question

Adobe Reader 10.1.3 uses max CPU when closed

Forum|Forum|13 years ago
June 13, 2012
6 replies
57284 views

We're having the problem where Adobe Reader uses all of a CPU core when a user is closing the program but the .exe file is still running in the background.

We're running 10.1.3 and have been using that since it was released but the problem just recently started. It's running on top of Windows 2008 SP2 with Citrix XenApp 5.0 installed and using DFS.

The trick with denying the user access to the "cRecentFiles" in the registry don't seem to solve the problem.

Anyone who knows a way to solve this?

This topic has been closed for replies.

A

amanera

Participant

Hi there. I've found this that solved the problem in my Windows 10 system:

High CPU usage by Acrobat after closing | Windows 8

The registry entry was path not exactly the same that the one described in the article, but it is very close.

Instead of

Navigate to the key: [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]

you should

Navigate to the key: [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store]

D

danarothrock

Participant

This problem of 100% CPU utilization after closing Adobe Reader (.exe program persists and continues impacting all processes) is still occurring in version 11.0.11 on Win 7 OS. Adobe can't fix it.

V

vdobhal

Adobe Employee

Hi,

Is somebody still seeing the issue?

Thanks,

A

Anonymous

Yes, I am. The fix(es) provided in this thread have not solved the issue. I created a new post to see if anyone could assist further.

My post

If you have any suggestions it would be greatly appreciated.

A

Anonymous

Our users are having the same issues with Adobe Reader 10.1.3. All of the above (disable all messages, delete message cache, clear recent files and disable Welcome Screen) have been tried and work, but only temporary. After a week or two, the users have the same problem again. Did any of you experience the same behaviour, or does the above mentioned work as a permanent solution?

The only thing that seems to be a permanent solution for us is disabling the protected mode, which we don't want to do. I opened a support case for this, but without a support contract (which we don't have and which doesn't exist for Adobe Reader) they say they cannot help.

A

Anonymous

We set both these current user registry keys on all existing computers under the user's context and have not seen any issues.

We also redid our MST to automatically set these registry keys for any new installs.

HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\IPM]

DWORD "bShowMsgAtLaunch" to 0

DWORD "bDontShowMsgWhenViewingDoc" to 1

A

andykn

Participant

How can you set the Current User keys in the mst for new installs?

V

Volnation

Participant

Disabling the Welcome screen fixed this for us.

See http://acrobatninja.blogspot.com/2011/09/acrobat-and-adobe-reader-1011.html for details on the registry entry to use. It is for 10.1.1, but worked with our 10.1.3.

J

je79aypsAuthor

Participant

Our problem was the ReaderMessages files. For more info see this: http://forums.citrix.com/thread.jspa?threadID=308672

B

Boilermaker_Nation

Participant

I implemented the deselection of the "Show Me Messages When I Launch Reader" via a Group Policy logon script. It's in a registry key (DWORD value) located here:

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\IPM]

Set/create the DWORD "bShowMsgAtLaunch" to 0 will do the trick going forward. Set/create the DWORD "bDontShowMsgWhenViewingDoc" to 0 as well.

I also delete the ReaderMessages file via the same logon script. It is located on XP here:

%USERPROFILE%\Application Data\Adobe\Acrobat\10.0\ReaderMessages

and located on Vista/7 here:

%USERPROFILE%\AppData\LocalLow\Adobe\Acrobat\10.0\ReaderMessages

When the reset is implemented via Group Policy, the key gets reset back to 0 if a user messes with it.

Message was edited by: DJFEHRIB

If you have Adobe processes (AcroRd32.exe) showing in the task manager after you close the Acrobat Reader that use up a significant amount of processor speed. This is what you can do to fix it.

Basically the file that is used by the welcome screen (ReaderMessages) has become corrupted (that file is located here on Windows 7 C:\Users\%UserProfile%\AppData\LocalLow\Adobe\Acrobat\10.0.) Deleting that file did not help on a long term basis, but by disabling the welcome screen it bypasses that file and will close normally. Unfortunately Adobe does not have a built in way to disable the welcome screen but you can disable it by making a small addition into the registry.

1. Open the regeidt and navigate to
1. a. HKLM\SOFTWARE\Policies\Adobe\Acrobat Reader\10.0\FeatureLockDown

2. Add the a key with the name
1. a. cWelcomeScreen

3. Add a DWORD value to that key
1. a. bShowWelcomeScreen = 0

It should look like this when your finished

The welcome screen should not show when you open Acrobat Reader, and when you close the window the process should close with it. If this fix does not work for you, there might be something else causing your problem.

A

ambitious_Zenith1549

Participant

We are experiencing this same exact problem, but with 32-bit Windows XP PC's. Looking for a solution.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded