Re: Adobe Acrobat Reader Dc Pro Free Download
Nichole Wernett
I've noticed that since the Adobe Acrobat Reader v2023.001.20064 upgrade, the 'Remember current state of tools pane' not working. Each time I close the tools pane, and then select the 'Remember current state of tools pane' option, and close Adobe, then next time I open that or any other PDF the Tools pane shows up. The option seems to be broken, and not persisting. Has anyone else found that to be the case, and is there a working solution to the problem?
Yes, I am experiencing the same, very annoying, behavior. I have checked 'remember current state of tools pane' and closed the tools pane--but it reopens everytime I open a pdf. The option is still checked so it seems to not be working. Just close the stupid tools pane!
This is certainly a bug in the "New Acrobat" but I'm guessing that Adobe hasn't admitted it yet? I found a tip about reverting to the old Reader on Reddit: _pdf_in_acrobat_reader_without_tools_pane_open/
I'm skeptical, because the new version is ignoring the user's choice to "Remember current state of tools pane" and the tools pane uses up a LOT of space until it is closed/minimized. Yes, I'll be happy to file a feature request, but I still contend that it is actually a bug, because we shouldn't hav to disable the New View in order for the software to respect our "Remember current state of tools pane" choice.
I am also experiencing the same thing. I use Windows 11 and have selected the "Remember the current state of Tools pane" but it keeps coming up every time I open a new document, it wasn't like this with the previous version. My current version is 2023.003.20244 and it's just frustrating to constantly close the tools pane all the time. I don't need it! Please let us know if Adobe has made changes to this.
We are actively working on all the currently unavailable features, such as customizing the All Tools pane and retaining its current state from the Preferences. And we will address them with the highest priority.
I hope Adobe gets familiar with letting the users decide what makes them more productive. This tools pane showing is is horribly unproductive as users have to close it 99% of the time. It's just absolutely awful and backwards. "Familiarize yourself with being less productive", thanks a lot.
I would respectfully like to note to my friends at Adobe that decreasing accessibility is never an improvement. As someone who cannot use the computer quite like most people, this matters. If nothing else, please at least allow a key combination to disable the tools view that makes reading quite difficult. Using the mouse is not a pleasant activity for myself. Thank you for listening.
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