EErrorHarbor
Error Library

SignTool.exe Not Found: Locate the Windows SDK Before Editing PATH

`SignTool.exe` is a Windows SDK utility. Before changing PATH or downloading anything, check whether the SDK already installed a versioned copy under Windows Kits.

Windows SDK · SignToolWindows 10/11 · Visual StudioLast reviewed Sep 25, 2026
🎯 You’re likely in the right place if:
A build, signing script or terminal says SignTool.exe cannot be found.You use Visual Studio, MSBuild, Windows SDK, WDK or a code-signing workflow.The failure occurs before the signing operation itself starts.
Difficulty: Easy–ModerateRisk: Low first
🔎 Quick Check — locate the installed SDK copy

Use PowerShell to search the standard Windows SDK bin directory for installed SignTool versions.

Get-ChildItem "${env:ProgramFiles(x86)}\Windows Kits\10\bin" -Filter signtool.exe -Recurse -ErrorAction SilentlyContinue | Select-Object -First 5 -ExpandProperty FullName

Verify: If one or more full paths are returned, SignTool is installed and the remaining issue is how your shell or build resolves it.

Did PowerShell find SignTool.exe?
ADSENSE · reserved slot after the first useful step

Why this happens

Microsoft ships SignTool as part of the Windows SDK, typically inside a versioned `Windows Kits\10\bin\\` directory. A normal shell may not have that directory on PATH even though the tool is installed.

Diagnose before changing more

1
Does the SDK path contain SignTool?
If yes, use the exact path or a Visual Studio Developer shell before modifying global PATH.
2
Are you running a normal PowerShell/cmd window?
Developer Command Prompt or Developer PowerShell may provide the expected build-tool environment.
3
Is the Windows SDK component installed?
If the search returns nothing, verify the Windows SDK/Visual Studio workload rather than copying SignTool from another machine.

Fix #2 — use the Developer shell or the full SDK path

Run the signing step from Visual Studio Developer PowerShell/Command Prompt, or configure your build to use the full path returned by the search. This avoids a machine-wide PATH change.

& 'C:\Program Files (x86)\Windows Kits\10\bin\\x64\signtool.exe' /?
🟡 Before changing configuration: Replace the placeholder with the version and architecture that actually exist on your machine.
Did Fix #2 work?

Fix #3 — install the Windows SDK component if SignTool is absent

If no SDK copy exists, add the appropriate Windows SDK through Visual Studio Installer or Microsoft’s official SDK installer. After installation, rerun the location check and then `signtool /?`.

signtool /?
🟡 Keep it reversible: Do not download a standalone SignTool.exe from unofficial DLL/tool sites.
Did Fix #3 work?

Still seeing the error?

If SignTool is found but your build still reports it missing, inspect the build script, CI runner or MSBuild environment that launches the signing step. The interactive shell and the build process may have different PATH values.

Official references

Microsoft: SignToolOfficial location, purpose and command syntax →Microsoft: SignTool.exe (.NET Framework tools)Developer shell guidance and signing options →

Still stuck? Ask the community

Share your operating system, software version, exact error text, and which fix you already tried. Another reader may have seen the same setup.

Keep it safe: never post passwords, API keys, access tokens, recovery codes, license keys, private URLs, or confidential logs.
Powered by GitHub DiscussionsSign in with GitHub to comment. Reading comments does not require sign-in.

Loading community discussion…