[GH-ISSUE #11804] Feature request: Ability to disable auto-update permanently #69890

Closed
opened 2026-05-04 19:43:44 -05:00 by GiteaMirror · 6 comments
Owner

Originally created by @erbanku on GitHub (Aug 8, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11804

Originally assigned to: @jmorganca on GitHub.

It is very frustrating and annoying that Ollama frequently auto-updates, causing repeated issues in our products.

We have to spend significant time debugging and resolving problems several times a week.

Currently, the only way to block updates seems to be by going completely offline or blocking ollama.com, which also prevents model installation. This is highly disruptive.

Please provide users with an option to permanently disable auto-updates, giving more control to the user.

Originally created by @erbanku on GitHub (Aug 8, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11804 Originally assigned to: @jmorganca on GitHub. It is very frustrating and annoying that Ollama frequently auto-updates, causing repeated issues in our products. We have to spend significant time debugging and resolving problems several times a week. Currently, the only way to block updates seems to be by going completely offline or blocking `ollama.com`, which also prevents model installation. This is highly disruptive. Please provide users with an option to permanently disable auto-updates, giving more control to the user.
GiteaMirror added the appfeature request labels 2026-05-04 19:43:45 -05:00
Author
Owner

@ice6 commented on GitHub (Aug 8, 2025):

@erbanku +1

<!-- gh-comment-id:3166852845 --> @ice6 commented on GitHub (Aug 8, 2025): @erbanku +1
Author
Owner

@jmorganca commented on GitHub (Aug 8, 2025):

@erbanku so sorry about this. Will make sure this can be better controlled in the app. May I ask what the source of the breakages was? Will make sure to address this as well.

<!-- gh-comment-id:3169489478 --> @jmorganca commented on GitHub (Aug 8, 2025): @erbanku so sorry about this. Will make sure this can be better controlled in the app. May I ask what the source of the breakages was? Will make sure to address this as well.
Author
Owner

@erbanku commented on GitHub (Aug 9, 2025):

@erbanku so sorry about this. Will make sure this can be better controlled in the app. May I ask what the source of the breakages was? Will make sure to address this as well.

Our product needs to interact with ollma via our plugin, and we have 30+ models for testing and different use cases, which is compatible with specific ollama versions. As such needs long-term compatibility, other than some features and improvements which we have never used, even in the future 10 years or so.

So just give users control, or a non-disruptive way to disable updates, if the new version of ollama has the features or improvements we need in the future, we naturally update it.

<!-- gh-comment-id:3169648968 --> @erbanku commented on GitHub (Aug 9, 2025): > [@erbanku](https://github.com/erbanku) so sorry about this. Will make sure this can be better controlled in the app. May I ask what the source of the breakages was? Will make sure to address this as well. Our product needs to interact with ollma via our plugin, and we have 30+ models for testing and different use cases, which is compatible with specific ollama versions. As such needs long-term compatibility, other than some features and improvements which we have never used, even in the future 10 years or so. So just give users control, or a non-disruptive way to disable updates, if the new version of ollama has the features or improvements we need in the future, we naturally update it.
Author
Owner

@D0k-Soundwave commented on GitHub (Aug 20, 2025):

definitely this, the latest update on windows 28/08/25 v0.11.5 seems to cause error with "Error model runner has unexpectedly stopped, this may be due to resource limitations or an internal error, check ollama server logs for details.", and doesn't even appear in the log files.

Users who have re-installed 11.4 have then had it auto update to the new version and had the same error.

<!-- gh-comment-id:3206283117 --> @D0k-Soundwave commented on GitHub (Aug 20, 2025): definitely this, the latest update on windows 28/08/25 v0.11.5 seems to cause error with "Error model runner has unexpectedly stopped, this may be due to resource limitations or an internal error, check ollama server logs for details.", and doesn't even appear in the log files. Users who have re-installed 11.4 have then had it auto update to the new version and had the same error.
Author
Owner

@erbanku commented on GitHub (Aug 27, 2025):

@jmorganca any update for this issue?🥲

<!-- gh-comment-id:3228425704 --> @erbanku commented on GitHub (Aug 27, 2025): @jmorganca any update for this issue?🥲
Author
Owner

@erbanku commented on GitHub (Aug 29, 2025):

Closing due to inactivity.
This issue has been inactive for about 1 month and seems to have been overlooked.
Closing it for now.

<!-- gh-comment-id:3235712622 --> @erbanku commented on GitHub (Aug 29, 2025): Closing due to inactivity. This issue has been inactive for about 1 month and seems to have been overlooked. Closing it for now.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#69890