Windows Application Error Referenced Memory could not be written

Report · Jul 18, 2024

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.

Report · Jul 22, 2024

This issue got fixed over a remote session with an Adobe support Tech. The fix was uninstalling Adobe Acrobat, deleting all folders/directories named "Adobe" on Local drive (Program Files, PF x86, Common Files, etc...), then finally using the "Adobe Cleanup Tool" (this step isn't too important if you deleted everything). After that, you should be able to reinstall it and the pop-up will no longer appear.

View solution in original post

Report · Sep 24, 2025

Have had this issue for months now. Scrolled through support threads dating back 12 months ago with a myriad of work arounds offered but no solutions. "We're working on it" the only update we've had.
Most of these threads are marked as SOLVED. There is no solution. Can we get the labelling changed? It might be pushing down the priority of this. In a large org these work arounds aren't viable, it's a major issue that's exited for a year now.

Report · Oct 01, 2025

Started hspping to us yesterday. Uninstalling and reinstalling is not a FIX. Adobe DC is slow and unresponsive many complaints form ALL the DC users. Never had this problem till we moved to DC. 2020 worked fine.

As much as we pay you for a Subscription this is BS.

Report · Oct 05, 2025

What version are you on currently? 25.001.20756 we pushed out recently seems to have fixed it across the org. Was previously getting the error every time a pdf was opened from within Outlook.

Report · Oct 22, 2025

not just an outlook issue. The issue persists when opening from local drive. Windows 8 compatibility saves the date. Not sure about "You lose a lot of functionality, though. You can’t create links to email pdf’s, for example - including via Word."

Report · Oct 22, 2025

The latest update (*.20756) appears to have fixed it.

Report · Oct 27, 2025

Pretty crazy that after a year this problem persists, even with newer installs.