PSCP not found
What “PSCP not found” usually means
When PuTTY reports pscp, the client has already attempted a network or protocol step and failed before a normal interactive shell is available. This guide explains what the message usually means on Windows clients, which local settings to verify first, and when the problem is almost certainly on the server, firewall, or DNS path rather than inside the PuTTY GUI.
Windows cannot find pscp.exe—PATH issue, standalone install incomplete, or command typed in a directory without the binary.
Independent resource: Putty.info is educational only and is not affiliated with the official PuTTY project. Compare symptoms against the official documentation for your installed version.
Symptoms you will see
Operators usually notice this failure in one of a few repeatable ways. Capture the exact dialog text, the hostname and port from the Session panel, and whether the failure happens before or after a username prompt—those details decide which checklist below applies.
- Command not recognized in cmd/PowerShell.
- GUI PuTTY works because its Start Menu shortcut points at an absolute path.
Likely causes ranked by frequency
Several independent conditions can produce the same client-facing wording. Work from the outside in: reachability first, protocol selection second, authentication third. Changing key files will not fix a TCP refusal, and opening a wider firewall will not fix a rejected public key.
- Only putty.exe copied; PSCP omitted.
- Installer PATH not refreshed in the open shell.
- Typo (pscp vs pscp.exe vs wrong directory).
Step-by-step client checks
Use this ordered checklist on a workstation you control. Prefer saved sessions so Host Name, Port, and Connection type stay consistent while you isolate one variable at a time.
- Locate pscp.exe under the official install directory.
- Use full path or reopen the shell after MSI install.
- Prefer full PuTTY install from official packages rather than random single-file copies.
- Verify you did not download a fake “pscp” from a bundler site.
- See /file-transfer/pscp/ for usage once the binary runs.
- Confirm corporate software restriction policies are not blocking the executable.
Do not paste private keys, passphrases, or production passwords into Putty.info tools or contact forms. Diagnose locally with PuTTY, Plink, PSCP, or PSFTP from an official install.
When it is a server or network issue
Not a server problem. Standardize jump-host images with official MSI installs and documented PATH.
If TCP connects from another network path but fails from yours, involve the network team with traceroute/path evidence rather than repeatedly regenerating keys. If authentication fails after a banner appears, collect the server sshd logs for the same timestamp and username—client-side retries alone rarely reveal AccountLocked, Match blocks, or AllowUsers denials.