We are in medical and use adobe reader 32bit, and it hast to be 32bit for the majority of our software. We are seeing several machines automatically updating to 64bit which is incompatible with our software.
I see multiple threads regarding this but all are using hard blocks on updates. We need to support security updates and stop the auto update to 64bit at the same time, we cannot just block all updates via registry.
What can we do to maintain just the 32bit version?
Hope you are doing well and sorry for the trouble. As described the Adobe reader 32 bit is automatically updating to 64 bit.
Please check out the suggestion provided in the similar discussion https://community.adobe.com/t5/acrobat-reader-discussions/how-can-i-make-32-bit-reader-update-to-onl... and see if that works for you too.
This is not going to work for us for more than a week or two. We need to be able to update adobe but still maintain the 32bit version. The solution you linked stops all updates for adobe, and that would leave us wide open without updates.
Please use the solution described by @Ravi Gour in the https://community.adobe.com/t5/acrobat-reader-discussions/adobe-reader-changing-itself-to-64bit-when... thread.
To revert back to 32-bit version of Reader, please uninstall 64-bit Reader, install 32-bit Reader from https://get.adobe.com/reader/otherversions/ (select 32-bit version to download from dropdown).
Create following registry key to block automatic upgrade
Key: bUpdateToSingleApp , Value = 0 , type = dword
Location : HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown
Is the key "bUpdateToSingleApp" a new key? I am unable to locate the support documentation and my understand is that the only key supported here is just "bUpdate".
What about the key Mode? If we were to create "bUpdateToSingleApp" will mode continue to update to 64bit automatically or will it now update only 32bit updates?
Additionally it was reported in the thread you have linked that the "bUpdateToSingleApp" key ravi mentioned did not work for that user.
Yes, this is a new key introduced. Please try the following stpes
1. Uninstall 64-bit Reader installed on the machine.
2. Restart the machine (optional step)
3. Create the key to block the upgrade
4. Install 32-bit Reader from https://get.adobe.com/reader/otherversions/
What a mess, why doesn't Adobe inform us that this is happening? We are distributing filea ssociations using group policy, this sets .pdf files to AcroExch.Document.DC, but after the automatic update, this changes to Acrobat.Document.DC. Since this is not correct after the group policy is processed (it uses the AcroExch.Document.DC setting again), the end result is that Google Chrome is the default PDF viewer for users now. It took me several days before I figured out what the cause is and was pulling my hair out why Acrobat Reader was updated to Acrobat DC, but when you start the application it presents itself as Acrobat Reader again.
This changed messed with Outlook's PDF preview handler, after 64-bit version of Adobe is uninstalled. How do you fix it?
I am using Office 2019 (64-bit) and latest Adobe Reader version (32-bit).
Hello, thank you for this. Could you clarify if this only blocks the upgrade of x32 to x64 versions OR does this block all updates? For example, we need to stay on x32 but still want security updates.
This key only blocks x32 to x64 upgrade. Security patch updates for x32 will continue to work.
I truly wondering who's the geniuses behind this extremely intrusive update! What sort of value added thing that can be achieved by forcing update without user consent? Think producttive function guys, don't add unneccessary work to other people for your own work benefits!