DPF docs

Forum|Forum|4 years ago
April 18, 2021
5 replies
1213 views

When I open a PDF file it closes on it's own within about 5 seconds. been doing this for 2 days I restarted my laptop and checked for updates. It was of no help.

This topic has been closed for replies.

R

ravinderg62643219

Adobe Employee

Hi All, Hope everyone is doing good. Thanks all for your time and patience on this and for your cooperation and sorry for the trouble you had with Acrobat. Please try the solutions shared in the following articles and let us know if you are still experiencing the issue: Acrobat DC opens for few seconds and closes after updating to April 2021 release. Acrobat automatically closes after launch/Acrobat Crash on Windows.

Regards

Ravi

A

AlgoRhythmZ

Participant

Ravi,

Thank you very much, this solution worked for us!

We had to go the extra mile though because the Creative Cloud app would not open either. Luckily, a simple "Repair" from the control panel resolved that issue. After running the updates for the CC app and making the registry key change, we had no further issues!

S

Swami-maj

Participant

Thanks Ravi,

I did the uninstall and re-install from the Adobe Creative Cloud app.

Adobe Acrobat DC no longer closes after startup.

A

AlgoRhythmZ

Participant

One of my users is also experiencing this issue, however I am not (even though we are both running 21.001.20149). A team member of mine and I have tried all sorts of things:

* Installing Windows Updates

* Uninstalling Windows updates

* Renaming folders (found this from a different thread, suggested by support apparently)

* C:\ProgramData\Adobe\SLStore

* C:\Users\USER\AppData\Local\Adobe\OOBE (the forum actually said to delete this one, i simply renamed it)

* C:\Program Files (x86)\Common Files\Adobe\SLCache

* C:\Program Files (x86)\Common Files\Adobe\Adobe PCD

* Running as admin ('works' but then the user isn't signed into their adobe account and they don't have admin priv... so this isn't a solution)

* Repairing

I'm running out of ideas. The log messages just give generic "faulting application" messages that point to ntdll.dll so I'm not sure if this is helpful or not.

I've seen a lot of forum posts about creating a dump file. I will probably try that next.

Sorry I don't have the solution, just wanted to contribute what I could!