Disable automatic update to 64 bit Reader DC

[Clinton Mac]

Hi,

We've got some legacy software that is hard coded to run with the 32bit version of Reader DC.  We're finding that our software is automatically upgrading itself to the 64bit version, which causes our legacy software to fail.

Is there any way to disable this automatic update?  I've tried disabling the AdobeARMService, and it hasn't helped.

Thanks

[edv-km]

[amangupt]

@Michaelomm can you please share a screenshot of the registry so that we can check whether it is created correctly or not?

[Jennie243907384c2q]

Amended“Mode” DWORD record and change the Value Data field from “3” to “0” Please find below the location of the Reg entry:

·         Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\Legacy\Acrobat\{AC76BA86-1033-1033-7760-BC15014EA700}

This is impacting the programs not developed for 64bit that use Adobe Reader 32 bit for Print. It is only designed to run with the 32-bit version of Adobe Reader so a Fix is needed urgently

Help appreciated

[GBarnes_DPS]

There seems to be a bug where if a user logs in with their Adobe account with an active subscription and accesses a pro feature, they'll be asked if they have the right version of Adobe installed.

Whether or not they have administrator rights, if they download the product and in my case, decline execution of the file, shortly after closing Adobe Reader, it will auto upgrade to 64-Bit.

I made changes to the product by disabling all the upsell settings in reader to reduce the possibility that users could click on one of these menu options. Lockable Settings (adobe.com)

It's clear though that the advised key alone doesn't work any more and we require something more robust.

[Jennie243907384c2q]

Ideally need a fix to stop Adobe auto-updating to 64 bit

I have done the following to no avail trying to FORCE adobe to stay on 32 bit but automatically swaps to 64 bit:

• Disabling and deleting the Adobe Acrobat Update Task in Task Scheduler
• Disable the service “Adobe Acrobat Update Service” and ensure it doesn’t start-up
• You need to amend the “Mode” DWORD record and change the value Data field from “3” to “0” Please find below the location of the Reg entry:

·         Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\Legacy\Acrobat\{AC76BA86-1033-1033-7760-BC15014EA700}

The string of numbers on the end may differ.

This is impacting the program SLI that uses Adobe Reader 32 bit for Print. It is only designed to run with the 32-bit version of Adobe Reader there for a Fix is needed

Help appreciated

[Mozzeh73]

These are the registry keys I use in my GPO and no Adobe installations have updated to x64 nor updated directly from the application since. (we use SCCM to deploy updates) 

Windows - Computer - Adobe Reader Disable Updates

Computer Configuration (Enabled)

PropertiesHive HKEY_LOCAL_MACHINE
Key path SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown
Value name bProtectedMode
Value type REG_DWORD
Value data 0x0 (0)

PropertiesHive HKEY_LOCAL_MACHINE
Key path SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown
Value name bUpdater
Value type REG_DWORD
Value data 0x0 (0)

PropertiesHive HKEY_LOCAL_MACHINE
Key path SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown
Value name bUpdateToSingleApp
Value type REG_DWORD
Value data 0x0 (0)

[Mozzeh73]

1. Uninstall 64-bit Reader installed on the machine.

2. Restart the machine

3. Create the key to block the upgrade

• [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown]
  "bUpdateToSingleApp"=dword:00000000
  [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown]
  "bUpdateToSingleApp"=dword:00000000

4. Install 32-bit Reader from https://get.adobe.com/reader/otherversions/ 

• select OS  & langage from drop down
• select 32-bit Reader from drop down and then install 32-bit Reader.

---------------------------------------------------

[BeHaberman]

This is an ongoing issue with dumb VPN laptops we deploy to WFH approved users. Adobe Reader is installed to the laptop image. It shows itself on the laptop user desktop as "Adobe Reader". Then at some point after the user takes the laptop home, Reader updates from x32 to x64, and swaps out the icon for a "Adobe Acrobat" icon instead. Just, why?

Because then the user sees this on their dumb terminal VPN laptop and thinks WE THE IT DEPT remote installed them sweet sweet Acrobat Pro and tries to go hog wild with it. Only it's not. And then they complain to mangement that WE THE IT DEPT lied to THEM about "Acrobat installed to their computer".

Acrobat Pro, when licensed to a user, IS installed to their office workstation. Never the VPN laptop.

Really, Adobe. Why you do this? Reader is Reader is Reader. Stop labeling Reader x64 as "Adobe Acrobat". Stop lying to your users.

Anyway, the GPO key fix works for our office workstations that don't have Acrobat Pro installed. But these VPN laptops aren't on the domain. And the local reg key fix on our VPN laptop image server? That's hit-or-miss. We really could use a permanent fix.

[Test Screen Name]

I wonder if the user is clicking on an item like "Edit PDF" in Acrobat Reader. Or the "rotate pages" icon. Or whatever. This would cause an upgrade to a trial version of Acrobat, since this is the job of Reader...

[BeHaberman]

I mean, yes, this happens a lot, with in office and WFH users. But the real point is that the "upgrade" from Reader x32 to x64 should not CHANGE the icon name, and that everybody gets frustrated at false advertising, and that IT dept's can't 100% prevent the "upgrade"!

[Raman33113694k2xl]

Disabling Automatic Updates via Windows Services also gets over-ridden to our frustration!  This is such simple thing to implement!  It appears that the Support folks are NOT communicating with the developers and implementers.  Sad & Shameful!