Adobe Acrobat Reader (64-bit)
Rosella Bowlan
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.
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.
@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.
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!
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.
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.
Is this a behavior with a particular PDF file or with all the PDF? Please try with a different PDF file and check. if the file is stored on a shared network/drive please download it to your computer first and try again.
However the workaround, to uninstall the 64-Bit Version and install 32-Bit Version helps, but not for long - because after a certain amount of time, it updates automatically to the broken 64-Bit Version.
We are still having issues with Adobe updating from 32bit to 64bit. We are IT for Dental offices and their software will not work with Adobe 64. We have tried to do the Registry fix, disable adobe update services, and disable adobe update in the task scheduler. It still finds a way to update and sometimes within seconds of installing the 32-bit version. Can anyone shed any lite on this?
We are sorry to hear that. Would you mind collecting the Adobe CC Logs -cloud/kb/cc-log-collector.html and procmon logs -docs/acrobatetk/tools/Labs/acromonitor.html and share them with us via document cloud link as described here -cloud/help/sharing-pdfs.html so that we can isolate the issue for the fix.
We are having the same issue here on all 100 PC's. Everything prints except adobe reader 64 bit. No error doesn't even ghet to the printer queue. I uninstalled 64 bit and put in 32 bit but it updates to 64 bit shortly after. Are you aware of the problem and are you developing a fix?
We are also having the same problem. 32bit is fine but the problem is it auto updates the 32bit version to 64bit. Surely this would be a big issue on Adobes radar? Its taken some time to get any official comment on this.
I've confirmed that on all the workstations I've manually updated as an administrator, the new version corrects the issue between Adobe Acrobat Reader 64bit and Trend Micro WFBS. Printing is working now, thank you.
I've always left Acorbat to it's own devices when it comes to automatic updates and generally they seem to happen in the background without user intervention or the need to elevate to an administrator. In order to update manually though, it appears you require admin rights. Do you know when or what triggers the automatic update? Is there a flag that Adobe sets to publish for manual update checks vs automatic? I haven't seen any machines move to v22.1.20085 as of yet.
I know that this can be fixed by changing the name of the "server" in the viewer output profile. This is how I have fixed it every time before. Currently I have it as "acroviewR21", which has worked this year until today. Usually it can be fixed just by updating the year, but since it is still 2021 (as is my version of acrobat reader DC), I am really not sure what to do. I have tried various permutations of the capitalization to no effect. I have tried making it 22 with no effect.
I have some experience using VBA, and I am interested in using "Adobe Acrobat 10.0 Type Library" to be able to open the adobe reader app within VBA and manipulate or extract information in adobe acrobat reader pdf files.
I was able to run this procedure, but only with adobe acrobat pro, which I had to get by getting the adobe creative cloud subscription. It will not work with the adobe acrobat reader, which is the free edition.
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
This package installs/upgrades the Multi-lingual ("MUI") release. In some cases, this package will by default be able to install over the top of a language-specific installation. Otherwise, this package will exit and require either a manual uninstall of the language specific installation or having the parameter '/OverwriteInstallation' set to do this automatically.
If the package fails on Windows 8.1 or earlier, this might be due to the installation of kb2919355 (which is a dependency of this package) if your system is not up-to-date. This KB requires a reboot of the system before the adobereader package installs successfully.
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
64591212e2