You double-click a PDF file in Windows and nothing happens. You try again, but Adobe Acrobat still doesn't appear.
Sometimes the problem is surprisingly simple: Adobe Acrobat is already running in the background but one or more of its processes have become stuck.
We recently encountered exactly this problem while troubleshooting a client's computer. PDF documents suddenly stopped opening when they were double-clicked in Windows. After checking Windows Task Manager, we found Acrobat-related processes still running even though there was no usable Acrobat window on the screen.
After terminating the stuck Acrobat processes and double-clicking the PDF again, Adobe Acrobat started normally and opened the document.
Before reinstalling Acrobat or making major changes to Windows, try these troubleshooting steps.
This is the simplest solution and, in many cases, may be all that is necessary.
If Acrobat has a process stuck in the background, restarting Windows terminates the existing processes and starts a clean Windows session.
After the computer restarts, try opening the PDF again.
This is why the familiar IT advice:
“Have you tried restarting the computer?”
actually works surprisingly often.
A restart isn't magic. It clears running processes, releases resources, reloads services and drivers, and gives applications a clean environment in which to start again.
If Acrobat opens normally after the restart, the problem was likely temporary.
If you don't want to restart the computer—or if the problem keeps returning—the next step is to investigate what Acrobat is doing in the background.
Press:
Ctrl + Shift + Esc
to open Windows Task Manager.
Look through the running applications and background processes for Adobe Acrobat-related processes.
The exact process names can vary depending on the Acrobat version and components installed.
If Acrobat appears to be running even though there is no usable Acrobat window open, it may be stuck in the background.
Before terminating anything, make sure you don't have an Acrobat document open with unsaved work.
Select the appropriate Acrobat process and choose:
End task
After Acrobat has completely closed, wait a few seconds and double-click the PDF file again.
If Acrobat launches and the PDF opens normally, you've probably identified the problem.
When you close an application, Windows normally terminates its processes and releases the resources associated with them.
Occasionally, an application does not shut down correctly.
Part of the program may remain running in memory even though its visible window has disappeared.
When you double-click another PDF, Windows attempts to pass the document to the Acrobat instance that it believes is already running.
But if that instance is hung or otherwise unable to respond correctly, the result can appear to the user as:
Nothing happens.
Ending the stuck process forces that instance of Acrobat to terminate.
The next time you open a PDF, Windows can start a fresh Acrobat process.
That is also why restarting the computer often fixes exactly the same problem.
This distinction is useful when troubleshooting Windows.
People often refer to any program running in the background as a "service," but processes and Windows services are not the same thing.
A process is a running instance of a program or one of its components.
A Windows service is a specific type of background component managed by the Windows Service Control Manager and usually designed to operate without a normal user interface.
Adobe software may use multiple background components, but seeing Acrobat in Task Manager does not automatically mean that a Windows service has failed.
In the situation described above, the relevant issue was a stuck Acrobat process.
That distinction becomes important when troubleshooting or creating scripts to restart applications.
If ending the background process doesn't solve the problem, try opening Acrobat itself rather than opening a PDF.
Open the Windows Start menu and launch:
Adobe Acrobat
If Acrobat opens normally, use:
File → Open
and select the PDF.
This simple test helps separate two different problems.
If Acrobat opens but a particular PDF does not, the document itself may be the problem.
If Acrobat itself refuses to open, the problem is more likely related to the application, its configuration, or Windows.
Don't troubleshoot the entire Acrobat installation based on one document.
Try opening several known-good PDF files.
There are two very different situations:
No PDF files open
and
One particular PDF file doesn't open
If other PDFs open normally, Acrobat itself may be working correctly.
The original document could be:
Damaged
Incomplete
Incorrectly downloaded
Improperly generated
or otherwise corrupted.
Try downloading the document again if it came from a website or email.
You can also test whether the same document opens in another PDF-capable application or browser.
Sometimes Acrobat isn't the actual problem.
Windows uses file associations to determine which application should open a particular type of file.
The .pdf file extension may be associated with:
Adobe Acrobat
Microsoft Edge
Google Chrome
Another PDF reader
or an application that is no longer installed correctly.
Right-click a PDF file and look for:
Open with
Then select Adobe Acrobat.
If necessary, you can change the Windows default application for .pdf files so PDFs consistently open with Acrobat.
This is particularly useful if PDFs work when opened from inside Acrobat but don't behave correctly when double-clicked in File Explorer.
Software problems can sometimes be caused by bugs that have already been corrected by the software developer.
If Acrobat opens, check for available updates.
Keeping Acrobat current is also important from a security perspective because PDF readers process files that may come from email, websites, customers, vendors, and other outside sources.
Applications that regularly process externally supplied files should receive appropriate security updates.
After updating Acrobat, restart the application and test the PDF again.
If Acrobat continues behaving incorrectly, repairing the installation may be appropriate before completely removing and reinstalling the application.
Depending on the Acrobat version installed, Adobe may provide an installation repair function.
A repair can replace or correct damaged application components while avoiding some of the disruption of a complete uninstall and reinstall.
If the repair option is available in your installed Acrobat version, try it and then restart the computer.
Test several PDF files afterward.
Uninstalling and reinstalling software is sometimes necessary.
But it shouldn't automatically be the first troubleshooting step.
If the actual problem is simply a hung background process, reinstalling the entire application is unnecessary.
A good troubleshooting sequence moves from the simplest and least disruptive possibilities toward more invasive solutions.
For this problem, that generally means:
Restart Windows
Check Task Manager
Restart Acrobat
Test another PDF
Check the PDF file association
Update Acrobat
Repair Acrobat
and only then consider:
Reinstall Acrobat
This approach can save considerable time.
A one-time application freeze isn't necessarily a major problem.
If Acrobat repeatedly becomes unresponsive or remains stuck in the background, however, there may be another underlying issue worth investigating.
Possible areas to examine include:
Outdated Acrobat software
Windows updates
Damaged Acrobat components
Problematic plug-ins
User-profile issues
Low system resources
Storage problems
Security software conflicts
Damaged PDF files
Other software conflicts
Repeatedly terminating Acrobat may restore operation, but it doesn't necessarily identify why the application keeps failing.
If the problem becomes frequent, the underlying cause should be investigated rather than continually treating the symptom.
Yes, Windows provides command-line tools that can terminate running processes, and this can be automated with a batch file.
For example, Windows administrators can use tools such as tasklist to identify running processes and taskkill to terminate a specific application process.
This can be useful when a known application repeatedly becomes stuck.
However, there is an important caution.
Do not simply terminate every process containing the word “Adobe.”
Adobe applications may have multiple components running, and a computer may also be running other Adobe software.
Indiscriminately terminating processes could close another application or interrupt work that the user wanted to keep open.
The correct approach is to first identify the specific process responsible for the problem and then target only that process.
For an occasional Acrobat problem, using Task Manager or simply restarting Windows is usually easier and safer for most users.
For an IT administrator dealing with the same repeatable problem across systems, a carefully designed script can make sense.
Application problems are also a good example of why a slow or malfunctioning computer doesn't automatically need replacement.
A computer can appear to have a serious problem when the actual cause is:
A stuck application
A failed background process
A software update problem
A damaged application installation
Insufficient memory
A failing storage device
An operating-system configuration problem
Replacing the computer might make the symptom disappear, but that doesn't mean replacement was necessary.
Good troubleshooting starts by identifying the cause.
If Adobe Acrobat won't open your PDF files, try these steps in order:
Restart the computer.
Try opening the PDF again.
Open Task Manager and check for stuck Acrobat processes.
End the stuck Acrobat task and try again.
Open Acrobat directly from the Start menu.
Try several different PDF files.
Check the Windows default application for .pdf files.
Update Adobe Acrobat.
Repair the Acrobat installation if the option is available.
Reinstall Acrobat if the simpler troubleshooting steps don't resolve the problem.
If Acrobat repeatedly becomes stuck, investigate the underlying cause rather than relying on repeated restarts.
Not every computer problem requires complicated troubleshooting.
In the client situation that prompted this article, Adobe Acrobat had background processes that remained running and prevented PDFs from opening normally.
Terminating those stuck processes allowed Acrobat to start again and immediately solved the problem.
Restarting the computer would likely have accomplished the same thing because Windows would have terminated the existing Acrobat processes during the restart.
Understanding why the solution works is more useful than simply memorizing the fix.
Wireknots provides computer troubleshooting, software support, Windows support, computer repair, maintenance, and upgrades for businesses throughout Chicago and the surrounding area.
If your business computers are experiencing recurring software problems, slow performance, crashes, update problems, or other technical issues, we can diagnose the underlying cause and determine the most practical solution.
Computer Support, Repair & Upgrades →