Skip to main content
J
je79ayps
Participant
June 13, 2012
Question

Adobe Reader 10.1.3 uses max CPU when closed

  • June 13, 2012
  • 6 replies
  • 57273 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.

      6 replies

      A
      amanera
      Participant
      August 21, 2015

      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
      July 5, 2015

      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
      Adobe Employee
      vdobhal
      Adobe Employee
      February 5, 2014

      Hi,

      Is somebody still seeing the issue?

      Thanks,

      A
      Anonymous
      June 20, 2014

      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
      August 14, 2012

      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
      August 14, 2012

      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
      August 29, 2012

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

      V
      Volnation
      Participant
      June 15, 2012

      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
      June 15, 2012

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

      A
      Anonymous
      June 19, 2012

      We are having the same issue on both Win7 64bit and XP 32 bit.  The ReaderMessage file seems to be the issue with incorrect entries in the file as mentioned on page 2 of the above mentioned Citrix forum link.  The issue happens by just opening and closing Reader from the Start - Programs menu.  When it's closed, acrord32.exe stays in memory using 50%+ CPU cycles.  Replacing with a good ReaderMessage file in the user's profiel seems to be a work around.

      Anyone from Adobe have a root cause of how we can prevent this corruption so we can proactively stop this from happening on our PCs?

      A
      ambitious_Zenith1549
      Participant
      June 14, 2012

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

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices