After MS Windows update KB5005565 Adobe Reader isn't starting up. You can see the process in task manager but the window never open. Using version 21.007.20091.
Repair fix the problem until next reboot then the issue is back. Any solution to this?
Hope you are doing well and sorry for the trouble. As described the Acrobat Reader DC version 21.07.20091 is not opening after the you have updated the Windows OS.
Also, repairing the installation fixes the issue until the next reboot is done.
Please try to create a new test user profile with full admin rights in Windows with full admin rights and try using the application there.
If it still doesn't work, please remove the application using the Acrobat cleaner tool - https://www.adobe.com/devnet-docs/acrobatetk/tools/Labs/cleaner.html reboot the computer once and reinstall the application using the link https://get.adobe.com/reader/enterprise/ and check if that works.
Let us know if you experience any trouble and need more help.
The test admin user has the same problem.
Acrobat cleaner tool did not solve the problem.
Only way to solve it is to uninstall KB5005565 but that's not an option. We have the same problem for 100+ computers.
Removing the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\AcroRd32.exe solves the problem until restart.
Any other solutions?
The cleaner tool didn't work for me. Searching around, found an older discussion, the following instructions did work.
My original issue was Acrobat Reader DC (64-bit) would come up with the first page of the PDF document displayed, but any attempt to do anything with the file (scroll, print, whatever) caused the application to gray out and show busy (forever). All I could do was click on the X to close. Restart for Windows 10, uninstall Reader and reinstall, etc. did nothing to fix the issue.
When I got to the preferences, only one version folder was a September date -- and it was called Preflight Acrobat Continuous. Strange name for a version. That is the one I moved out of the directory per the instructions. Brought Acrobat Reader up again and all is good to go. Checking back after restarting Acrobat Reader, a new version folder with the strange name is back, created with today's date.
We have the same issues in our companies!
We need a quick solution to this issue.
We have exactly the same issue - Please can you provide a fix for this asap as it's a creeping issue.
A temp fix that we have shared with our users is to open appwiz.cpl, select Adobe Reader, select "Change" and then run the repair option. This does not require Admin permissions
Please noe this is only a temp fix that will need to be repeated when the issues resurfaces after a device restart.
A Windows Quality Update (Security Update For Microsoft Windows (KB5005565) causes the problem with Adobe reader and Excel. This updating came yesterday. You can roll back this update, and it will solve your problem.
You can test with some PCes first before rulling back.
Hope everyone is doing well and am sorry for the trouble you had with Acrobat Reader.
Would it be possible to share the Process Monitor logs from the affected machine using the Log tool: https://www.adobe.com/devnet-docs/acrobatetk/tools/Labs/acromonitor.html
Download the tool, run it, reproduce the issue, and save the logs. Share the logs with us either by uploading them to the Document Cloud Storage: https://documentcloud.adobe.com/link/home/ and share the link with us. Or attach it to the thread.
So that we can go ahead and investigate the root cause and can get it eliminated as soon as possible.
Thank you for your cooperation and your patience.
Wouldn't it be a good idea for you to recreate the issue yourselves and work with Microsoft to resolve. Quite straight forward - Windows10 20H2 with KB5005565 and Adobe Reader.
Please let us know once either Micrsoft or yourselves are able to provide a fix.
Have same issue.
As someone says below, is related to KB5005565 and default Exploite Protections for Adobe Reader.
Found that update to Adobe Reader version 21.007.20091 that has just come out, fixed for us.
Hope it helps.
21.007.20091 version does not solve it for us. Same problem when you reboot the computer.
We made a quick fix that deletes the registry value below every time a user logon. Works for now until this is solved properly.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\AcroRd32.exe
This info was really good to find to get us isolate the issue!
We have the exact same problem here. Adobe Reader opens fine until you open a PDF. So, clicking directly on a PDF or opening a PDF from inside the app.
In my case Windows Defender Exploit Protection was the issue. Now it's working again with the latest baseline: Windows-Defender-Exploit-Guard-Configuration/Windows10-v2104_ExploitGuard-Security-Baseline.xml at m...
We applied this baseline via Intune and the issue seems to be gone. Thanks so much!
This worked for us aswell. Thanks!
Wow, did anyone actually look at this "baseline" This actually turns off all the EP features. everything is set to False.
Is that really the solution to turn off Exploitguard for these products?
It's a mistake that people think it's a Baseline because it's included in the 21H1 Security Baseline from Microsoft. If you read the notes from Microsoft though, and even the name of the file (EPReset.xml) this is designed to reset Exploit Protection and remove it from the Baseline as it was causing issues. It is not Microsoft saying that EP should be turned off, just they're not providing the xml as part of the Baseline anymore.
I found (pretty sure you already did too) that the setting causing the issue is:
Yep. I wonder how many people have just disabled their security without reading what they are actually doing. I've contacted our TAM and I'm still waiting for an "Offical" EP Baseline,
We are unable to reproduce the issue at our end. We would need your help in understanding and reproducing the issue.
Could you share us the following information:
An Outdated Exploit Protection Baseline was in place. Somehow the issue occured after the MS Patch KB5005565 was applied.
<DEP Enable="true" EmulateAtlThunks="false" />
<ASLR ForceRelocateImages="true" RequireInfo="false" BottomUp="true" HighEntropy="false" />
<Payload EnableExportAddressFilter="true" EnableExportAddressFilterPlus="true" EnableImportAddressFilter="true" EnableRopStackPivot="true" EnableRopCallerCheck="true" EnableRopSimExec="true" />
Replaced it with:
<DEP OverrideDEP="false" />
<ASLR ForceRelocateImages="true" />
<Payload OverrideEnableExportAddressFilter="false" OverrideEnableExportAddressFilterPlus="false" OverrideEnableImportAddressFilter="false" OverrideEnableRopStackPivot="false" OverrideEnableRopCallerCheck="false" OverrideEnableRopSimExec="false" />
This is happening to our company as well....several hundred machines impacted. @AnandSri please work with your team and see what can be done to help all of our companies out. We are all experiencing the same thing
I am sorry for the trouble you had. We're working to isolate the issue at our end.
Would you mind sharing the following details so that it can help us in expediting the investigation:
Thanks for your patience and for your cooperation on this.
This is happening to our company too. More than 3k of devices with the issue.