github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #8783] Ollama Auto-Starts on Windows Without User Permission #52214

New Issue
Closed
opened 2026-04-28 22:31:34 -05:00 by GiteaMirror · 24 comments
GiteaMirror commented 2026-04-28 22:31:34 -05:00
Owner
Copy Link

Originally created by @TreyEvreux on GitHub (Feb 3, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/8783

What is the issue?

Ollama is automatically starting on Windows boot, even though there’s no setting to enable or disable this behavior. Users have no obvious way to prevent it from launching on startup.

Steps to Reproduce:

Install Ollama on Windows 11 (possibly affects other versions too).
Restart the computer.
Check running processes (tasklist | findstr "ollama") and network ports (netstat -ano | findstr :11434).
Ollama is running even though the user did not launch it manually.
Expected Behavior:

Ollama should not start automatically unless the user explicitly enables it.
If auto-start is intentional, there should be a clear setting to toggle it.
Actual Behavior:

Ollama silently adds itself to the Windows Startup folder (shell:startup) without notifying the user.
There is no visible setting to disable it.
The only way to stop this behavior is to manually delete Ollama.lnk from C:\Users<User>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup.
Workaround (Temporary Fix):
To manually prevent Ollama from starting on boot:

Press Win + R, type shell:startup, and press Enter.
Delete Ollama.lnk from the folder.
Restart the computer and confirm that Ollama no longer auto-starts.

Additional Context:
This issue is frustrating for users who don’t expect an AI model service to launch on startup. There should be a toggle option in the settings or at least a clear installation prompt asking whether the user wants Ollama to start on boot.

Would love to see this fixed so users have control over when Ollama runs! 👍

OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.5.7

Originally created by @TreyEvreux on GitHub (Feb 3, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/8783 ### What is the issue? Ollama is automatically starting on Windows boot, even though there’s no setting to enable or disable this behavior. Users have no obvious way to prevent it from launching on startup. Steps to Reproduce: Install Ollama on Windows 11 (possibly affects other versions too). Restart the computer. Check running processes (tasklist | findstr "ollama") and network ports (netstat -ano | findstr :11434). Ollama is running even though the user did not launch it manually. Expected Behavior: Ollama should not start automatically unless the user explicitly enables it. If auto-start is intentional, there should be a clear setting to toggle it. Actual Behavior: Ollama silently adds itself to the Windows Startup folder (shell:startup) without notifying the user. There is no visible setting to disable it. The only way to stop this behavior is to manually delete Ollama.lnk from C:\Users\<User>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. Workaround (Temporary Fix): To manually prevent Ollama from starting on boot: Press Win + R, type shell:startup, and press Enter. Delete Ollama.lnk from the folder. Restart the computer and confirm that Ollama no longer auto-starts. Additional Context: This issue is frustrating for users who don’t expect an AI model service to launch on startup. There should be a toggle option in the settings or at least a clear installation prompt asking whether the user wants Ollama to start on boot. Would love to see this fixed so users have control over when Ollama runs! 👍 ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.5.7
GiteaMirror added the bug label 2026-04-28 22:31:34 -05:00
GiteaMirror commented 2026-04-28 22:31:37 -05:00
Author
Owner
Copy Link

@iLikeToCode commented on GitHub (Mar 4, 2025):

this was making me wonder why my games were running slow, thanks for the fix, still annoying though

<!-- gh-comment-id:2698818776 --> @iLikeToCode commented on GitHub (Mar 4, 2025): this was making me wonder why my games were running slow, thanks for the fix, still annoying though
GiteaMirror commented 2026-04-28 22:31:38 -05:00
Author
Owner
Copy Link

@Fabricio333 commented on GitHub (Mar 6, 2025):

Same Issue Here, is there a solution? Chatgpt says that deleting the .ink file from start folder will prevent this but an update will create the file again.

<!-- gh-comment-id:2704504321 --> @Fabricio333 commented on GitHub (Mar 6, 2025): Same Issue Here, is there a solution? Chatgpt says that deleting the .ink file from start folder will prevent this but an update will create the file again.
GiteaMirror commented 2026-04-28 22:31:39 -05:00
Author
Owner
Copy Link

@comodoro commented on GitHub (Jul 31, 2025):

How is this completed? The issue is undeniable, I'm also facing it. Or have you forgot to leave a comment?

<!-- gh-comment-id:3139661071 --> @comodoro commented on GitHub (Jul 31, 2025): How is this completed? The issue is undeniable, I'm also facing it. Or have you forgot to leave a comment?
GiteaMirror commented 2026-04-28 22:31:40 -05:00
Author
Owner
Copy Link

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

In prior versions, the app would clobber the users updates to remove the windows/mac start-at-login wiring and always start. That was a bug which has been fixed, and we've added a FAQ explaining how you can disable the start at login behavior if you prefer.

<!-- gh-comment-id:3140348746 --> @dhiltgen commented on GitHub (Jul 31, 2025): In prior versions, the app would clobber the users updates to remove the windows/mac start-at-login wiring and always start. That was a bug which has been fixed, and we've added a [FAQ](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-can-i-stop-ollama-from-starting-when-i-login-to-my-computer) explaining how you can disable the start at login behavior if you prefer.
GiteaMirror commented 2026-04-28 22:31:41 -05:00
Author
Owner
Copy Link

@mlarabi commented on GitHub (Aug 20, 2025):

Is this by design? Having the application register itself as a startup app without user permission?

<!-- gh-comment-id:3204839675 --> @mlarabi commented on GitHub (Aug 20, 2025): Is this by design? Having the application register itself as a startup app without user permission?
GiteaMirror commented 2026-04-28 22:31:44 -05:00
Author
Owner
Copy Link

@andywarburton commented on GitHub (Nov 1, 2025):

In prior versions, the app would clobber the users updates to remove the windows/mac start-at-login wiring and always start. That was a bug which has been fixed, and we've added a FAQ explaining how you can disable the start at login behavior if you prefer.

this FAQ no longer exists, and the new FAQ has no mention of this

<!-- gh-comment-id:3476282174 --> @andywarburton commented on GitHub (Nov 1, 2025): > In prior versions, the app would clobber the users updates to remove the windows/mac start-at-login wiring and always start. That was a bug which has been fixed, and we've added a [FAQ](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-can-i-stop-ollama-from-starting-when-i-login-to-my-computer) explaining how you can disable the start at login behavior if you prefer. this FAQ no longer exists, and the new FAQ has no mention of this
GiteaMirror commented 2026-04-28 22:31:46 -05:00
Author
Owner
Copy Link

@MrStyles02 commented on GitHub (Nov 15, 2025):

This is still a problem. This is invasive behaviour and should never be allowed. Users should have full control over this, not not the developer, permission needs to be asked for. For the rest of you, go to Settings -> Apps -> Startup and turn it off.

<!-- gh-comment-id:3536042982 --> @MrStyles02 commented on GitHub (Nov 15, 2025): This is still a problem. This is invasive behaviour and should never be allowed. Users should have full control over this, not not the developer, permission needs to be asked for. For the rest of you, go to Settings -> Apps -> Startup and turn it off.
GiteaMirror commented 2026-04-28 22:31:46 -05:00
Author
Owner
Copy Link

@gael-vanderlee commented on GitHub (Nov 21, 2025):

Issue persists for me, and I don't see ollama in the startup apps on windows.

<!-- gh-comment-id:3562143865 --> @gael-vanderlee commented on GitHub (Nov 21, 2025): Issue persists for me, and I don't see ollama in the startup apps on windows.
GiteaMirror commented 2026-04-28 22:31:47 -05:00
Author
Owner
Copy Link

@mwoody450 commented on GitHub (Dec 4, 2025):

Why is this marked closed? I found this on a web search on how to stop Ollama from starting at startup, and find out it's intentional, known behavior and the devs are basically telling you it can't be changed? Uninstall it is; I'll find other software to do this.

<!-- gh-comment-id:3609588922 --> @mwoody450 commented on GitHub (Dec 4, 2025): Why is this marked closed? I found this on a web search on how to stop Ollama from starting at startup, and find out it's intentional, known behavior and the devs are basically telling you it can't be changed? Uninstall it is; I'll find other software to do this.
GiteaMirror commented 2026-04-28 22:31:48 -05:00
Author
Owner
Copy Link

@Bottlecap202 commented on GitHub (Dec 4, 2025):

Copilot issue

<!-- gh-comment-id:3609614328 --> @Bottlecap202 commented on GitHub (Dec 4, 2025): Copilot issue
GiteaMirror commented 2026-04-28 22:31:49 -05:00
Author
Owner
Copy Link

@dhlavaty commented on GitHub (Dec 20, 2025):

It autostarts on Mac as well. Automatic startup without explicit opt-in is intrusive, presumptive, and reflects user-hostile design. This is so invasive and utterly disrespectful.

BTW: FAQ is available on https://github.com/ollama/ollama/blob/main/docs/faq.mdx#how-can-i-stop-ollama-from-starting-when-i-login-to-my-computer atm

<!-- gh-comment-id:3677878843 --> @dhlavaty commented on GitHub (Dec 20, 2025): It autostarts on Mac as well. Automatic startup without explicit opt-in is intrusive, presumptive, and reflects user-hostile design. This is so invasive and utterly disrespectful. BTW: FAQ is available on https://github.com/ollama/ollama/blob/main/docs/faq.mdx#how-can-i-stop-ollama-from-starting-when-i-login-to-my-computer atm
GiteaMirror commented 2026-04-28 22:31:49 -05:00
Author
Owner
Copy Link

@MaverickMartyn commented on GitHub (Jan 23, 2026):

@dhiltgen ´This issue has not been fixed.
I have disabled Ollama in Task manager, and yet it keeps launching on OS boot.

Image

Please re-open this issue.

<!-- gh-comment-id:3789803708 --> @MaverickMartyn commented on GitHub (Jan 23, 2026): @dhiltgen ´This issue has not been fixed. I have disabled Ollama in Task manager, and yet it keeps launching on OS boot. <img width="723" height="48" alt="Image" src="https://github.com/user-attachments/assets/8c601344-a1f9-4867-958f-2ce55cb76615" /> Please re-open this issue.
GiteaMirror commented 2026-04-28 22:31:50 -05:00
Author
Owner
Copy Link

@ilvalerione commented on GitHub (Feb 13, 2026):

Same problem, I'm going to uninstall Ollama.

<!-- gh-comment-id:3896319190 --> @ilvalerione commented on GitHub (Feb 13, 2026): Same problem, I'm going to uninstall Ollama.
GiteaMirror commented 2026-04-28 22:31:51 -05:00
Author
Owner
Copy Link

@mwoody450 commented on GitHub (Feb 13, 2026):

Same problem, I'm going to uninstall Ollama.

That's what I ended up doing. Grabbed koboldcpp instead and never looked back. I'd argue Ollama should be classified as malware if it has no way to turn off starting with the operating system when that's completely unnecessary.

<!-- gh-comment-id:3897132786 --> @mwoody450 commented on GitHub (Feb 13, 2026): > Same problem, I'm going to uninstall Ollama. That's what I ended up doing. Grabbed koboldcpp instead and never looked back. I'd argue Ollama should be classified as malware if it has no way to turn off starting with the operating system when that's completely unnecessary.
GiteaMirror commented 2026-04-28 22:31:51 -05:00
Author
Owner
Copy Link

@MrStyles02 commented on GitHub (Feb 13, 2026):

I disabled mine on startup by going to Windows 11 Settings -> Apps -> Startup - and turned it off

From: mwoody450 @.>
Sent: Friday, February 13, 2026 8:02 AM
To: ollama/ollama @.>
Cc: MrStyles02 @.>; Comment @.>
Subject: Re: [ollama/ollama] Ollama Auto-Starts on Windows Without User Permission (Issue #8783)

[https://avatars.githubusercontent.com/u/20287482?s=20&v=4]mwoody450 left a comment (ollama/ollama#8783)https://github.com/ollama/ollama/issues/8783#issuecomment-3897132786

Same problem, I'm going to uninstall Ollama.

That's what I ended up doing. Grabbed koboldcpp instead and never looked back. I'd argue Ollama should be classified as malware if it has no way to turn off starting with the operating system when that's completely unnecessary.

—
Reply to this email directly, view it on GitHubhttps://github.com/ollama/ollama/issues/8783#issuecomment-3897132786, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7G5T5JRDB52LKHG74G4T2T4LXDNLAVCNFSM6AAAAABWLNMJJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQOJXGEZTENZYGY.
You are receiving this because you commented.Message ID: @.***>

<!-- gh-comment-id:3899511698 --> @MrStyles02 commented on GitHub (Feb 13, 2026): I disabled mine on startup by going to Windows 11 Settings -> Apps -> Startup - and turned it off ________________________________ From: mwoody450 ***@***.***> Sent: Friday, February 13, 2026 8:02 AM To: ollama/ollama ***@***.***> Cc: MrStyles02 ***@***.***>; Comment ***@***.***> Subject: Re: [ollama/ollama] Ollama Auto-Starts on Windows Without User Permission (Issue #8783) [https://avatars.githubusercontent.com/u/20287482?s=20&v=4]mwoody450 left a comment (ollama/ollama#8783)<https://github.com/ollama/ollama/issues/8783#issuecomment-3897132786> Same problem, I'm going to uninstall Ollama. That's what I ended up doing. Grabbed koboldcpp instead and never looked back. I'd argue Ollama should be classified as malware if it has no way to turn off starting with the operating system when that's completely unnecessary. — Reply to this email directly, view it on GitHub<https://github.com/ollama/ollama/issues/8783#issuecomment-3897132786>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7G5T5JRDB52LKHG74G4T2T4LXDNLAVCNFSM6AAAAABWLNMJJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQOJXGEZTENZYGY>. You are receiving this because you commented.Message ID: ***@***.***>
GiteaMirror commented 2026-04-28 22:31:52 -05:00
Author
Owner
Copy Link

@DanaGoyette commented on GitHub (Mar 23, 2026):

Not only does it auto-start, it also repeatedly auto-starts if you kill it. I'm trying to run it in the terminal so I can see the log output, but every time I kill it, it comes back instantly, so my attempt to start it dies with:
Error: listen tcp 127.0.0.1:11434: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.

<!-- gh-comment-id:4114365257 --> @DanaGoyette commented on GitHub (Mar 23, 2026): Not only does it auto-start, it also repeatedly auto-starts if you kill it. I'm trying to run it in the terminal so I can see the log output, but every time I kill it, it comes back instantly, so my attempt to start it dies with: `Error: listen tcp 127.0.0.1:11434: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.`
GiteaMirror commented 2026-04-28 22:31:54 -05:00
Author
Owner
Copy Link

@MaverickMartyn commented on GitHub (Mar 27, 2026):

Just came back to say that I also ended up uninstalling Ollama.
I'll be giving koboldcpp a try instead, as well.

<!-- gh-comment-id:4141095391 --> @MaverickMartyn commented on GitHub (Mar 27, 2026): Just came back to say that I also ended up uninstalling Ollama. I'll be giving koboldcpp a try instead, as well.
GiteaMirror commented 2026-04-28 22:31:56 -05:00
Author
Owner
Copy Link

@santana-repos commented on GitHub (Apr 11, 2026):

Although the issue is definitely still not solved, I have found a silly but effective workaround, however.
After following instructions here, I went to the %USERPROFILE%\AppData\Local\Programs\Ollama and just renamed the ollame.exe to something like _ollama.exe, then after rebooting, ollama service is no longer auto-starting

>ollama list
'ollama' is not recognized as an internal or external command,
operable program or batch file.
>_ollama list
Error: timed out waiting for server to start

That workaround is temporarily solving the issue for me, as I don't need Ollama service to be active all the time, so whenever I really need to use Ollama, I just rename it back to the original, and by performing ollama serve, it starts as expected.

Note: I'm really grateful for the open-source maintainers' effort in keeping Ollama actively evolving and working not just in Linux environments.

<!-- gh-comment-id:4229426264 --> @santana-repos commented on GitHub (Apr 11, 2026): Although the issue is definitely still not solved, I have found a silly but effective workaround, however. After following instructions [here](https://github.com/ollama/ollama/blob/main/docs/faq.mdx#how-can-i-stop-ollama-from-starting-when-i-login-to-my-computer), I went to the `%USERPROFILE%\AppData\Local\Programs\Ollama` and just renamed the `ollame.exe` to something like `_ollama.exe`, then after rebooting, ollama service is no longer auto-starting ```shell >ollama list 'ollama' is not recognized as an internal or external command, operable program or batch file. >_ollama list Error: timed out waiting for server to start ``` That workaround is temporarily solving the issue for me, as I don't need Ollama service to be active all the time, so whenever I really need to use Ollama, I just rename it back to the original, and by performing `ollama serve`, it starts as expected. Note: I'm really grateful for the open-source maintainers' effort in keeping Ollama actively evolving and working not just in Linux environments.
GiteaMirror commented 2026-04-28 22:31:57 -05:00
Author
Owner
Copy Link

@angelspire commented on GitHub (Apr 11, 2026):

Just uninstall it. It's extremely intrusive and opinionated.

<!-- gh-comment-id:4230180800 --> @angelspire commented on GitHub (Apr 11, 2026): Just uninstall it. It's extremely intrusive and opinionated.
GiteaMirror commented 2026-04-28 22:31:58 -05:00
Author
Owner
Copy Link

@sethswango commented on GitHub (Apr 16, 2026):

Ended up uninstalling for this reason

<!-- gh-comment-id:4262064663 --> @sethswango commented on GitHub (Apr 16, 2026): Ended up uninstalling for this reason
GiteaMirror commented 2026-04-28 22:31:59 -05:00
Author
Owner
Copy Link

@barokurniawan commented on GitHub (Apr 21, 2026):

Uninstalling ollama for this reason

<!-- gh-comment-id:4290560069 --> @barokurniawan commented on GitHub (Apr 21, 2026): Uninstalling ollama for this reason
GiteaMirror commented 2026-04-28 22:31:59 -05:00
Author
Owner
Copy Link

@luismesa-io commented on GitHub (Apr 25, 2026):

Not only does it auto-start, it also repeatedly auto-starts if you kill it. I'm trying to run it in the terminal so I can see the log output, but every time I kill it, it comes back instantly, so my attempt to start it dies with: Error: listen tcp 127.0.0.1:11434: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.

I have to do:

Get-Process | Where-Object {$_.ProcessName -like '*ollama*'} | Stop-Process -Force; ollama serve

in Powershell to get rid of ollama and be able to execute ollama serve (I want to be able to see the logs to double-check my context length)

<!-- gh-comment-id:4320215431 --> @luismesa-io commented on GitHub (Apr 25, 2026): > Not only does it auto-start, it also repeatedly auto-starts if you kill it. I'm trying to run it in the terminal so I can see the log output, but every time I kill it, it comes back instantly, so my attempt to start it dies with: `Error: listen tcp 127.0.0.1:11434: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.` I have to do: `Get-Process | Where-Object {$_.ProcessName -like '*ollama*'} | Stop-Process -Force; ollama serve` in Powershell to get rid of ollama and be able to execute ollama serve (I want to be able to see the logs to double-check my context length)
GiteaMirror commented 2026-04-28 22:32:00 -05:00
Author
Owner
Copy Link

@luismesa-io commented on GitHub (Apr 25, 2026):

In prior versions, the app would clobber the users updates to remove the windows/mac start-at-login wiring and always start. That was a bug which has been fixed, and we've added a FAQ explaining how you can disable the start at login behavior if you prefer.

I have deleted the lnk file in windows. I press Quit Ollama and it inevitable starts up on its own IMMEDIATELY.

I can see "beginning update checker" app.log and tray icon re-appear

<!-- gh-comment-id:4320231893 --> @luismesa-io commented on GitHub (Apr 25, 2026): > In prior versions, the app would clobber the users updates to remove the windows/mac start-at-login wiring and always start. That was a bug which has been fixed, and we've added a [FAQ](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-can-i-stop-ollama-from-starting-when-i-login-to-my-computer) explaining how you can disable the start at login behavior if you prefer. I have deleted the lnk file in windows. I press Quit Ollama and it inevitable starts up on its own IMMEDIATELY. I can see "beginning update checker" app.log and tray icon re-appear
GiteaMirror commented 2026-04-28 22:32:01 -05:00
Author
Owner
Copy Link

@sethswango commented on GitHub (Apr 26, 2026):

Too late. Should be an easy option exposed in the UI. Sent from my iPhoneOn Apr 25, 2026, at 12:59 PM, luismesa-io @.***> wrote:luismesa-io left a comment (ollama/ollama#8783)

In prior versions, the app would clobber the users updates to remove the windows/mac start-at-login wiring and always start. That was a bug which has been fixed, and we've added a FAQ explaining how you can disable the start at login behavior if you prefer.

I have deleted the lnk file in windows. I press Quit Ollama and it inevitable starts up on its own IMMEDIATELY.
I can see "beginning update checker" app.log and tray icon re-appear

—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you commented.Message ID: @.***>

<!-- gh-comment-id:4321135221 --> @sethswango commented on GitHub (Apr 26, 2026): Too late. Should be an easy option exposed in the UI. Sent from my iPhoneOn Apr 25, 2026, at 12:59 PM, luismesa-io ***@***.***> wrote:luismesa-io left a comment (ollama/ollama#8783) In prior versions, the app would clobber the users updates to remove the windows/mac start-at-login wiring and always start. That was a bug which has been fixed, and we've added a FAQ explaining how you can disable the start at login behavior if you prefer. I have deleted the lnk file in windows. I press Quit Ollama and it inevitable starts up on its own IMMEDIATELY. I can see "beginning update checker" app.log and tray icon re-appear —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you commented.Message ID: ***@***.***>
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 bug
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#52214
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?