SumatraPDF Printer Not Found: How to Fix It

When SumatraPDF reports that a printer cannot be found, or a command unexpectedly prints to the wrong device, the PDF reader itself is often working normally. The failure usually comes from a mismatch between the printer name supplied to SumatraPDF and the name registered in Windows. Other likely causes include missing quotation marks, a renamed or disconnected printer, an unavailable driver, confusion between a named printer and the Windows default, or persistent settings that point to an old device.

This guide focuses on printer identity, especially when printing from Command Prompt, PowerShell, a script, or another application that launches SumatraPDF. Work through the tests in order. Once a simple document reaches the intended printer, stop changing settings and retest the original workflow.

1. Confirm the Symptom With One Simple Printing Test

Before editing commands or reinstalling software, determine whether the failure affects every print job or only a particular document, printer, or automation command. A controlled test prevents a document rendering problem from being mistaken for a missing printer.

1.1 Print a simple local PDF from the graphical interface

Open SumatraPDF normally, load a small PDF stored on the local computer, and choose the Print command. In the Windows print dialog, select the intended printer manually. Do not rely on the preselected device for this test.

A useful test file contains one page of ordinary text and no unusual fonts, forms, security controls, or large images. If that document prints correctly after you select the target printer, SumatraPDF can render and submit a basic print job. The likely problem is then the printer name, default-printer selection, or command that launches printing.

If the target printer is absent from the print dialog, focus on Windows and the printer installation. SumatraPDF cannot send a job to a printer that Windows does not currently expose to applications.

1.2 Compare the named printer with the Windows default

A named printer and the default printer are not interchangeable concepts. A command using -print-to requests a specific printer. A command using -print-to-default asks Windows for the current default printer.

Run a default-printer test with a simple local file:

SumatraPDF.exe -print-to-default "C:\Docs\print-test.pdf"

Success means the job appears in the queue for the current Windows default printer and produces the expected output. If this succeeds while a named-printer command fails, the document and basic print path are probably sound. Concentrate on the exact printer name supplied to -print-to.

If the job reaches the wrong device, inspect the current Windows default printer. Windows can manage the default printer automatically in some configurations, which may cause the most recently used device to become the default. Either select the desired default in Windows or use an exact named-printer command.

2. Check the SumatraPDF Command and Exact Printer Name

For command-line printing, the printer argument must identify a printer Windows knows by that name. Friendly shorthand, an old label, a model family, an IP address, or the physical label attached to the printer may not match the registered Windows printer name.

2.1 Copy the printer name exactly from Windows

Open the Windows printer settings or the classic Devices and Printers view. Find the target printer and copy or carefully transcribe its displayed name. Preserve spaces, punctuation, queue suffixes, server notation, and distinguishing labels such as Color, Secure, Upstairs, or Copy 2.

For example, these could represent different Windows queues even if they use the same physical machine:

• Office LaserJet
• Office LaserJet PCL 6
• Office LaserJet on PRINTSERVER
• \\PRINTSERVER\Office-LaserJet

Do not guess which form is installed. Use the name Windows presents to applications. Printer names are generally not treated as case-sensitive, but spacing, punctuation, share names, and the rest of the identity still need to be correct.

2.2 Put printer names containing spaces in quotes

A printer name with spaces must be passed as one command-line argument. Surround it with straight quotation marks:

SumatraPDF.exe -print-to "Office LaserJet PCL 6" "C:\Docs\invoice.pdf"

The document path should also be quoted when it contains spaces:

"C:\Program Files\SumatraPDF\SumatraPDF.exe" -print-to "Accounts Printer" "C:\Monthly Reports\report.pdf"

Without quotes, the shell can split the printer name or file path into several arguments. SumatraPDF may then search for a printer with an incomplete name, reject the command, or fail to open the intended file.

Success means the process submits the document to the named queue, not merely to whichever printer is currently the default. At that point, stop modifying the command and test it in the original script or application.

2.3 Check for a printer renamed in Windows

A saved command does not automatically follow a printer rename. If Warehouse Printer becomes Warehouse Printer Color, a script that still specifies the old name can produce a printer-not-found result.

Renames can also happen when a printer is removed and reinstalled, when an administrator deploys a replacement queue, or when Windows creates a second queue with a suffix such as Copy 1. Update the command, shortcut, scheduled task, or calling application with the current name.

2.4 Use the printer-not-found exit code in automation

SumatraPDF command-line printing returns an exit code that scripts can inspect. According to its command-line documentation, exit code 4 means the printer was not found. This is more specific than treating every nonzero result as a document failure.

In a batch workflow, capture the process exit code immediately after SumatraPDF finishes. In PowerShell, use Start-Process with -Wait and -PassThru, then inspect the returned process object's ExitCode. If the result is 4, verify the printer identity before changing PDF rendering options.

An exit code only reports what the process encountered. A zero result indicates that SumatraPDF accepted and submitted the print operation, but it does not guarantee that paper emerged. A later driver, spooler, network, or physical printer failure can still prevent completion.

3. Check Windows Printers, Drivers, and External Factors

If the exact command looks correct, verify that the printer is genuinely available in the same Windows environment and user account running SumatraPDF.

3.1 Check network and disconnected printers

A network printer may remain visible in Windows even when its print server, VPN, office network, or device is unreachable. Conversely, a shared printer mapped for your interactive account may not exist for a scheduled task, service account, remote session, or different user.

• Open the printer queue and look for Offline, Paused, or connection errors.
• Confirm that the computer is connected to the required local network or VPN.
• Print a Windows test page from the printer's properties.
• Run the SumatraPDF command under the same account used by the automated workflow.
• For a shared queue, verify that the print server and share are still available.

If a Windows test page cannot print, SumatraPDF troubleshooting should pause. Restore the Windows printer connection first. Success is a completed Windows test page followed by a successful SumatraPDF test to that same queue.

3.2 Confirm that a usable printer driver is installed

A visible printer entry still needs a functioning driver. Missing, damaged, incompatible, or partially installed drivers can cause print submission to fail after the printer has been identified.

Use Windows printer properties to inspect the driver and print a test page. For a managed workplace printer, obtain the approved driver through Windows Update, your organization, the print server, or the printer manufacturer. Avoid downloading drivers from unrelated third-party sites.

If the printer was recently replaced, remove obsolete duplicate queues only after confirming which queue other applications use. Reinstalling SumatraPDF will not repair a broken Windows printer driver.

3.3 Separate printer identity from document rendering

If a simple PDF prints but one source document does not, the printer has already been found. The remaining issue may involve document permissions, damaged content, complex fonts, transparency, unusually large pages, or format-specific rendering.

Try opening the affected document interactively and printing one page. Also confirm that printing is permitted when the document format supports access restrictions. Do not attempt to bypass DRM or document restrictions. Ask the document owner for a printable copy when necessary.

SumatraPDF supports several document types, but some workflows can depend on external components or format-specific behavior. Ghostscript, codecs, or conversion tools are relevant only when the source format or workflow actually uses them. They are not the first place to look when exit code 4 or an exact printer-name error is present.

3.4 Check the executable and file path used by automation

File associations determine what Windows opens when a user double-clicks a document, but an explicit command should call the intended SumatraPDF executable directly. If a script relies only on the file association, another PDF application may receive the document and apply different printer behavior.

Quote the complete executable path and confirm that it points to the expected installed or portable copy. Also verify the source file path. If SumatraPDF cannot open the document, that is a different failure category from not finding the printer.

4. Inspect or Reset SumatraPDF-settings.txt Safely

SumatraPDF stores preferences in SumatraPDF-settings.txt. Settings persistence matters when the graphical interface repeatedly remembers an unwanted printer-related state, when portable and installed copies behave differently, or when an old configuration appears to affect testing.

4.1 Find the settings file for the copy you are using

An installed copy normally keeps its settings under the user's local application-data location. Portable operation can keep settings alongside the executable, depending on how it is launched and where it can write. This means two SumatraPDF executables can use different settings even on the same computer.

First identify the exact executable used by the failing command. Then close all SumatraPDF windows before inspecting the settings file. Do not assume that changing one copy's configuration will affect another copy.

4.2 Back up before editing or resetting

Make a copy of SumatraPDF-settings.txt and give it a clear backup name. Open the original only in a plain-text editor. Avoid changing unrelated values, and do not copy random settings from an untrusted source.

For a reset test, close SumatraPDF and rename the settings file rather than deleting it. Launch SumatraPDF again so it can create a fresh configuration. Test the simple document and exact printer command.

If printing now works, the prior settings state contributed to the behavior. Reapply only the preferences you need instead of restoring the entire old file immediately. If nothing changes, close SumatraPDF and restore the backup if desired. The printer's Windows identity, connection, or driver remains the more likely cause.

5. Run a Clean Temporary Test Before Reinstalling

Reinstallation is rarely the best first response to a printer-not-found result because reinstalling does not rename a Windows printer, reconnect a network queue, or repair a command with missing quotes. A clean temporary test gives better evidence.

5.1 Test with a separate settings directory

SumatraPDF supports an -appdata command-line option that can direct it to a separate settings location. Create an empty temporary folder and launch the executable with that folder, a simple local PDF, and the printer test you want to perform.

For example:

SumatraPDF.exe -appdata "C:\Temp\SumatraTest" -print-to "Office LaserJet" "C:\Docs\print-test.pdf"

This isolates the test from the normal settings file without permanently deleting preferences. Ensure the temporary folder is writable by the account running the command.

If the clean command succeeds, compare it with the original command and settings environment. If it still returns printer-not-found behavior, verify the Windows queue name and user context again. Reinstallation is unlikely to help unless the executable itself is damaged or cannot run correctly.

5.2 Change one variable at a time

Use the same one-page PDF while testing the default printer, then the exact named printer. After the named printer works, move back to the original document. Finally, restore the original script, scheduled task, or calling program.

1. Print the simple PDF interactively to the selected printer.
2. Print it with -print-to-default.
3. Print it with -print-to and the exact quoted name.
4. Test the original document with the working command.
5. Test under the account and environment used by automation.

Stop at the first failing transition. That transition identifies the relevant layer and avoids unnecessary changes elsewhere.

6. Quick Fix Checklist

• Copy the printer name exactly as Windows displays it.
• Put printer names and file paths containing spaces in straight quotes.
• Use -print-to-default to test the current Windows default printer.
• Use -print-to "Exact Printer Name" when the destination must not vary.
• Check whether the printer was renamed, replaced, or duplicated in Windows.
• Confirm that network printers are online and available to the same user account.
• Print a Windows test page to verify the queue and driver independently.
• Treat exit code 4 as a printer identity or availability problem.
• Test a simple local PDF before troubleshooting one complex document.
• Back up SumatraPDF-settings.txt before resetting it.
• Use a temporary -appdata directory for a clean configuration test.
• Stop changing settings once the simple file reaches the correct printer.

7. Frequently Asked Questions

7.1 Why does SumatraPDF say printer not found when Windows shows the printer?

The supplied name may differ from the printer's registered Windows name, or the printer may be mapped only for another user. Copy the full displayed name, quote it if it contains spaces, and test under the same account that runs SumatraPDF. Also verify that the queue is connected rather than merely listed.

7.2 Why does SumatraPDF print to the wrong printer?

The command may be using -print-to-default, in which case Windows chooses its current default printer. Check the Windows default or switch to -print-to with the exact destination name. If a named command still reaches the wrong device, check whether multiple Windows queues point to the same physical printer or port.

7.3 What does SumatraPDF exit code 4 mean?

For command-line printing, exit code 4 means the requested printer was not found. Check the printer name, quotation marks, user context, network connection, and whether the printer was renamed. Do not begin with document rendering changes when this specific code is returned.

7.4 Do printer names with spaces require quotation marks?

Yes. Quotation marks ensure the complete name is passed as one argument. Use a command such as SumatraPDF.exe -print-to "Front Office Printer" "C:\Docs\file.pdf". Quote the executable and document paths as well when they contain spaces.

7.5 Should I reinstall SumatraPDF?

Usually not as the first fix. Reinstallation does not correct an obsolete printer name, unavailable network share, wrong default printer, or missing Windows driver. First test a simple PDF, the default-printer command, the exact named-printer command, and a clean temporary settings directory.

7.6 How do I know the problem is fixed?

The controlled one-page PDF should appear in the intended Windows queue and print successfully. A named-printer command should continue using that printer even when another device is the Windows default. Once that happens, stop changing SumatraPDF or printer settings and retest the original document and automation workflow.