Adobe Reader 64 Bits

[Jules Altier]

Weve 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.

Acrobat & Reader DC October updates are live now containing the fix, please install the latest update from the help menu of the app>select check for updates, reboot the machine if possible after the update and check the functionality.

I am using Windows 10 21H1 and can print from Word, Excel, Powerpoint, Shoretel, Outlook , Chrome browser, Microsoft Edge, adobe reader 32 bit. Any adobe file 64 bit will not print. Do you have a fix yet?

No, they don't have a fix yet. I had to start a new thread which I bump every week or so. On October 29th they had a file from me they couldn't print either but haven't resolved it yet. So they are aware of the problem, but not enough people are making noise I guess so we get stuck with now 5 months of software subscription payments for something that doesn't work like it did before then.

Unable to print large format drawings from Adobe Reader DC 64 to my HP Designjet800PS 42. I can print pdf's to my other printers as long as they are letter size 8 1/2 x 11. Nothing larger. The 32bit version worked flawlessly. Its as if its not seeing the printer when the print size is changed.

This worked for me. But what a ridiculous solution - and not easy to find this solution on the web. For Acrobat on Windows 11 you go to Menu > Preferences > Security (Enhanced) and uncheck "Enagle Protected Mode at Startup." Then you have to Exit Acrobat and restart the App.

Thanks to all for the advice. But unfortunately, no change. Even tried using the HP print program, but no luck. Hopefully theres a fix in the works. It costs $10 a page to get them printed and sent to me. Costing me an arm and a leg right now.

When I tried to print a test page, I received an error code 0x000000cb, which says the system could not find the envioronment option that was entered. Which envioronment option is required for printing?

I am having this same problem, first it was a Canon IR 8580 but now also a Canon iPF6400. I'm a printshop so not being able to print is a problem. Some PDFs are fine. others won't work. I can't even send a blank page to the Canon iPF6400 right now. Same 2021.007.20091 version as you.

I noticed I changed from A3 to A4 and it printed, back to A3 and it wouldn't print. Sadly the plans Im working on are hard enough to see in A3. Any ideas. I called the pro line and they said they worked out there was a problem a week ago and they hoped to have something by the end of the week. Told me to use free reader for printing in the mean timewhich doesn't seem to be effected but not really an option. I also asked him to email me which he promised to do but then didn't ? Could hardly hear the guy on the phone

I'm facing similar issues, using Acrobat DC subscription based, after recent update 2021.007.20091 not able to print pdf to pdf getting error message "this document can't be printed" and then there was an error printing the document and it generates an output file with equal number of blank page.

I just went back to test my orientation fix on a file I had a problem with last week and it fails. I printed this same file last year without issue(I'm a print shop so this is a huge problem). In this case if I turn off 'secure print' or 'use covers' in the driver then it will work. But I shouldn't have to do that.

That same file I printed out of another PDF program without issue using both 'secure print' and 'use covers' in the print dialog. So it isn't the driver or the file. It's Acrobat.Pro DC. I am also working on Windows 10 64 Bit Acrobat DC 2021.007.20091

do whatever you do in print dialogue box, i mean settings, page size, scaling etc. but before u click on Print Button, just click the page setup button on the left hand side bottom corner n click ok. After that just hit print

That didn't work for me on the file I could print last year but can't print this year.

I even extracted just the first page and tried to print that and can't. (assuming I'm using 'secure print' and 'use covers' in the driver).

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.

Try clearing the C:\Users\kbinesh\AppData\Roaming\PTC\ProductView directory. I got this error many times with several clients, but I don't have one single solution which fixed all. Some fixes were downgraded to Adobe X, updated Creoview to latest version, disable security preference in Reader XI

Thanks for the suggestion, I have already done this. It has worked in the past on some clients but it does not always work. I have one client right now that I can not get fixed. I've uninstalled all remnants of ProductView, and Adobe reader. Cleared all AppData for both and did a fresh install of CreoView and Adober reader and still get the same results.

Hi Craig, I just see that you replied and got it working. Good to hear. I am including what I typed up to explain what is happening. You will probably see this issue come back as it could be tied to IE bit, but is directly tied to how Adobe is set to open PDFs in browsers and the short answer is set adobe and IE to open pdfs in your web browser, restart your computer and then it should work. Now for the long answer:

That is a general error to basically say Creo View is not able to use the Adobe add-in either due to it being turned off, or not available for the IE64-bit version. This issue depends on several programs/settings between Adobe, Adobe add-in for IE, and 64-bit vs 32-bit IE.

3a8082e126