Acrobat Reader Old Version 11

0 views
Skip to first unread message

Nathen Paisley

unread,
Aug 4, 2024, 11:22:35 PM8/4/24
to procenrati
Secondwhile I have the latest updated version of OS on my iMac, my printer, Canon Prima MX870 series 2, does support duplex printing and I use it all the time for duplex printing my word documents I send to the printer, I cannot figure out how to duplex print my adobe reader PDF files or any PDF files for that matter. I have followed all instructions that I could find about how to turn it on, however none of the instructions work. I have clicked on "printer" and when my screen comes up it shows duplex printing "off" in light gray and I cannot change it to "on" and no where on my iMac screen does it show anything called "properties" which some other instructions tell me to click on.

The instructions worked in find the version of Adobe Reader I have; I found I have version 2015.010.20056, but I am not sure how this relates to the 10.3.1 that the instructions say. I thought that I had downloaded the most recent version but does the 010.20056 means I only have version 10.2 and need to down load a newer version to get duplex printing?


Sorry, I guess I have been working on this too long I meant that I have been told I need to have 10.1.3, not 10.3.1. But still nothing is working and the instructions about duplex printing do not help to turn on my duplex printing.


If you're on a Mac, About Acrobat Reader is not on the Help menu but on the app menu (the first one after the apple, with the name of the app). This should be the same for all apps, so it's easy to find once you know how.


2015.010.20056 is still pretty old (but much less old than 10.2). It came out almost 2 years ago. I suggest you check for updates, which you can do via Help > Check for Updates. This is supposed to be automatic, so it might tell you about a problem. Please let us know where you get to.


I did what you suggested, went to help and clicked on "check for up dates." It said that my Adobe Acrobat Reader is up to date. What do I now? What is wrong? You say I have an old version and it says I am up to date?


I keep getting this in every browser. The document you are trying to load requires Adobe Reader 8 or Higher. You may not have Adobe Reader installed on your viewing environment may not be properly configured to use adobe reader.


The form you are attempting to open is a dynamic XFA form. These forms can only be opened in an XFA aware reader, which basically means Adobe Acrobat. You must download it and open it with acrobat/reader in order to view it.


Acrobat Reader is a type of freeware developed by Adobe systems as a .pdf reader (Portable Document Format). Users can view, print and email .pdf documents along with newer premium features which include converting files to .pdf and vice versa and creating professional, interactive fillable forms such as questionnaires or application forms. Acrobat Reader automatically installs a plug-in for Netscape Navigator allowing users to view .pdf forms through their web browser.






AdobeReader is a must-have software for viewing PDF files. OldVersion.com offers quickand free download of Acrobat Reader. Our site has several popular versions ofAcrobat Reader, which are free from viruses, malware and spyware. From AcrobatReader 1.0 for DOS to Acrobat Reader 11.0.01, we are your one-stop online communityfor installing Acrobat Reader. Not sure which version is right for you? Ask our passionate online community of old software below!


When you upload software to oldversion.com you get rewarded by points. For every field that is filled out correctly, points will berewarded, some fields are optional but the more you provide the more you will get rewarded!


An update on this one, the September 16th release brings a new capability for the Flexera agent to recognize the activated edition (for all users who have logged in the last 90 days on a computer) of Acrobat by reading the "ActivationLevel" registry entry.


Make sure that your inventory settings let the "InventorySettings.xml" to automatically take the latest version (66) and you will take advantage of this new data collection. More information on: -6/RN-chg-AgentAdobeExtension.html


Done some more research and it seams that a registry value needs to be read to set the correct product to reader. It might be possible to have a workaround in the agent to add the registry key and evidences, but will go for a ticket to the content team.


Our plan is to stop using the ambiguous add/remove program evidence from Acrobat DC, add it to Acrobat Reader, and enhance the WMI evidences we use for Acrobat DC (Created from the SWIDTags that have not been systematically managed in the last versions), with the patterns below.


I would prefer we use the existing WMI evidences collected from the SWIDTags than change the agent to collect a new registry entry (by the way, thanks for your investigation, I had found the IsAcrInstalledInRdrMode in the same node but the key you provide looks good!).


@nrousseau1 It seams that I do not have any newer Acrobat WMI evidences in the FLX_Adobe class. Could that relate to this issue since we are running the onpremise 2021r1?

Known Issue: Adobe Acrobat 2020 edition does not get recognized based on inventory gathered by the F... - Community (flexera.com)


