Over the past week, we have been experiencing strange behaviour where the latest version of Adobe Acrobat Reader DC is automatically upgraded to the Adobe Acrobat Pro version of the application. It's not until we blocked Automatic Updates using the "bUpdater" Registry Key that this behaviour has stopped. As multiple users utilise the system it may well be possible they are initiating the upgrade but as they don't have Windows Administrative Rights then it shouldn't be possible to upgrade the software.
Has this behaviour changed recently? I've noted another post in these forums from this month where their version was automatically upgrading from 32-bit to 64-bit and a new (undocumented) Registry Key was required to fix, bUpdateToSingleApp. Are these related?
Descargar archivo ✶✶✶ https://www.google.com/url?hl=en&q=https://psfmi.com/2yOK8k&source=gmail&ust=1719827604083000&usg=AOvVaw315L0eQU745RLfs8p9cZ5Z
Just thought I'd give you a heads up, I work for an IT firm and we have (so far) 3 different clients that have had nearly every machine upgrade itself from Adobe Reader 32-bit, to Acrobat Pro. It has broken a lot of things, and is definitely not due to users clicking upgrade, due to the simultaneous upgrade of all machines.
I've read this response a few times now. From what I can tell, it seems to suggest that Adobe is aware of this and it is not considered an issue. Should we just stop providing Adobe Reader to our customers and start looking for alternatives if they have no need for the paid Adobe apps??
I have already started to move clients to different PDF readers as a result. Unsure how such a huge organisation can have such a bizarre fault, it's almost like they're hoping people will just start paying for Pro...
We still have the exakt same issue, for a month now. We've moved to just using a web browser to open PDFs instead, but the customer really likes adding notes and such to the documents, which they have gotten used to doing in Adobe Reader. Its strange that they say "they're aware of the issue" yet say nothing about the issue in over a month.
I am having this problem right now. One user has an account, and when she opens Reader it goes and updates to full product.
I've tried a few of the registry changes, but this is still trying eveyr time a PDF is opened by this user on this machine.
Thank you Jamie and Meenakshi. As an update to this issue, we are still experiencing the problem, even with the two mentioned Registry Keys established in the environment. We haven't been able to identify what has been triggering the upgrade, so for now we have moved to another 3rd-party application for opening PDFs. When we receive a response from Adobe with a suitable fix we will look at testing this and reverting back.
Noticing the exact same behaviour on one of our customers shared terminal server. Ive tried disabled both the service for Adobe update, and the scheduled task for updating but it seem to be upgrading on its own anyway. Trying the bUpdater regedit fix now too in hopes of a solution..
We too have been having this problem with our terminal servers switching from Acrobat Reader DC to Acrobat Reader Pro DC totally on its own. the registry fixes have not worked and its causing major problems.
We are using a modified installer (Adobe Configuration Wizard). All Adobe Online Services AND the upselling are disabled in the installer file. But the Reader keeps upgrading itself to Acrobat DC, rendering the software unusable due to missing licenses for the full version.
I'm seeing this and have been chasing this for ages. The prevention in software policies don't work. The updater service is disabled but re-enables itself somehow. I de-installed and re-installed reader on Sunday and it's back to DC Pro again by today. Really ruddy annoying !!!
Its probably never being fixed if its been flagged as a known issue for this long. 6 months since an Adobe offical said "Yes, it is a related issue and the team is aware of it.".
Probably just another way of forcing people to pay for something they dont want..
The issue is that 64bit Reader gives people the option to sign-in with Adobe credentials. If you have any staff with a Pro subscription, they are able to upgrade Reader to Pro on the machine, without admin credentials. This should not be the case but Adobe refuses to acknowledge it being an issue. I'm guessing it's their way of forcing you to upgrade all staff to Pro.
These remove the Sign Out buttons from the upper right and Help menus. I added them to the Acrobat Customization Wizard so it automatically installs with the package but I suppose you can do it with GPP as well. If you don't want to reinstall Adobe, GPP may be your best bet.
I did NOT disable all Adobe Services in the Acro Cust Wizard because there are some that our staff use. I've heard you can disable that as well and it will work but I have not personally tested it. I just wanted a way to stop people from signing in, which prevents Pro users from being able to upgrade.
This shouldn't still be an issue for anyone since Adobe DC is now a Unified installer. If you don't have a Pro subscription, it will stay as Reader. If you have a Pro subscription and login, it converts your Adobe to Pro. Do you have the DC Unified installed?
None of us have a paid subscription, the company does not use a subscriptiont. We all had Reader DC, then we showed up Monday and had "you're decice needs to restart to install updates" and then we have pro. My biggest complaint is I can't figure out how to take a snapshot but the redact feature was very helpful.
As of late 2022 this was no longer possible - installing the 2nd app automatically unbinstalled the 1st app. Sometimes, a log in to the Reader app with a licensed user account automatically triggerred an install of Standard and an uninstall of Reader. That seems to be the the issue here.
I am not against Acrobat Standard or Pro (S/P) having Adobe Reader as a subset of the main program but I am against having to be logged into Acrobat S/P in order to view a PDF file. I have a couple of general use computers that several people use that have no Acrobat S/P licensing and only need to view PDF documents. They are not able to unless someone with a license is available to login. Other times users with credentials use these same computers and require the full ability of Acrobat.
That's fair, and another great example of how Adobe is causing unnecessary issues for their paying and loyal customers.
I have resorted to uninstalling 64-bit and then installing 32-bit versions of both applications and that is working, for now.
But I hope Adobe will allow users to install just the 1 app, Standard, and all the Reader features to be available without logging in.
I should qualify that by admitting I have encouraged our unlicensed users to create a free account and login to Reader just to save their signatures so that they can respond to our internal "please Adobe-sign this" requests.
But that's only because auditors like to see invoices with a big clumsy "Approved" stamps and a squiggle that looks like a signature next to it, when an simple email with "I approve the attached invoice for payment" would provide a superior audit trail. Oh well.
Finn OMahony
That's a regrettable position for Adobe to take, since it opens the door to 3rd-party PDF apps gaining larger market share. I have some users with Enterprise Adobe IDs to create/edit PDFs in Acrobat DC, but most users only need to quickly view/print PDFs with the Reader. If Acrobat Pro DC and Acrobat Reader DC cannot exist on the same device, that means it will be simpler for most people to use 3rd-party PDF viewers/printers (or let Microsft keep pushing Edge as the default for everything) -- and over time those users will get used to 3rd-party apps and stop perceiving Adobe products as familiar and useful.
I work with Financial Regulators and they have forms that we are required to fill in and that needs Adobe Reader to open and i can not edit them with Acrobat. while I have the Acrobat subscription I am forced to keep install and uninstall Adobe Reader /Acrobat as per the requirements, which is a pain.
I use Acrobat reader for confirming operation of above to how a user with Acrobat Reader only would view the documents and be able to manipulate. Also some PDF documents are stored in our database which prefers Acrobat Reader to be present.
seems like installing reader and pro 32 bit versions fixes the problem of not being able to install both. Though I imagine the 64bit version would work better or faster than the 32. Especially for things like compare pdf.
No it does not work, those files need only need Adobe Reader to Export to xfdf file for submission and wont let me use the pro version. There was a time I had both installed on my PC, but not anymore. Trying to figure out.
Amal, adding to the discussion some more. I have been using separate installations of Acrobat DC and Acrobat Reader DC on the same machine. On updating to a new computer, installing Actobat DC resulting in reader uninstalling. I use Reader to test that funcationality is working properly in Reader on forms created in Actobat DC... something I am unable to do on the same machine if Reader is unistalled by default.
What about SHARED computers where SOME users are licensed for Acrobat and SOME are not? Previously we could install both apps and the licensed users could use Acrobat and the unlicensed users could use Reader. Now one set of users will need to use a non-Adobe product. Very inconvenient.
Also, if Reader is a subset of Standard and Pro, why not allow unlicensed users to login to Standard and Pro and access only the free tools they'd get in the free READER version? That way both sets of users could use the same app.
Basically, i can open the PDF, fill the fields, save the document but when i reopen the document afterward, the content has disapeared. If i look at the same PDF with notepad, i can see the values next to the field but the values are not visible anymore in the reader.
Your form does not appear to be available on Ge.TT, so I can't test. I suspect that your form IS Reader Enabled, but that the use of viewers other than Acrobat or Adobe Reader is adversely affecting the data.
d3342ee215