sumatrapdf-tool.exe Not Found: How to Fix It

If Windows reports that sumatrapdf-tool.exe is not found or is not recognized as a command, the problem usually occurs before SumatraPDF processes your document. The executable may be absent from your SumatraPDF package, stored in a different folder, blocked or removed by security software, or present but unavailable through the current command prompt and PATH. Another common cause is confusing the newer command-line tool with the standard SumatraPDF.exe viewer, which supports a different set of command-line flags.

Start by confirming that the tool file actually exists. Do not change document settings, reinstall printer drivers, or troubleshoot command syntax until you have completed that check. Once a command displays its help text or begins processing a simple local document, stop changing settings and focus only on any document-specific error that remains.

1. Confirm the Symptom With One Simple Test

Open File Explorer and locate the folder containing SumatraPDF.exe. In a package that includes the newer command-line tool, sumatrapdf-tool.exe should normally be installed or extracted next to the viewer executable. Search this specific folder first rather than searching only the Start menu.

1.1 Check Whether the Tool Exists

Look for both executable filenames in the same directory:

• SumatraPDF.exe, the normal graphical document viewer
• sumatrapdf-tool.exe, the separate command-line tool

If Windows hides filename extensions, enable View > Show > File name extensions in File Explorer. This prevents a similarly named shortcut, text file, or incomplete download from being mistaken for the executable.

If sumatrapdf-tool.exe is absent, command syntax is not yet the issue. The successful outcome of this check is seeing the real executable in the folder. If it is missing, proceed to the package and installation checks below.

1.2 Launch the File by Its Full Path

Open Command Prompt and run the tool using its complete quoted path. For example:

"C:\Program Files\SumatraPDF\sumatrapdf-tool.exe"

Your actual installation path may be different. Quotation marks are necessary when the path contains spaces. You can avoid typing mistakes by holding Shift, right-clicking the executable in File Explorer, and using the available copy-path option.

If the command prints help, usage information, or a message indicating that a subcommand is required, Windows has found and launched the executable. That is a successful test. Stop troubleshooting PATH and installation location at that point. You can then check the syntax for the particular grep, convert, extract, or merge operation you intend to use.

If Windows says the path does not exist, verify the folder and filename. If Windows displays a security or access error instead, investigate file permissions and security software before testing document arguments.

2. Check the Package, Command, and Executable Directly

The presence of the normal SumatraPDF viewer does not prove that sumatrapdf-tool.exe is installed. SumatraPDF distributions and development builds can differ, and a stable build may not contain the same files or experimental command capabilities as a pre-release build. Do not assume that every installed or portable package includes the newer tool.

2.1 Verify That Your Download Includes the Tool

Check the official SumatraPDF download options and release information for the package you obtained. Compare the files in the downloaded installer or archive with the files in your current SumatraPDF directory. If the official package you selected does not include sumatrapdf-tool.exe, repeatedly reinstalling that same package will not create it.

Use a package that explicitly includes the tool you need. When comparing stable and pre-release downloads, treat them as separate packages rather than assuming their contents are identical. Pre-release software can contain newer functionality, but it can also change and may be less thoroughly tested. Back up important files and test commands on copies of documents.

Success means that the downloaded or installed directory contains both executables and the tool launches by full path. Once that happens, stop switching packages unless a specific command is documented as unavailable in your build.

2.2 Distinguish the Tool From Viewer Flags

SumatraPDF.exe and sumatrapdf-tool.exe are not interchangeable names for one program. The viewer executable supports documented options for viewer-related tasks such as opening a page, controlling presentation behavior, or printing. The separate tool is intended for its own documented command operations.

If your goal is simply to open or print a document, check whether a supported SumatraPDF.exe flag already handles the task. Do not rename SumatraPDF.exe to sumatrapdf-tool.exe. Renaming a file does not add the tool's commands and can break shortcuts or associations.

If your intended operation is grep, convert, extract, or merge, first confirm that the command is supported by the exact tool build you downloaded. A command copied from a development discussion, an older example, or another PDF utility may not match the installed executable.

2.3 Run From the Correct Directory

Command Prompt does not automatically search every folder on the computer. You can change to the SumatraPDF folder before running the tool:

cd /d "C:\Program Files\SumatraPDF"

Then run:

sumatrapdf-tool.exe

In PowerShell, executables in the current directory commonly need an explicit relative path:

.\sumatrapdf-tool.exe

