Re: Acrobat Reader Free
Elpidio Heart
I kept getting this problem with my Adobe Acrobat reader. I tried to repair and even reinstall but it keeps coming up. Not sure if it has anything to do with recent Windows updates. I am using Windows 10 64bit.
I followed the steps to enable CrashDumps. After that in Adobe Reader Preferences I turned on "Enable PDF thumbnail previews in Windows Explorer". When I clicked OK I immediately got the small error window. Checking in Windows Explorer I could not find the CrashDumps folder.
As I previously mentioned, for me the Crash Dumps are not generated. I also posted screenshots of the Registry to prove that I did everything correctly. I did get files in the CrashDumps folder after running the Cleanup Tool, but nothing when the error we are talking about here is shown. Maybe it is not a real error that brings up that message??? Maybe just a bug?
Hi @FuzzyJohn I got the same behaviour as you.
I've also create the Registry Keys as requested.
But even with many popup "Acrobat quit unexpectedly" there is no single file related to Acrobat in the Dump folder
Yes I am getting the same error recently on a pretty much brand new install of Windows 11 too. I think its related the thumbnails, as only get error when Enable PDF thumbnails previews is enabled. I have tried fresh reinstall, remove completly using cleaner, and manually removing all traces before reinstalling, but still get dozens if not hundreds of errors per day. I have also tried clearing all thumbnails with Windows, no change. I have also tried installing Reader first, then Acrobat (pro) but always get the error when Thumbnails are enabled.
Your diagnosis is correct. You have to uncheck "Enable PDF thumbnails in Windows Explorer" in order to stop getting the error. This problem arose only recently (Since September 2023). Adobe needs to fix this. The thumbnail feature is useful, and paying subscribers should not be deprived of this feature.
I get this same message even when my Enable PDF... is unchecked. And I only get the error when opening a doc from the server. Also, weirdly, the doc then opens just fine ?? But it's extremely annoying to have to click Skip every time.
If I open a doc from inside Adobe, I do not get the message. Another weird thing...
If you feel at ease editing the Windows Registry, in Regedit go to HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\DC\AVGeneral\CrashDataAtLaunch and create a new DWORD (32-bit) Value named bDisableSuggestWorkaroundsAtLaunch then set it to 1. Once you click OK the error messages should disappear until you delete this value or set it to 0 (zero).
Alternately you can use the bDisableSuggestWorkaroundsAtLaunch.txt file I attached here, change the extension from .txt to .reg and double-click the file. Allow this app (Registry Editor) to make changes to your device, and the bDisableSuggestWorkaroundsAtLaunch value will be created and it will be set to 1.
Hi Fuzzy,
Thank you kindly for the workaround. This has worked for me too.
I am sure I am correct in saying that I speak for all when I say.
Eventhough this IS NOT a fix, it is a work around we all require because Adobe is too... well, you know the word I want to use here, to fix the issue itself, that clearly MANY are experiencing!!!
Everyone is clearly pointing out that no logs is being created for this hogwash issue.
Anyway, I am still appreciative of the fix/ workaround provided.
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
Prior to downloading the latest Adobe Acrobat, please make sure that your labels are visible in the Security and Compliance center UI @ . If the labels are visible and are published by a label policy from the Security and Compliance center, the Adobe Integration will function.
After you have validated the label being visible in the Security and Compliance center, please proceed to download your Adobe Acrobat Reader from the Adobe site. Once you have installed the Reader then please proceed to the link and download the integration plug-in for installation. Please make sure that you close the Adobe Acrobat solution prior to installing the plug-in, otherwise it will not work.
d3342ee215