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

[JR Boulay]

MOVED TO THE ACROBAT READER FORUM

[Test Screen Name]

You shouldn't need a link, since you clearly can see the post... !

But it is https://community.adobe.com/t5/acrobat-reader-discussions/disable-automatic-update-to-64-bit-reader-...

[Laurel5E3D]

I need this too.  I don't want to disable updates altogether, I just dont want to 'upgrade' to 64bit.

[amangupt · Accepted solution]

Hi @Laurel5E3D 

You set the below registry 

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown]
"bUpdateToSingleApp" Dword32 and set this to 0.

Setting this will ensure that only upgrade to 64 bit is disabled. Let me know if this works for you.

[Hall Computer5FB0]

Thank you @amangupt 

Why we had to have the last 3 weeks of pain, it would have been nice that all the RDS are going to auto break adobe. Without warning and then keep doing that unless the system has all updates turned off.

Fingers crossed 

[Hall Computer5FB0]

Still doesn't work auto updated over night

[amangupt]

@Hall Computer5FB0  I am not sure what's the exact workflow which you have tried. It might be possible that there are some stale registries on your machine causing the issue. I would suggest you use first uninstall the existing application. Then run the AcroCleaner tool ( or you could simply delete the entire registry hive for [HKEY_CURRENT_USER\SOFTWARE\Adobe\Adobe Acrobat] and [HKEY_CURRENT_USER\SOFTWARE\Adobe\Acrobat Reader] ). Then please install the 32 bit reader and before the first launch, run the above registry. This should fix your issue. If not, we can connect to debug the issue on your machine.

[defaultdqik199k668k]

Hey mate delete the service AdobeARMservice from the service.msc

You can  use command promt commands to delete it. Use below command.

SC DELETE AdobeARMservice

[edv-km]

Not working with current version? Tested on two different computers.

[Nicholas28208919nasf]

This "fix" doesn't work.

I have to ask... what's the point of going out of my way to purposefully download the 32-bit reader when Adobe is just going to F me and update to the all in one 64-bit? I CAN'T USE THE 64 BIT. This is Infuriating!

Does anyone have an updated fix for this? I'm downloading reader EVERY TIME I NEED TO USE IT because this dumb program keeps "upgrading" me.

[amangupt]

@Nicholas28208919nasf  Have you the tried this registry : 

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown]
"bUpdateToSingleApp" Dword32 and set this to 0.

If yes, then can you please share a screenshot of this

[Nicholas28208919nasf]

That can't be a serious question. This is exactly what I'm replying too. Yes, I'm about to do it for the 4th time today!

Instead of forcing users into the windows registry editor. Why don't you properly fix you program so I can use what I intentionally download and install?

Do you have a different fix for this "upgrade" issue?

[Mozzeh73]

Check this post I did in case you have a GPO that is reverting your setting.
Mozzeh73

[Dan29735674gkga]

How is this such a huge problem in 2023? I work in a medical setting and one of our critical pieces of software is not compatible with 64 bit. I've had to reinstall multiple times today, as I have every week for months, and I try every single thing that pops up in these threads. What kind of garbage management decision is driving these forced updates? It would be one thing if your registry hacks work, but they very clearly don't or we wouldn't have people digging these posts back up constantly. Just make the 32 bit only update to 32 bit and never upgrade. If we wanted 64 bit, we'd download it. It's pure incompetence that costs us literally hours a week. We're not going to renew our licences and move to another platform if we can't get a good resolution in the next month or two. 

It doesn't matter how many times you repeat the same registry hack. IT DOES NOT WORK. This is the kind of problem that was normal in the 90s. It is an utter disgrace to have this issue occurring for years in this age. 

[Mozzeh73]

Likewise, I have spent days trying to work out how this has updated to x64, we lost functionality of "BlackIce PDF" which is very important to our line of work.

I have then used SCCM to deploy x32 back to devices, but we now have duel installation of x32 and x64.
If only Adobe made a MSI removal tool so we could undo their mistake!!

Thanks for the reg keys I have impimented these into GPO to stop any repeat, but Adobe should explain why this happened.

[defaultremyegvk6wut]

dumb question since i am not an it guy.  is the registery entry for Dword32 that says to enter "0," is that decimal or hexadecimal?

[Mozzeh73]

Either, as long as the DWORD (32bit) is 0, but I always just use "Decimal" whe setting the value.

 If you use GPO you can drag these (attachments) into the reg key to add the required keys, these will stop it changing to x64 edition and block the users from updating from within the application.
GPO - Computer Configuration\Preferences\Windows Settings\Registry
It will then look like this:

Thanks
Glenn

[Hugo24511571vyqw]

A 0 is always a 0, no matter if you are using de decimal, binary or hexadecimal.

[defaultremyegvk6wut]

ok, thank you.  when going back in, it will not allow me to select decimal.  it is set as hex.  we will see if it works.  thank you.

[Mozzeh73]

Run regedit as administrator and it will allow you to edit it.
However as long as the value is 0 then the update option will be missing in Adobe

[Michaelomm]

This doesnt appear to work anymore. So far i have had 1 server do the update ignoring the registry entry that i have had in there for a month or two

[edv-km]

I can confirm this... please fix it @amangupt 

We need to urgent disable the x64 version as we have multiple problems on older clients while only viewing and on newer clients while printing.

[amangupt]

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