Windows Application Error Referenced Memory could not be written

[adminu31318584]

Hello,

I am having an issue with Adobe Acrobat Standard license when opening all PDF's. When I open the PDF's, I get the error in the attached image. I have tried uninstalling and reinstalling Adobe twice, updating Windows, rolling back the version of Adobe to DC June 2024 (24.002.20857) from DC Jul 2024 (24.002.20933), SFC, DISM, checked compatibility settings on .exe of the app, turned off protection mode in Adobe. Nothing seems to pop up in event viewer or Process monitor. Mind you, clicking OK on this pop-up does not close the application and does allow the PDF to be edited normally. Any help would be much appreciated.

The error if you can't see the picture is:

Windows - Application Error

The instruction at 0x0000000071C80670 referenced memory at 0x0000000071C80670. The memory could not be written. Click on OK to terminate the program.

[JC_LA]

They must of been feeling FOMO with Crowdstrike!

[JT___]

I'm still getting the error after this install. Anyone else?

[LagunaJim1]

Yes I still have the error with 20965 as well.  It seems to be when I apply a signature graphic to a document, which was listed in their release notes I believe.  When I updated from 20895 to 20965 on first launch Acrobat made me re-import the signature and initials - so I was hopeful.

But no, still error.  I've reverted back to 20895.

[mill72118576]

Still happening to everyone here as well.  It has been two weeks!!!   If ever fixed, I am blocking all future updates until there is literally no path forward.  I don't have time to deal with this every time something gets screwed up.  In the meantime I have to hear 'Hey, It's still happening - is there a fix yet?' every time I walk past an Acrobat DC user.  Every. Single. Day.

[grafixman1]

Downloaded and installed "AcrobatDCx64Upd2400220965.msp". Still having the popup window when exiting a pdf file. I didn't unistall first. Shouldn't be necessary. Abobe...do you have a cleanup file to remove and cleanup possible issues with files?

[JC_LA]

Agree 100%, totally unacceptable. I am staying on 24.002.20759.

I pay a monthly subscription for updates I don't want that break functionality if I let them install, just terrific.

[JM-Tech]

Complete uninstall and reinstall does fix it but takes too long.

Quick workaround fixed it for me was setting acrobat to compatibility mode win7. Again... this is a workaround at best. Not a solution.

[LagunaJim1]

I have done a clean install and also installed it clean in a VM.

The issue did not resolve for me - surprised the clean VM also presented the issue.

[adminu31318584]

Which installer did you use? I used AcrobatDCUpd2300820533.msp - This was the reinstalled version that seemed to fix the issue.

[LagunaJim1]

Anything north of 20895 exhibits the issue for me.

Adobe knows about it - a problem with the "signatures" database, they discussed it the release notes for a subsequent "hotfix" I believe.

[LagunaJim1]

..they thought they fixed it / but no joy!

[JM-Tech]

24.002.2096x Optional update, July 24, 2024 — Acrobat-Acrobat Reader Release Notes (adobe.com)
Fix released July 24th it appears to resolve the issue for me and I don't need to run it in compat mode anymore.
No ideal why this is an optional update and wasn't pushed out to everyone. Probably because it's a fairly big package.

[LagunaJim1]

2096x did not solve the problem for me, as an update or on a clean install.

i use png files for signature and initials, for what it's worth...

[S. S]

Hi Guys, 

Sorry for the experience! 

We are aware of the issue and are working on a fix.

While we are at it, it would be helpful to get some logs to expedite the investigation. 

Please use this link: https://helpx.adobe.com/acrobat/kb/acrobat-diagnostics.html to collect crash logs and share the unique ID of the log.

Thanks,

Souvik

[anthonym57652342]

A truly annoying bug...The complete uninstall and this didn't resolve the problem for me.

The Win 7 compatibility workaround did.

[Abort_Retry_Fail]

even if it did work,   this is not an answer. why do we need to reinstall the software everytime there is a problem?   I manage a team of 7 users and just deploying the compatability mode was a pain in the @$$

[S. S]

@anthonym57652342 @Abort_Retry_Fail Sorry for your experience! 

While the team is already investigating this, we would like to have a session with you to understand this further and get the necessary details to expedite the fix.

If you are up for it, let me know, and I'll share a link with you over private messages to schedule a call as per your convenience.

-Souvik

[Abort_Retry_Fail]

hi Souvik,

I appreacate you reaching out but I do not have anything to offer except the error (attached)  that popped up every time they tried to edit a PDF.  The problem/memory error didnt happen to me so my own computer's logs would be no help. The rest of the team are remote and luckly I was able to send simple instructions to enable the compatiblity mode. I can tell you that they all use "Creative Cloud All Apps - Pro Edition" on a mix of Windows 10 and Windows 11 Lenovo computers. I might be able to retrive adobe logs from one of them, but that will take some time. The windows error logs were useless, nothing written there that had anything to do with it. 

If you have any other questions about their setup, I can answer on email or on here. I do not have time for a call.

[S. S]

Thanks for the response @Abort_Retry_Fail. I completely understand your point. 

-Souvik

[AcroGuest111]

I've been getting the same error, using Adobe Acrobat Standard. I downloaded the latest update (July 24, 2024), and the issue persisted.

There were some posts about this issue from over 5 years ago, and the solution offered then (updated slightly) fixed it for me. It's much easier that uninstalling / reinstalling the app:

1. Find your Adobe Acrobat program.

2. Right Click --> Properties.

3. Select Compatability tab.

4. Click on Run Compatability Troubleshooter.

5. Select Try Recommended Settings.

That's it. Hope it works for you.

[Stretchr1]

This older solution fixed the issue for me without having to go through the trouble of using the first solution suggested by Adobe. Thanks AccroGuest111

[Tiffany35781103oa61]

that worked for me! thanks!

[JamesM1775]

Thank you!!!! 

[bryan_8388]

Thanks!

Might be the first time in my life I stumbled onto a fix on my first attempt!!

[daniel_5316]

We have users still experiencing this error as of March 19th, 2025. Running the program in compatibility mode for Windows 8 has made the error go away. BTW, our users are running Windows 11 24H2 currently.

It's a shame Adobe can't seem to figure out how to fix their own products that they developed.