CMD-PATH-NOT-FOUND
What it means
The folder path in your command doesn't exist, or was typed incorrectly.
Also seen as: The system cannot find the path specified.
Quick fix steps
- Double-check the exact spelling of every folder in the path, including capitalization of drive letters.
- If the path contains spaces, make sure the whole path is wrapped in quotation marks.
- Use dir to list the contents of the folder you think you're in, to confirm the next folder in your path actually exists there.
For the full step-by-step walkthrough, see Command Prompt Won't Open.
Frequently Asked Questions
Is this different from "is not recognized" errors?
They're related — this specifically means the path (folder location) you referenced doesn't exist, while "not recognized" more often refers to a command or program name itself not being found.
How do I check the exact correct path?
Using dir in the parent folder to list its actual contents, or File Explorer's address bar to copy the exact path, avoids typos that are the most common cause of this error.
Other error codes
CMD-NOT-RECOGNIZED — "is not recognized as an internal or external command"
Command Prompt can't find the program or command you typed, usually because of a typo, a missing space, or the program not being in a location Windows searches by default (its PATH).
CMD-ACCESS-DENIED — "Access is denied" in Command Prompt
The command you ran needs administrator privileges that the current Command Prompt window doesn't have.
DISM-SOURCE-FILES-NOT-FOUND — DISM Error: The Source Files Could Not Be Found
DISM couldn't reach Windows Update to download the repair files it needs, or a local source wasn't specified.
CMD-FILE-IN-USE — "The Process Cannot Access the File Because It Is Being Used by Another Process"
Another program currently has the file open or locked, preventing the command from modifying or deleting it.