Could Not Locate Ollama App? Fixes for Windows and Mac

Both messages mean that something tried to start the Ollama desktop app and could not find it. On Windows, Error: could not locate ollama app comes from the Ollama CLI. It found no server running, looked for ollama app.exe in three places, and found nothing. That usually means the desktop app is not installed (the standalone CLI zip has no app), or the folder it lives in is missing from PATH. On macOS, Unable to find application named 'Ollama' comes from macOS itself, usually printed by the install script right after it copied the app into /Applications. Opening the app by its full path, open /Applications/Ollama.app, normally gets past it. On either system you can skip the app entirely: run ollama serve, and the CLI stops looking for it.

The CLI only goes looking for the app when no server answered its first check. So the moment a server is running, whether that is the desktop app, a service or ollama serve in another window, none of these messages can appear.

Everything below was read from ollama/ollama at tag v0.40.13 (released 28 October 2026), from Ollama's Windows and macOS docs, from Homebrew's package data, or quoted from the GitHub issue linked next to it.

Which of these messages do you have?

There are five versions of "can't find or reach the app" in circulation, printed by the Ollama CLI (in different versions) or by macOS itself. Find yours first, because two of them belong on other pages.

One more Windows variant is Error: unable to start ollama app followed by a system error. That one means the CLI did find ollama app.exe, but Windows refused to run it. The error text after it names the reason.

Windows: where does the CLI look for ollama app.exe?

In three places, in this order: next to the ollama.exe you ran, in %LOCALAPPDATA%\Ollama, and on PATH. This is the search in cmd/start_windows.go, trimmed to the part that matters:

AppName := "ollama app.exe"
exe, err := os.Executable()
...
appExe := filepath.Join(filepath.Dir(exe), AppName)
_, err = os.Stat(appExe)
if errors.Is(err, os.ErrNotExist) {
	// Try the standard install location
	localAppData := os.Getenv("LOCALAPPDATA")
	appExe = filepath.Join(localAppData, "Ollama", AppName)
	_, err := os.Stat(appExe)
	if errors.Is(err, os.ErrNotExist) {
		// Finally look in the path
		appExe, err = exec.LookPath(AppName)
		if err != nil {
			return errors.New("could not locate ollama app")
		}
	}
}

One detail in there is easy to miss. The second place, %LOCALAPPDATA%\Ollama, is where Ollama keeps its logs today. The installer puts the program files in %LOCALAPPDATA%\Programs\Ollama (DefaultDirName in app/ollama.iss), so that check rarely finds anything. In practice the app is found in one of two ways: it sits next to the CLI you ran, or its folder is on PATH. The installer adds its folder to your user PATH for exactly this reason.

So the error has three real causes.

1. There is no desktop app, by design

Ollama's Windows docs describe a standalone ollama-windows-amd64.zip that contains "only the Ollama CLI and GPU library dependencies", meant for running ollama serve as a service with a tool such as NSSM. There is no ollama app.exe in it. If that is how you installed Ollama, the CLI is doing its best to launch something that was never there.

Fix: start the server yourself and leave it running, then use the CLI from a second window:

ollama serve
# in another PowerShell window
ollama list

For something that survives a reboot, either set it up as a service (the route the docs describe for the zip), or install OllamaSetup.exe from ollama.com/download/windows to get the tray app.

2. A different ollama.exe runs first, and the app's folder is not on PATH

If you have more than one ollama.exe (an old standalone copy, one bundled with another tool, or one you copied somewhere), Windows runs whichever comes first on PATH. That copy then looks for the app next to itself, where there is none. Normally the PATH lookup still rescues it, but only if the installer's folder is on PATH and the PATH value is intact.

Check which copy runs and whether the app exists:

where.exe ollama
Get-Command ollama | Format-List Source
Test-Path "$env:LOCALAPPDATA\Programs\Ollama\ollama app.exe"
[System.Environment]::GetEnvironmentVariable('Path', 'User') -split ';'

• where.exe lists more than one path, and the first is not ...\AppData\Local\Programs\Ollama\ollama.exe: remove or rename the other copy, or move the Ollama folder above it in PATH.
• The user PATH has no ...\Programs\Ollama entry: add it back (Settings, search "environment variables", "Edit environment variables for your account"), then open a new terminal.
• The PATH value contains a stray ": everything after that character stops working. This exact problem breaks the tray app as well, and is covered with the commands to find it in Ollama timed out waiting for server to start.