You can run the query below (you can uncomment to get only the computers where 2021 Continuous Pro exists but performance is poor) and hopefully will see many records. Can you confirm this? I can verify this with other customers.


You are right Acrobat reader as a common add / remove program evidence, but no WMI. So, you could theoretically ignore the add / remove evidence and add the WMI... The issue is that you can't make WMI evidences clever (for instance 21.%.20%), unless inserting them in the database.


We have a few sites which has the Adobe Cloud products and can see very few results and I can also see a lot of leftovers from earlier versions. For our major sites we run FRL-Offline 64 bit package and they do not show up in the query with/without the uncomment rows.


Hello Nicolas! Based on your comment Our plan is to stop using the ambiguous add/remove program evidence from Acrobat DC, add it to Acrobat Reader, and enhance the WMI evidences we use for Acrobat DC (Created from the SWIDTags that have not been systematically managed in the last versions), with the patterns below. When do you think you'll be getting something in place?


Hello @JenMaier , please check also on your side. We are looking for confirmation that data is here and consistent to extend the ARL (and remove the link to the add remove program)... your help will be useful confirming this. Then, this is a matter of a week to wait for the next ARL build. Thanks for sharing your observations.


The fact older versons appear, related to swidtag files that stay after upgrade (unless the WMI evidences are here even when applications have been installed) should not be a big issue as consomption will not be augmented...


@mag00_75 , could you please share by email nrou...@flexera.com the extracts of a computer deployed with FRL-Offline 64 for installer, file and WMI evidences tabs. We need to find and accurate evidence...


@nrousseau1 After the new ARL it looks better, however still need to be extended for the 22.xx releases of Acrobat DC Reader, Standard and Pro.

I have mailed you some screenshots and Swid from our FRL-Offline installations, and the NDI files are included in the support case.


So, what happens if you are not using the FlexNet agent and are getting inventory from JAMF and SCCM? WMI does not really come in. Why can't Flexera use a combination of Distiller and Acrobat to determine if it is not Reader. That would seem to be a pretty direct way of identifying at least free versions from paid versions.


I tested the swidtag by uninstalling the Pro version, rebooting, reinstalling from CC Desktop and the swidtag did not get updated, so no, i don't trust those entirely. Once I reinstalled, I show one entry for Adobe Acrobat Reader DC and then another for Adobe Acrobat DC (the Pro version - see attached). I am working with our packaging team to add Pro to our deployed packages.


I'd be careful on the suite, unless you do one massive piece of file evidence that can be applied against different versions (for example, Adobe DC shows up as 22.x but Distiller is 21.x - so the required could kill that idea, but Distiller is the best way of determining Pro/Standard from Reader.


see attached for file evidence. I think one of the real problems is that AcroRd32.exe appears in both versions. However, acrobat.exe is unique to the Pro Install, as is AcroBroker and AcroDist. But the distiller version can differ from the executable. The Pro version executable has no file size, so not sure why that is not being distinguished from the Reader Version


Greetings to everyone on this thread. Just wanted to share my personal experience on this topic.



Yesterday my local install of Acrobat Reader on my Windows 10 machine self-upgraded to version 2022. After the upgrade:

1 - My Add/Remove Program Name simply says "Adobe Acrobat DC".

2 - My Start Menu now says "Adobe Acrobat DC"

3 - The Start Menu shortcut launches ACROBAT.EXE



So, looking at my Installer and File Evidence, it is now the same as if the full version of Acrobat DC is installed.



And, when I launch Acrobat DC from my Start menu, it does in fact launch Acrobat Reader. When I go to Help


Upgraded to MacOS Sonoma 14.0 October 7 2023 and now I cannot print any pdf files from Adobe Reader. Error Message says "The document could not be printed" "There were no pages selected to print". Adobe wants $ to convert to Word. Cannot "Select all" and copy to Word or Pages. Cannot "Select all" and print selection. Same issue with all pdf's. Work around is to open pdf file in Open Office Text and print from Open Office.


After several months of putting off figuring out this "Adobe PDF not printing" issue, I just found this forum. I have Sonoma 14.1.2 and an Epson Workforce printer. It is fixed (for me anyway) now by deleting my Adobe Reader application and reinstalling the new version 2023.008.20423. Looks like someone, somewhere fixed the issue. Works perfectly now.

3a8082e126
Reply all
Reply to author
Forward
0 new messages