github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-16 13:19:40 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #10713] Ollama service missing in sevices.msc on Windows 11 (v0.6.8) #7039

New Issue
Closed
opened 2026-04-12 18:56:52 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 18:56:52 -05:00
Owner
Copy Link

Originally created by @Horace1423 on GitHub (May 15, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10713

What is the issue?

Hi, I'm having a persistent issue installing Ollama as a background service on Windows. The core server seems functional, but the service registration is failing.

System Details:

  • OS: Windows 11 Home 24H2
  • Ollama Version: 0.6.8
  • Hardware: Intel i7-10870H, RTX 3060 Laptop

Problem Description:

  1. Ollama does not correctly install/register as a standard Windows Service. There is no "Ollama Service" entry in services.msc.
  2. The Ollama GUI (tray icon) does not appear, and the Start Menu shortcut is unresponsive.
  3. Instead, ollama.exe (and sometimes ollama app.exe) automatically launches via the Task Manager 'Startup apps' entry when Windows starts.
  4. This 'Startup apps' launched instance of ollama.exe occupies port 11434. If I try to run ollama serve manually while this instance is running, I get a "bind: only one usage of each socket address is normally permitted" error.

Key Diagnostic Finding:

  • After killing ALL ollama.exe and ollama app.exe processes in Task Manager, running ollama serve from a standard command prompt works perfectly. It starts the server and shows "Listening on 127.0.0.1:11434". This confirms the core binary and port 11434 are functional when not blocked by the startup instance.

Troubleshooting steps already attempted:

  • Multiple uninstall/reinstall cycles (always using "Run as administrator" for installation).
  • Force-killing all ollama.exe processes before reinstall attempts.
  • Deleting the .ollama folder in the user profile (C:\Users\...\.ollama) and other potential leftover installation directories.
  • Checked services.msc repeatedly before and after reinstall (Ollama Service entry is always missing).
  • Checked Registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services after uninstall - no Ollama entry found there.
  • Used netstat -a -o | findstr "11434" immediately when the "bind" error occurred, which showed the PID belonged to ollama.exe itself (the startup instance).
  • Disabled the Ollama entry in Task Manager 'Startup apps' to prevent automatic incorrect launching.

I am seeking assistance to diagnose why the Windows Service registration is failing persistently on my system and how to get Ollama running correctly as a reliable background service.

Thank you for your help!

Relevant log output

OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.6.8

Originally created by @Horace1423 on GitHub (May 15, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10713 ### What is the issue? Hi, I'm having a persistent issue installing Ollama as a background service on Windows. The core server seems functional, but the service registration is failing. System Details: * OS: Windows 11 Home 24H2 * Ollama Version: 0.6.8 * Hardware: Intel i7-10870H, RTX 3060 Laptop Problem Description: 1. Ollama does not correctly install/register as a standard Windows Service. There is no "Ollama Service" entry in `services.msc`. 2. The Ollama GUI (tray icon) does not appear, and the Start Menu shortcut is unresponsive. 3. Instead, ollama.exe (and sometimes `ollama app.exe`) automatically launches via the Task Manager 'Startup apps' entry when Windows starts. 4. This 'Startup apps' launched instance of ollama.exe occupies port 11434. If I try to run ollama serve manually while this instance is running, I get a "bind: only one usage of each socket address is normally permitted" error. Key Diagnostic Finding: * After killing ALL ollama.exe and ollama app.exe processes in Task Manager, running `ollama serve` from a standard command prompt works perfectly. It starts the server and shows "Listening on 127.0.0.1:11434". This confirms the core binary and port 11434 are functional when not blocked by the startup instance. Troubleshooting steps already attempted: * Multiple uninstall/reinstall cycles (always using "Run as administrator" for installation). * Force-killing all ollama.exe processes before reinstall attempts. * Deleting the .ollama folder in the user profile (`C:\Users\...\.ollama`) and other potential leftover installation directories. * Checked services.msc repeatedly before and after reinstall (Ollama Service entry is always missing). * Checked Registry `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services` after uninstall - no Ollama entry found there. * Used netstat -a -o | findstr "11434" immediately when the "bind" error occurred, which showed the PID belonged to ollama.exe itself (the startup instance). * Disabled the Ollama entry in Task Manager 'Startup apps' to prevent automatic incorrect launching. I am seeking assistance to diagnose why the Windows Service registration is failing persistently on my system and how to get Ollama running correctly as a reliable background service. Thank you for your help! ### Relevant log output ```shell ``` ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.6.8
GiteaMirror added the installquestionwindows labels 2026-04-12 18:56:52 -05:00
GiteaMirror commented 2026-04-12 18:56:54 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Jul 5, 2025):

The Ollama desktop app does not register a system-wide service by design to avoid requiring admin permissions. It sets up as a user Start Menu Startup item to launch when the user logs in.

If you want to run Ollama as a system-wide service, we provide a zip file with every release that can be used with tools like NSSM to set up a system service - see https://github.com/ollama/ollama/blob/main/docs/windows.md#standalone-cli

<!-- gh-comment-id:3040331996 --> @dhiltgen commented on GitHub (Jul 5, 2025): The Ollama desktop app does not register a system-wide service by design to avoid requiring admin permissions. It sets up as a user Start Menu Startup item to launch when the user logs in. If you want to run Ollama as a system-wide service, we provide a zip file with every release that can be used with tools like NSSM to set up a system service - see https://github.com/ollama/ollama/blob/main/docs/windows.md#standalone-cli
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label install question windows
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#7039
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?