Contents

Search

Related Articles

How to Enable Two-Factor Authentication on Gmail

Fixing WordPress Scheduled Posts with a System Cron Job

Fixing Microsoft Windows with DISM

Enabling TPM and Secure Boot for Battlefield 6

Upgrading to pfSense 2.8.0 — Fatal Trap 12 Wireless Card Error

Connect to a Wireless Network from the Windows 11 Login Screen

Using Shazam with Apple CarPlay Without Interrupting Audio

The Difference Between sudo apt-upgrade vs update

Adobe Acrobat Memory Could Not Be Read Fix

This error appears when opening a PDF file in Adobe Reader or Adobe Acrobat. It usually indicates a software issue rather than a hardware problem.

1. Update Adobe Reader or Acrobat

Outdated software often causes memory reference errors.

  • Open Adobe Reader or Acrobat.
  • Go to Help > Check for Updates.
  • Install all available updates.
    After updating, restart the program and test opening a PDF.

2. Repair the Installation

Corrupted program files are a common cause of this error. In our experience, this step resolves the issue most often. The error usually appears after a Windows Update. Updates can replace or unregister certain system libraries that Adobe Reader depends on, which breaks its connection to those components. When that happens, Reader fails when trying to load a PDF.

  • In Adobe Reader or Acrobat, go to Help > Repair Installation.
  • Allow the repair process to complete.
  • Restart your computer and try opening the file again.

This step has been effective in most cases we’ve handled.

3. Disable Protected Mode (Not Recommended)

Adobe includes a feature called Protected Mode that runs PDFs in a sandboxed environment. This isolates the program from the rest of your system, reducing the risk of malicious code inside a PDF.

Disabling Protected Mode may stop the memory error, but doing so removes this layer of security. Running Adobe Reader without Protected Mode leaves your system more vulnerable to malware embedded in PDF files. Because of this, we do not recommend disabling it except as a short test to confirm the cause of the issue. If disabling Protected Mode fixes the problem, use that information to focus on updates or compatibility fixes instead of leaving it turned off.