If this works while the bare command fails elsewhere, the executable is healthy and the problem is command discovery, not SumatraPDF or the source document.

2.4 Decide Whether to Add the Folder to PATH

Using the full executable path is the safest approach for occasional commands and scripts that must be predictable. If you use the tool frequently, you may add its containing directory, not the executable itself, to your Windows user PATH.

1. Open Edit environment variables for your account from Windows search.
2. Select the user Path variable and choose Edit.
3. Add the folder containing sumatrapdf-tool.exe.
4. Close and reopen Command Prompt or PowerShell.
5. Run where sumatrapdf-tool.exe in Command Prompt to see which copy Windows finds.

Success means the command launches from a new terminal regardless of its current directory. If where lists multiple copies, use a full path or remove obsolete PATH entries so that Windows does not launch an unintended build.

3. Check Installed and Portable Locations

Installed and portable copies often cause confusion because shortcuts can open one copy while a terminal command points to another. A portable archive does not register its directory in PATH automatically, and extracting a new archive does not necessarily replace an older installed version.

3.1 Find the Installed Copy

If you launch SumatraPDF from a shortcut, open the shortcut's properties and inspect its target. You can also use Task Manager while the viewer is open, locate the SumatraPDF process, and open its file location. That directory is the relevant place to check for the tool.

On 64-bit Windows, do not assume the application is in one particular Program Files directory. Use the shortcut target or file location instead of guessing. If the tool is present there, launch it using that exact full path.

3.2 Find the Portable Copy

For portable use, the executable remains wherever you extracted the archive, such as a dedicated applications folder, a USB drive, or a Downloads subfolder. The tool must be extracted with the rest of the package. Running an executable from inside a compressed archive or copying only SumatraPDF.exe can leave companion files behind.

Extract the complete archive into a normal writable folder, verify that both executable files are present, and test there. If this succeeds, keep the package together. Do not move only the viewer or only the tool unless the official documentation says that the files are independent.

3.3 Check Security and Permissions

If the file existed but disappeared, review Windows Security protection history or your organization's endpoint-security console. Do not disable antivirus protection merely to make the command run. Confirm the file came from the official SumatraPDF website, verify any warning, and ask an administrator to review a detection when necessary.

Files downloaded from the internet can also carry Windows security metadata. Open the executable's Properties dialog and review any security notice. Only unblock a file when you trust its official source. In managed workplaces, application-control policy may prohibit unapproved command-line utilities even when the graphical viewer is allowed.

If the tool launches but cannot read or write a document, test with a copy stored in a user-owned folder such as Documents. Avoid protected locations, read-only media, synchronized files that are not downloaded locally, and output paths requiring administrator rights. Success means the tool starts and can access the test file without an access-denied error.

4. Separate Tool Discovery From Document Problems

A missing executable and a failed document operation are different symptoms. Windows must locate and launch the tool before file format, rendering, codecs, Ghostscript, printer drivers, or document permissions can affect the result.

4.1 Use a Simple Local Test Document

After the executable launches, test the intended command on a small, ordinary local document that opens correctly in the SumatraPDF viewer. Use short paths and quote every path containing spaces. Work on a copy rather than the only copy of an important file.

If the simple document works, the installation and basic command syntax are likely sound. Stop reinstalling or editing PATH. Compare the failing document's format, permissions, encryption status, filename, path length, and condition with the successful test.

If the document is protected or access-controlled, use it only according to the permissions granted by its owner. This troubleshooting process should not be used to bypass DRM, passwords, or document restrictions.

4.2 Consider External Components Only After Launch

Some workflows may rely on printing infrastructure, format-specific support, or external software. These factors are relevant only when the executable starts and then reports an operation-specific failure.

• For a printing problem, test the printer from another application and check the selected Windows printer driver.
• For PostScript-related workflows, verify whether the documented operation actually requires Ghostscript and whether it is installed correctly.
• For image conversion, confirm that the input format is supported by the selected command and build.
• For network or cloud files, copy the source locally to rule out availability and permission problems.

Do not install random codec packs or third-party PDF utilities to fix a literal “not recognized” message. Such a message means Windows cannot find the requested executable, not that the PDF renderer lacks a codec.

5. Inspect SumatraPDF-settings.txt Safely

SumatraPDF stores viewer preferences in SumatraPDF-settings.txt. This file can matter when viewer settings fail to persist or when you are diagnosing normal SumatraPDF.exe behavior. It generally does not make a missing sumatrapdf-tool.exe appear, and resetting it should not be the first response to a command-not-found error.

