Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Update Problem Terminl Servers!

New Here ,
Jan 31, 2023 Jan 31, 2023

Unfortunately, there are major problems with Adobe Reader on terminal servers. The Adobe update service and the task start when you want it! It is not possible for us to permanently deactivate the update service via GPO or script and to switch it on if necessary to schedule the updates manually!
Even changing the reg entry in the registry does not lead to success! In other words, Adobe forces you to carry out updates, which is critical on terminal servers!
What is the solution to permanently disable the service for the time being???

TOPICS
General troubleshooting , Install update and subscribe to Acrobat
2.4K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Feb 01, 2023 Feb 01, 2023

Can you please clarify what exactly you are trying to achieve?

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 02, 2023 Feb 02, 2023

I would like to ensure that Adobe does not start installing updates sporadically. The update service should be permanently deactivated. 1-2x a month I check independently and install the updates. Adobe kicks us into the day so that users get problems with the reader!

 

Regedit entry does not work. The service can be deactivated, but it sporadically activates itself again! Everything useless!

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Feb 02, 2023 Feb 02, 2023

The only proper way to disable updates for a product is to use bUpdater registry value.

 

For Adobe Reader DC registry path on 64bit system is

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

Set bUpdater DWORD Registry value  to 0.

If you don't have Adobe Reader DC, registry path will be different.

Let me know if the above solution does not work for you, in which case please provide  Registry exports from:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Acrobat Reader\

and

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\Legacy\Reader

 

You can also refer to Basic Configuration — Deployment Planning and Configuration (adobe.com)

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 02, 2023 Feb 02, 2023

Hello, the DC version is not in use, but: Adobe Reader 2022.003.20314 Where to set the entry there?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 02, 2023 Feb 02, 2023

This is my path:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Acrobat Reader

Do I just have to create the folder "FeatureLockDown" there and then set the entry "bUpdater" with the value "0" ???

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 02, 2023 Feb 02, 2023

Its:

Adobe Acrobat Reader - Deutsch    Version: 22.003.20314

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Feb 02, 2023 Feb 02, 2023

According to this link Release Notes | Adobe Acrobat, Reader22.003.20314 was released on Continious track, which is DC

Your full Registry path to add bUpdater registry value is as I provided initially - HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

Yes, you have to create full path, including DC portion.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Feb 02, 2023 Feb 02, 2023

DC is build track, not a version. What is the name of the Adobe Reader you have installed? Does it have DC anywhere in the title or product name?

Best if you provide Registry export  from HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\Legacy\Reader so I can check what you have registered with Updater.

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 10, 2024 Apr 10, 2024
LATEST

I know this is old but we jsut went through this with Adobe Acrobat on a TS causing issues due to auto-updating and confciting with a crappy old LOB app client has to use.  bUpdater 0 can be used to disable Adobe Updates but if put in the wrong place also disables all cloud services including Request e-Signature.  For continuous track Adobe Acrobat (DC), 

the adobe instructions are terrible.  Basically adding bUpdater 0 here  -

 

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown\cServices

 

disables cloud services including e-sig requests.

 

To just disable updates, you only need bUpdater here:

 

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown

 

HTH

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines