Fix Acrobat “A running instance has caused an error”
What to do first
Troubleshoot Acrobat “A running instance has caused an error” by following the official decision path while preserving user data.
This is a general troubleshooting guide, not an announcement of a current outage.
Affected products and symptoms
- Product
- Adobe Acrobat
- Versions and conditions
- Acrobat on Windows
- Error codes and identifiers
- A running instance of Acrobat has caused an error
Symptoms
- Opening a PDF shows a running-instance error
- It recurs after Acrobat is closed
Causes and conditions
Check stale processes, updates, and damaged installation in order.
Before you start
- Before changes, record and preserve unsaved PDF edits and names of open files.
- Change one item at a time and record the original symptom after each stage.
Precautions
- Do not bulk-delete unrelated settings or data.
- Exclude personal data and credentials; share only the necessary parts of unsaved PDF edits and names of open files.
Step-by-step instructions
Close Acrobat and open Task Manager with Ctrl+Shift+Esc.
End Adobe Acrobat under Apps and Background Processes.
Also check the Details tab for Acrobat.exe; this distinguishes closing the window from ending the process.
Start one Acrobat instance and open a local PDF.
Avoid repeated clicks and duplicate launches.
After updating, record the version under Help > About Acrobat. Recurrence on the same build is useful evidence.
Use Menu > Help > Check for updates.
Restart Windows after completion.
Repair re-registers program components; it does not delete the PDF itself or its Document Cloud original.
Use Menu > Help > Repair Installation.
Do not edit the registry from the official advanced procedure without backup and administrator review.
Adobe also documents a DDE registry value, but a wrong edit affects launch behavior. Only an administrator should use that advanced path after backup.
Check the result
- start one Acrobat instance and open one local PDF both from Acrobat and File Explorer
- Check adjacent basic functions for side effects from the change.
If the problem continues
- give Adobe Support the Acrobat logs and Windows events from the same time
- When continuing with a workaround, preserve original files or account data separately.
Scope of this guide
Troubleshooting guide — Troubleshoot Acrobat “A running instance has caused an error” by following the official decision path while preserving user data.
Frequently asked questions
Can force-ending lose data?
Unsaved PDF edits can be lost, so save first when possible.
Is registry editing required?
Try process cleanup, update, and repair first.
Official sources and dates
Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.
Related troubleshooting guides
- Fix Firefox “already running” or profile-in-use errors
- Identify the source of Chrome “Managed by your organization”
- Fix OneDrive “Can’t open file” or “Make sure OneDrive is running”
- Fix OneDrive error 0x8007016a
- Fix “Cannot start Microsoft Outlook” with resetnavpane
- Separate PDF damage from Acrobat installation damage