5.1 Locate and Back Up the Settings File

The settings location depends on how SumatraPDF is being used. An installed copy commonly stores user settings in the user's application-data area, while portable behavior can involve the application folder when it is writable. Use the viewer's settings or advanced-options interface, when available, to identify and edit the active file rather than guessing.

Close SumatraPDF before making manual changes. Copy the settings file to a safe backup location. If you need a reset test, rename it to something recognizable such as SumatraPDF-settings.backup.txt instead of deleting it.

Restart the viewer and let it create fresh defaults. Success means the original viewer symptom disappears with the clean settings file. Restore the backup if the reset changes nothing or if you need your preferences back.

5.2 Know When Settings Are Irrelevant

If Command Prompt says that sumatrapdf-tool.exe is not recognized, the shell has not launched SumatraPDF code. Editing viewer preferences cannot correct a missing file, incorrect path, incomplete portable extraction, or absent PATH entry. Return to the executable-location checks instead.

6. Run a Clean Temporary Test

A clean test can distinguish a damaged installation from PATH confusion without deleting settings or disrupting your working viewer.

1. Download the appropriate package from the official SumatraPDF website.
2. Create a new temporary folder in a user-writable location.
3. Extract the complete package into that folder if it is an archive.
4. Confirm visually whether sumatrapdf-tool.exe is included.
5. Open a terminal in that folder and launch the tool with .\sumatrapdf-tool.exe in PowerShell or its filename in Command Prompt.
6. After it displays help or usage output, test a supported command on a copy of a simple local document.

If the clean copy works, keep your existing settings intact. Correct the old shortcut, PATH entry, extraction, or installation location instead of deleting unrelated preferences. If the fresh official package does not contain the tool, confirm that you selected a package or build that actually provides it. If it contains the tool but Windows blocks it, record the exact security message and investigate policy or protection history.

7. Quick Fix Checklist

• Confirm that sumatrapdf-tool.exe physically exists next to SumatraPDF.exe.
• Check whether your selected stable or pre-release package includes the newer tool.
• Run the executable once by its full quoted path.
• In PowerShell, use .\sumatrapdf-tool.exe from the correct directory.
• Use where sumatrapdf-tool.exe to detect old or conflicting PATH entries.
• Extract the entire portable archive rather than copying only the viewer.
• Use documented SumatraPDF.exe flags for viewer and supported printing tasks.
• Do not troubleshoot command syntax until the executable launches.
• Test commands on a simple local document with quoted paths.
• Review security history if the executable was removed or blocked.
• Reset SumatraPDF-settings.txt only for a relevant viewer-settings problem.
• Stop changing installation settings once help output appears and a simple test succeeds.

8. Frequently Asked Questions

8.1 Why Is sumatrapdf-tool.exe Not Recognized?

Windows cannot find the executable under the name you entered. It may be missing, outside the current directory, absent from PATH, or stored under a different SumatraPDF installation. Run it by full path first. If that works, correct the working directory or PATH rather than reinstalling the viewer.

8.2 Should sumatrapdf-tool.exe Be Next to SumatraPDF.exe?

In a distribution that includes the tool, that is the first and most relevant location to check. If the viewer is present but the tool is not, verify the contents of the exact package you downloaded. Do not assume all stable, pre-release, installed, and portable packages contain identical files.

8.3 Can I Use SumatraPDF.exe Instead?

Use SumatraPDF.exe when its documented viewer command-line flags support your goal, such as opening a document in a particular way or performing a supported printing operation. It is not a drop-in replacement for separate grep, convert, extract, or merge subcommands. Confirm which executable the documentation assigns to the task.

8.4 Why Does the Command Work Only Inside the SumatraPDF Folder?

The SumatraPDF directory is not on PATH, or your shell requires an explicit current-directory prefix. Use a full path, run the command from that folder, or add the folder to your user PATH. In PowerShell, try .\sumatrapdf-tool.exe.

8.5 Will Reinstalling SumatraPDF Fix the Missing Tool?

Only if the replacement package includes the tool and installs or extracts it successfully. Reinstalling the same package that does not contain the executable will not help. A clean temporary extraction is usually a faster and safer test.

8.6 Should I Delete SumatraPDF-settings.txt?

Not for a literal executable-not-found message. The settings file affects viewer preferences, while command discovery is handled by Windows, the current folder, and PATH. Back up and reset the settings file only when a reproducible viewer-setting problem justifies it.