SumatraPDF Crashes Opening a PDF: How to Fix It

When SumatraPDF crashes opening a PDF, the window may close instantly, hang without displaying the first page, or disappear after briefly showing the document. The most likely causes fall into a few categories: one damaged or unusually constructed PDF, a problem with SumatraPDF's saved settings, an outdated application build, interference from Windows or an external tool, or a damaged installation. The key is to separate a document-specific failure from a broken SumatraPDF setup before reinstalling anything.

Work through the tests below in order. After each change, reopen the same document and note the result. If the file opens normally, stop changing settings. Making additional changes after the problem is solved can hide the original cause and make future troubleshooting harder.

1. Confirm the Symptom With a Simple Document Test

The fastest diagnostic step is to open another known-good PDF. Choose a small, ordinary PDF from a trusted source, preferably one that previously opened successfully. Do not begin with another file downloaded from the same website or generated by the same scanner, reporting system, or document application because it may contain the same structural problem.

1.1 Test another PDF directly

1. Close every SumatraPDF window.
2. Save a simple test PDF to a local folder such as Documents.
3. Open SumatraPDF from the Start menu or its executable file.
4. Use the application's Open command to select the test PDF.
5. Wait long enough to confirm that the first page renders and scrolling works.

If the test document opens normally, the SumatraPDF installation is probably functional. The original PDF may be incomplete, corrupt, malformed, unusually complex, encrypted, or dependent on a feature that does not render correctly. At this point, stop changing global settings and focus on the source document.

If every PDF causes SumatraPDF to crash or disappear, continue with the application, settings, and Windows checks below. A repeatable crash involving multiple unrelated PDFs points more strongly to the program environment than to one bad file.

1.2 Copy the failing file to a local folder

A file opened from a browser download area, email attachment, network share, cloud placeholder, removable drive, or temporary folder may not be fully available. Copy the PDF to a short local path, such as C:\Temp\test.pdf, and open that copy from inside SumatraPDF.

Success means the local copy opens and remains responsive. If so, the issue is likely associated with the original location, synchronization state, permissions, or the application launching the attachment. Keep using the local copy or download the file completely before opening it.

1.3 Distinguish a crash from a slow render

A complex PDF containing large images, transparency, unusual fonts, or many vector objects can take time to render. Open Task Manager and observe SumatraPDF briefly. If the process remains present and CPU or disk activity continues, the program may be busy rather than terminated. Avoid repeatedly double-clicking the file because that can start additional work.

If the process vanishes, Windows reports that the application stopped working, or the same action closes the window consistently, treat it as a crash. Record the exact action that triggers it, such as opening the file, moving to a particular page, searching, printing, or displaying a thumbnail.

2. Check the SumatraPDF Setting, Command, Association, or Format

Once you know whether the failure affects one file or many, check how SumatraPDF is being started. A crash that occurs only after double-clicking a file can have a different cause from a crash that occurs when the same file is opened through SumatraPDF's Open command.

2.1 Compare double-clicking with opening from the application

1. Start SumatraPDF without selecting a document.
2. Use the Open command and browse to the PDF.
3. If that works, close the document.
4. Double-click the same PDF in File Explorer.

If opening from inside the application works but double-clicking fails, repair the Windows file association. Open Windows Settings, locate default apps by file type, and assign the .pdf extension to the correct SumatraPDF executable. This matters particularly if both portable and installed copies have been used because Windows may still point to an old or deleted executable.

Success means both opening methods launch the same current SumatraPDF copy and display the document. Once they do, do not reset unrelated rendering preferences.

2.2 Remove shortcuts and custom commands from the test

If SumatraPDF is normally launched through a custom shortcut, script, file manager, command line, browser integration, or third-party launcher, test the executable directly. A shortcut can contain an outdated path, command-line options, or a document path that no longer exists.

Create a clean test by opening SumatraPDF.exe directly and then selecting the document through the Open dialog. If this succeeds, inspect the shortcut or launching tool rather than reinstalling SumatraPDF. Recreate the shortcut without optional arguments and add necessary options back one at a time.

2.3 Confirm the document's real format

SumatraPDF supports more than PDFs, including several eBook, comic, help, image, and document formats. However, changing a filename extension does not convert a file. A document named report.pdf may actually be an HTML error page, an incomplete download, or another file type delivered with the wrong name.

Check the file size and download it again from its legitimate source. If the source provides a checksum, compare it. You can also ask the sender to export a fresh PDF using the originating application. Do not attempt to remove DRM or bypass document restrictions. Protected content should be opened through an authorized application and account.

2.4 Update to the latest stable build

Download the current stable SumatraPDF release from the official website. Match the architecture appropriate for your Windows installation and choose either the installer or portable package intentionally. Avoid unofficial download sites and modified packages.

Before updating, close SumatraPDF and preserve any settings you need. After installing or extracting the new build, test a known-good PDF first and then the failing file. Success means the stable build opens both documents without closing or hanging. If only the original file still fails, return your attention to that document rather than repeatedly reinstalling the reader.

3. Check Windows, the Source Document, and External Factors

SumatraPDF may be the visible application when the crash occurs, but another component can trigger the failure. File permissions, security software, printer drivers, browser integrations, and external conversion tools are relevant when the symptom appears only in a particular workflow.

3.1 Check document access and permissions

Right-click the file, open Properties, and confirm that your Windows account can read it. If Windows shows an Unblock option for a trusted downloaded file, evaluate the source before using it. Do not unblock files from unknown or suspicious sources.

Try copying the file to a folder owned by your account. A successful local test suggests that access controls, network availability, cloud synchronization, or security scanning affected the original path. There is no reason to alter SumatraPDF settings if changing the location solves the problem.

3.2 Treat one failing PDF as a source-document problem

A corrupt or malformed PDF may contain a damaged cross-reference table, incomplete objects, broken embedded fonts, invalid images, or content streams that expose a rendering bug. Download the document again and compare its size with the original. If it arrived by email, ask the sender to attach it again or export a new copy.

If another reputable PDF viewer can open the file, that does not necessarily prove the file is valid. Viewers differ in how they recover from malformed structures. If permitted, use the originating application to create a new standards-compliant PDF. Avoid uploading confidential documents to random online repair services.

3.3 Test printing separately from opening

If the document opens but SumatraPDF crashes when you select Print, preview pages, or choose a particular printer, the printer driver may be involved. Test with a different installed printer or a built-in Windows print destination. Update the physical printer's driver from the manufacturer if the crash is limited to that device.

Success means the PDF remains open and the print dialog or alternate printer works. That result narrows the issue to printing rather than PDF loading. Do not delete SumatraPDF settings merely because one printer driver fails.

3.4 Consider Ghostscript, codecs, and external viewers only when relevant

Ordinary PDF viewing should not lead you to install random codec packs. Codecs, Ghostscript, shell extensions, or external converters matter only when your workflow explicitly invokes them, such as through a script, conversion process, preview handler, unusual PostScript workflow, or third-party file manager.

Temporarily bypass the external tool and open the source file directly in SumatraPDF. If direct opening succeeds, update or reconfigure the external component. Also check whether a browser extension or another viewer intercepts the file before SumatraPDF receives it. Disable only the integration involved in the failing path, not unrelated Windows services.

4. Inspect or Reset SumatraPDF-settings.txt Safely

SumatraPDF stores preferences and session-related information in a settings file named SumatraPDF-settings.txt. Depending on whether you use an installed or portable copy, the file may be stored with application data or near the portable executable. Settings persistence can explain why replacing the program executable does not change the behavior.

4.1 Back up the settings file first

1. Close all SumatraPDF windows and confirm the process has ended in Task Manager.
2. Locate SumatraPDF-settings.txt for the copy you are actually running.
3. Copy it to a safe location and give the backup a recognizable name.
4. Do not edit the only copy while SumatraPDF is running.

The backup preserves preferences and gives you a way to undo the reset. It may also help isolate which setting caused the problem if a clean file fixes it.

4.2 Reset settings without permanently deleting them

Rename the active settings file, for example to SumatraPDF-settings-backup.txt. Start SumatraPDF again so it can create a fresh default configuration. Open a known-good PDF, followed by the problematic document.

If both files now work, the previous configuration was probably involved. Keep the backup, but do not immediately restore the entire old file because that may restore the fault. Reapply only the preferences you need through the application, testing after meaningful changes.

If the crash remains unchanged, close SumatraPDF and restore the backup if desired. A failed settings reset is useful evidence because it tells you to investigate the document, build, Windows environment, or external launch path instead.

4.3 Avoid editing unfamiliar settings blindly

Manual settings edits can create syntax errors or values that are inappropriate for the current build. If you previously copied settings from another computer or an older installation, test with defaults before attempting line-by-line changes. Keep notes about edits so each one can be reversed.

Success after removing one known customization identifies a practical fix. Stop there. There is no benefit in changing additional display, history, tab, or rendering preferences after stable operation returns.

5. Run a Clean Temporary Test Before Reinstalling

A clean portable test is one of the best ways to distinguish the installed environment from the document itself. It does not require you to uninstall the existing copy or erase preferences.

5.1 Create an isolated portable test

1. Download the latest stable portable package from the official SumatraPDF website.
2. Extract it into a new empty folder that is writable by your Windows account.
3. Do not copy old settings, shortcuts, plugins, or launch scripts into that folder.
4. Run the portable executable directly.
5. Open a simple PDF and then the problematic PDF through the Open command.

If the portable copy opens both files, the installed copy, its settings, its shortcut, or its Windows association is likely responsible. You can then update or reinstall the installed edition without guessing that the document is bad.

If the clean portable copy opens ordinary PDFs but crashes on the same single document, the file or a format-specific rendering defect is the stronger suspect. If even unrelated documents crash in both clean portable and installed copies, investigate Windows security events, display or printer drivers when applicable, and any reproducible system-level interference.

5.2 Reinstall only after the isolated test

Reinstalling is appropriate when the portable copy works but the installed application does not, especially if the installed executable may be damaged or outdated. Uninstall the installed edition through Windows, restart if Windows requires it, and install the current stable release from the official source.

Do not delete your backed-up settings until the new installation has been tested. First run it with defaults. Success means a known-good PDF and the original PDF open consistently through both the application's Open command and File Explorer.

6. Quick Fix Checklist

• Open a different, known-good PDF to separate a bad document from a broken reader.
• Copy the failing file to a local folder and confirm it downloaded completely.
• Open the file from inside SumatraPDF instead of double-clicking it.
• Repair the Windows .pdf association if it targets an old portable or installed copy.
• Update to the latest stable build from the official SumatraPDF website.
• Test a clean portable copy without importing old settings.
• Back up SumatraPDF-settings.txt before renaming or resetting it.
• Bypass custom shortcuts, scripts, browser integrations, and external viewers temporarily.
• Test another printer if the crash happens only during printing.
• Stop changing settings as soon as normal opening and navigation work reliably.

7. Frequently Asked Questions

7.1 Why does SumatraPDF crash on only one PDF?

The file may be incomplete, malformed, corrupt, unusually complex, or created with features that trigger a document-specific rendering problem. Download it again, test a local copy, and ask the sender to export a fresh PDF. If other unrelated PDFs open normally, avoid resetting the entire application unless additional evidence points to its settings.

7.2 Should I reinstall SumatraPDF immediately?

No. First test another PDF and run a clean portable copy. Reinstallation is most useful when the portable edition works but the installed edition fails. If only one file crashes in both editions, reinstalling is unlikely to repair that document.

7.3 Can installed and portable copies conflict?

They can cause confusion if Windows associations, shortcuts, or settings point to a different copy than the one you expect. Verify the executable path in use. Keep the portable test in a separate folder and launch it directly so the result is unambiguous.

7.4 Will resetting SumatraPDF-settings.txt delete my PDFs?

No. The settings file is separate from your documents, but resetting it can remove preferences, history, or session-related configuration. Back it up and rename it rather than deleting it permanently. Restore the backup if the reset does not affect the crash.

7.5 What if SumatraPDF opens the PDF but crashes when printing?

Treat that as a printing problem rather than an opening problem. Test another printer, update the relevant printer driver, and confirm whether a built-in Windows print destination works. A crash limited to one printer strongly suggests a driver or device-specific path.

7.6 When should I submit a crash report?

Submit a report when the crash is reproducible in the latest stable build, especially if it also occurs in a clean portable test. Include your Windows edition and architecture, the SumatraPDF build, whether the copy is installed or portable, the exact steps, and whether other PDFs work. If the document is non-confidential and you have permission to share it, attach or link the problematic file because a reproducible sample is often the most useful evidence. Never share private, licensed, restricted, or sensitive material publicly. If the file cannot be shared, describe its source, approximate size, triggering page, and the smallest repeatable sequence instead.