Adobe Reader quit unexpectedly

[eddie_77]

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.

Help! 

<title altered for clarity-kglad>

[kglad]

@WinklerCanvas 

contact your admin.

[WinklerCanvas]

My ticket is about a buggy Adobe Acrobat Reader September 2023 update.
My problem (Quick Print from Outlook 2016 stopped working) is related to the topic - Adobe Reader quit unexpectedly because Outlook tried to open the default PDF application to make Quick Print.

It WORKS BEFORE SEPTEMBER 2023 ACROBAT READER UPDATES!

[kglad]

@WinklerCanvas 

ok.

[Michael33546353txom]

Hi I contacted my admin and he said uninstall Adobe reader and use a different product

[kglad]

@Michael33546353txom 

ok.

[acroferbat]

This is outrageous. This is affecting many users, the problem has been reproduced several times by many. I have this problem myself on my desktop (Win 10 64bits), on my laptop (Win 11 64bits), in all cases with all software updates. It doesn't matter if there is an antivirus (Avast) or not, it doesn't matter if there are other pieces of software installed. It seems to be a problem exclusive to Acrobat. Please fix it!

[Jennifer246297531jaf]

I second that! Anyone at Adobe watching/listening?

[kglad]

I second that! Anyone at Adobe watching/listening?

By @Jennifer246297531jaf

no.  these are user-to-user forums.  and this thread is confounded by posts from people with different problems, different causes and even users with acrobat, not reader.

[Jennifer246297531jaf]

You gotta think some community manager at Adobe follows these to some degree. This is an Adobe site after all. 

[kglad]

@Jennifer246297531jaf 

that would be in the realm of "you never know". ie, anything's possible.

[FuzzyJohn]

I did the bDisableSuggestWorkaroundsAtLaunch Registry Edit (which I mentioned here a few times) about 10 days ago  and I haven't seen this error since. I have nothing disabled in my Adobe Acrobat Reader DC.

When Adobe releases an update I turn off the bDisableSuggestWorkaroundsAtLaunch Registry value and check. If the problem is fixed, great. If not, I turn it back on and go about my business until the next update.

Keeps my sanity clean.

[Barren Mind]

It's worked for me too. Made the edit a couple of days ago and everything's been fine. It was driving me crazy -- thanks for posting the solution/workaround.

[Cstew2019]

Menu > Preferences > Security (Enhanced), disable "Enable Protected Mode at startup" seems to have fixed it for me. NO issues for week or so. ... (but didn't seem to solve it for a co-worker)

[matuko]

Thanks.. I've tried it! Fingers crossed.

[matuko]

It seems to be working for me, as well.

[Zach3358572827gx]

That's great... but if you can't even get the product to actually run.... you can't get into the settings!

[FuzzyJohn]

That's great... but if you can't even get the product to actually run.... you can't get into the settings!

By @Zach3358572827gx

In that case I guess you have a bigger problem than the one this thread is for.

[FuzzyJohn]

New update released today (v2023.006.20380). Let's see if our problem is fixed.  

[FuzzyJohn]

New update released today (v2023.006.20380). Let's see if our problem is fixed.  

By @FuzzyJohn

That didn't last long: got 8 errors in 5 minutes.

Turning bDisableSuggestWorkaroundsAtLaunch back ON.

[G_Man]

Jeeeeezzzzzzzzzzzz

[eddie_77]

new update but i still get the fail error

[slipd]

Wow, I'm not the only one with this issue... that's reassuring, but also really disappointing at the same time.

Windows 11, latest updates etc. Think it could be related to the thumbnail preview thing, which I do need enabled.

Come on Adobe, how hard can it be? 

[slipd]

Subscribed Creative Suite, Acrobat Pro user. All apps are working fine apart from this error. 

[kglad]

@slipd 

you shouldn't be using adobe reader if you have acrobat pro which does what reader does, plus much much more.

[slipd]

Yep, sorry - Pro user but same issue. I'm guessing it's related.