What this error means
The full error message is:
In PowerShell it looks like:
Both mean the same thing: Windows cannot find ollama.exe in any folder on your PATH. This is almost always one of three causes: PATH not updated, terminal not restarted, or Ollama not installed.
Open a new terminal window
This is the fix for 80% of cases. When Ollama installs, it adds itself to your PATH — but that change only applies to new terminal sessions. Any terminal that was already open before you installed Ollama will not see it.
Check what is actually happening
Before changing PATH settings, run these checks in a new terminal:
If Step 1 fails: Ollama is not installed → Download and install.
If Step 1 passes but Step 2 fails: PATH is not set → continue to Fix 2.
Ollama is installed but not on PATH
Ollama installs to %LOCALAPPDATA%\Programs\Ollama. Add this folder to your PATH:
GUI method (permanent)
- Press Win+S → search Environment Variables → click Edit environment variables for your account.
- Select Path → Edit → New.
- Type
%LOCALAPPDATA%\Programs\Ollamaand click OK on all dialogs. - Open a new terminal and run
ollama --version.
Command line method (current session only)
This works only in the current window. Use the GUI method for a permanent fix.
Ollama is not installed
If the dir check in step 1 above returns "File Not Found", Ollama is not installed. Download and install OllamaSetup.exe, then open a new terminal and try again.
Wrong Ollama version in PATH (Git or other tools)
Some tools like Git for Windows, Cygwin or Anaconda bundle older OpenSSL or other binaries that could shadow commands. Run where ollama to see all resolved paths:
Not recognized questions
Works in cmd.exe but not in PowerShell
ollama pull works but ollama run does not
run fails, check if the Ollama service is running: right-click the system tray icon. If there is no tray icon, start Ollama from the Start menu.After Windows update, ollama stopped working
setx says "SUCCESS" but ollama still not found
setx saves the PATH change to the registry but the current terminal does not see it. Close the terminal completely, open a new one, and try again.