If you installed with a custom folder (OllamaSetup.exe /DIR="d:\some\location", the flag from Ollama's docs), the same rules apply to that folder instead.

3. The install is incomplete

If Test-Path above prints False and you did use the installer, ollama app.exe is missing from the install folder. Re-run the current OllamaSetup.exe. The installer refuses to run twice at once, and the CLI itself stops with Error: upgrade in progress... while OllamaSetup.exe is running, so let any update finish before you try again.

macOS: why does the installer say Unable to find application named 'Ollama'?

Because the install script starts the app by name, and macOS's app database has not caught up with the app it just copied. The relevant lines of scripts/install.sh:

status "Installing Ollama to /Applications..."
unzip -q "$TEMP_DIR/Ollama-darwin.zip" -d "$TEMP_DIR"
mv "$TEMP_DIR/Ollama.app" "/Applications/"
...
status "Starting Ollama..."
open -a Ollama --args hidden

open -a Ollama asks macOS's Launch Services to find an app by name. Issue #16638 (9 June 2026) shows the full failing run, ending in Unable to find application named 'Ollama' straight after >>> Starting Ollama.... The proposed fix, pull request #16640, explains it: "On some systems, Launch Services cannot resolve the application by name immediately after the script removes and replaces the app bundle." The PR changes the line to open the app by its path. It was still open, not merged, on 2 November 2026.

The important part is the order of the script. By the time it reaches open -a, it has already moved the app into /Applications and created the /usr/local/bin/ollama link. So in most cases the install worked, and only the final "start it" step failed.

Check, then start it by path:

ls -d /Applications/Ollama.app
ls -l /usr/local/bin/ollama
open /Applications/Ollama.app
ollama --version

If macOS still cannot see the app, you can ask Launch Services to register it directly:

/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -f /Applications/Ollama.app

When opening by path fails too

A comment on #16640 (30 June 2026) reports that open "/Applications/Ollama.app" then failed with kLSIncompatibleSystemVersionErr: The app cannot run on the current OS version (error -10825). That is a different problem: the Mac is older than the app supports. Ollama's macOS docs require macOS Sonoma (v14) or newer, and Homebrew's ollama-app cask declares the same minimum. Check yours with:

sw_vers -productVersion

If it prints a version below 14, the current app will not run on that Mac, however you install it.

You installed with Homebrew

brew install ollama installs the formula, which is the command-line program and a background service, with no app. On a formula install, open -a Ollama has nothing to open, and the fix is to start the service:

brew services start ollama
ollama list

The formula's service runs ollama serve and writes its log to $(brew --prefix)/var/log/ollama.log, according to Homebrew's package data for 0.40.13. If you want the menu-bar app instead, Homebrew ships it as a separate cask, ollama-app. It installs /Applications/Ollama.app and links ollama in Homebrew's bin folder to the CLI inside the app. Both the formula and the cask put an ollama command in that same folder, so remove one before adding the other:

brew services stop ollama
brew uninstall ollama
brew install --cask ollama-app

macOS: what does "could not find ollama app" mean on older builds?

It means the ollama you ran is not part of an Ollama.app, so the CLI had no app to start when it found no server. Up to v0.15.4, cmd/start_darwin.go resolved the CLI's symlink and checked it against a pattern for an app bundle:

r := regexp.MustCompile(`^.*/Ollama\s?\d*.app`)
m := r.FindStringSubmatch(link)
if len(m) != 1 {
	return errors.New("could not find ollama app")
}

and cmd/cmd.go wrapped any launch failure as ollama server not responding - .... A Homebrew formula install is a symlink into Homebrew's Cellar, never into an app bundle, so on those builds every "no server" moment ends in this message.

We reproduced it on macOS with the Homebrew formula, Ollama 0.12.3, no app installed, and a server running normally on 11434. Pointing the CLI at an unused port gives exactly this:

$ OLLAMA_HOST=127.0.0.1:11999 ollama list
Error: ollama server not responding - could not find ollama app

OLLAMA_HOST=http://localhost ollama list gives the same message on that machine, because http:// with no port means port 80 to Ollama, not 11434. So "could not find ollama app" does not always mean the server is down. It can also mean the CLI is looking at the wrong address. Check echo "$OLLAMA_HOST" before restarting anything.

From v0.15.5 (3 February 2026) the same situation prints could not connect to ollama server, run 'ollama serve' to start it instead, and no longer mentions an app. The fix is the same either way: start the server (brew services start ollama or ollama serve), or fix OLLAMA_HOST. The other causes of an unreachable server are in our connection refused guide.

One real-world case is worth knowing. In issue #13404 (Homebrew, Ollama 0.13.2), ollama list hung and then printed this message, even though brew services showed Ollama running. The models folder was a symlink to an external drive. A commenter traced the same symptom to a macOS prompt asking to give Ollama Full Disk Access, which was waiting unseen on the screen. Granting it under System Settings, Privacy & Security, Full Disk Access fixed it.

Do you need the desktop app at all?

No. The app is a convenience that starts ollama serve for you and adds a chat window. Everything the CLI and other apps talk to is the server on port 11434, and you can run it without the app on every platform:

Do not run the app and ollama serve at the same time. The second one cannot get port 11434 and fails with address already in use. If you have never set Ollama up on Windows before, our Ollama on Windows guide walks through the installer route, and 15 first-time setup mistakes covers what tends to go wrong next.

Honest limitations

• We reproduced the macOS "could not find ollama app" message only, on Homebrew Ollama 0.12.3. The Windows causes follow from the search order in cmd/start_windows.go and from Ollama's install docs. We did not reproduce them on a Windows machine, and we found no bug report built around that exact error to quote.
• The installer explanation is the PR author's. The Launch Services timing in #16640 is their description of why open -a fails. We have not tested it, and the PR is unmerged, so the install script may change.
• Homebrew details are from Homebrew's package data on 2 November 2026 (formula and cask both at 0.40.13). Package names and layouts can change between releases.
• This page does not cover Docker or WSL. Inside a Linux container or a WSL distro, the Linux CLI never looks for a desktop app.

FAQ

Is "could not locate ollama app" a sign of a broken install?

Not necessarily. It only means the CLI found no running server and then found no ollama app.exe to start. If you installed the standalone zip, that is expected, and running ollama serve is the intended way to use it. It points to a broken install only when you used OllamaSetup.exe and ollama app.exe is missing from %LOCALAPPDATA%\Programs\Ollama.

Why does ollama --version work when ollama run says it cannot find the app?

ollama --version does not need a server or the app. It prints the client version, plus a warning if no server answers. ollama run, list, pull and most other commands check for a server first and try to launch the app when there is none. That launch attempt is what fails.

Did the Ollama install fail if I saw Unable to find application named 'Ollama'?

Usually not. The install script prints that message at its very last step, after the app is already in /Applications and the ollama command is already linked. Run open /Applications/Ollama.app and then ollama --version. Only if opening by path also fails is something else wrong, most often a macOS version below 14.

Should I install Ollama on Mac with Homebrew or the app?

Either works. The Homebrew formula gives you the CLI and a background service, with no window, and updates through brew upgrade. The app, from ollama.com or the ollama-app cask, adds the menu-bar icon and chat window, and lets the CLI start the server for you. Pick one. Running both means two servers competing for the same port.

Can I keep Ollama.app outside /Applications?

Yes. Ollama's macOS docs allow it, as long as the ollama on your PATH is the CLI inside that bundle or a symlink to it. The CLI recognises the app by checking that its symlink points into a folder named Ollama.app, so renaming the bundle to something else stops it launching the app for you.

Why does the CLI look in %LOCALAPPDATA%\Ollama if the app is installed in Programs?

The code checks %LOCALAPPDATA%\Ollama, labelled in the source as "the standard install location", but the current installer uses %LOCALAPPDATA%\Programs\Ollama and keeps logs in the first folder. The PATH lookup that follows is what finds a normal install, which is why a damaged PATH can produce this error even when the app is installed.

Other Ollama errors: every error string, indexed · timed out waiting for server to start · ollama: command not found · connection refused on 11434

Sources

• ollama/ollama v0.40.13: cmd/start_windows.go (the three-place search, could not locate ollama app, upgrade in progress...)
• cmd/start_darwin.go, compared with v0.15.4 (could not find ollama app) and v0.15.4 cmd/cmd.go (the "server not responding" prefix)
• app/ollama.iss (the Windows install folder and the PATH entry the installer adds)
• scripts/install.sh (the macOS install steps and open -a Ollama)
• Ollama Windows docs (standalone CLI zip, /DIR, file locations) and macOS docs (macOS 14 or newer, custom install location)
• Homebrew package data: ollama formula and ollama-app cask (read 2 November 2026, both 0.40.13)
• Issues: #16638 (install script: Unable to find application named 'Ollama'), PR #16640 (open by path; the -10825 comment), #13404 (Homebrew, external drive, Full Disk Access)