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

[GH-ISSUE #9095] update failure #5919

New Issue
Closed
opened 2026-04-12 17:15:30 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-12 17:15:30 -05:00
Owner
Copy Link

Originally created by @NGC13009 on GitHub (Feb 14, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/9095

Originally assigned to: @dhiltgen on GitHub.

What is the issue?

I'm Windows, and for each update on ollama, I need to manually exit from the tray icon, then start it up with administrator privileges, and after that, right-click on the tray icon to update it, before the update succeeds.

If you right click the tray icon to update directly, then it will go through the process normally, but not actually update.

I hope that when the user updates, an automatic UAC privilege prompt pops up, so that the program can be upgraded with administrator privileges and then restarted with user privileges.

Note: ollama is installed under the default user path, which theoretically should not require administrator privileges, and I'm not sure what's causing this.

Relevant log output

(The log does not contain any information about this)

OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.5.9

Originally created by @NGC13009 on GitHub (Feb 14, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/9095 Originally assigned to: @dhiltgen on GitHub. ### What is the issue? I'm Windows, and for each update on ollama, I need to manually exit from the tray icon, then start it up with administrator privileges, and after that, right-click on the tray icon to update it, before the update succeeds. If you right click the tray icon to update directly, then it will go through the process normally, but not actually update. I hope that when the user updates, an automatic UAC privilege prompt pops up, so that the program can be upgraded with administrator privileges and then restarted with user privileges. Note: ollama is installed under the default user path, which theoretically should not require administrator privileges, and I'm not sure what's causing this. ### Relevant log output ```shell (The log does not contain any information about this) ``` ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.5.9
GiteaMirror added the installneeds more infobugwindows labels 2026-04-12 17:15:30 -05:00
GiteaMirror commented 2026-04-12 17:15:33 -05:00
Author
Owner
Copy Link

@LeisureLinux commented on GitHub (Feb 15, 2025):

check your model path, if you originally run by admin user, then the following update need admin permission.

<!-- gh-comment-id:2660826920 --> @LeisureLinux commented on GitHub (Feb 15, 2025): check your model path, if you originally run by admin user, then the following update need admin permission.
GiteaMirror commented 2026-04-12 17:15:34 -05:00
Author
Owner
Copy Link

@NGC13009 commented on GitHub (Feb 16, 2025):

check your model path, if you originally run by admin user, then the following update need admin permission.

The model paths are on other disks that all applications have access to. I use user permissions when installing, and when pulling models, only upgrades will require administrator permissions.

Or could ollama provide a test that prompts for elevation of privileges when it detects that the user's privileges cannot be escalated?

<!-- gh-comment-id:2661330595 --> @NGC13009 commented on GitHub (Feb 16, 2025): > check your model path, if you originally run by admin user, then the following update need admin permission. The model paths are on other disks that all applications have access to. I use user permissions when installing, and when pulling models, only upgrades will require administrator permissions. Or could ollama provide a test that prompts for elevation of privileges when it detects that the user's privileges cannot be escalated?
GiteaMirror commented 2026-04-12 17:15:34 -05:00
Author
Owner
Copy Link

@cs0tony commented on GitHub (Feb 25, 2025):

check your model path, if you originally run by admin user, then the following update need admin permission.

I am in the same situation as him. When installing, I use user permissions and Olama prompts for an update. Click to install, and then Olama restarts. However, Olama is still an old version and prompts for an update repeatedly.

<!-- gh-comment-id:2680379025 --> @cs0tony commented on GitHub (Feb 25, 2025): > check your model path, if you originally run by admin user, then the following update need admin permission. I am in the same situation as him. When installing, I use user permissions and Olama prompts for an update. Click to install, and then Olama restarts. However, Olama is still an old version and prompts for an update repeatedly.
GiteaMirror commented 2026-04-12 17:15:35 -05:00
Author
Owner
Copy Link

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

If you're still hitting this problem, please try to install version 0.9.4 (1 version back at the moment) then let it download the update, right click for Restart to update, and if it still fails, please share the app.log (possibly app-2.log as well) so we can see what is causing the automated upgrade flow to fall over. As others have mentioned, it sounds like some path Ollama is trying to access isn't writable by your account and requires UAC.

explorer %LOCALAPPDATA%\Ollama

<!-- gh-comment-id:3037290722 --> @dhiltgen commented on GitHub (Jul 4, 2025): If you're still hitting this problem, please try to install version [0.9.4](https://github.com/ollama/ollama/releases/tag/v0.9.4) (1 version back at the moment) then let it download the update, right click for Restart to update, and if it still fails, please share the app.log (possibly app-2.log as well) so we can see what is causing the automated upgrade flow to fall over. As others have mentioned, it sounds like some path Ollama is trying to access isn't writable by your account and requires UAC. `explorer %LOCALAPPDATA%\Ollama`
GiteaMirror commented 2026-04-12 17:15:35 -05:00
Author
Owner
Copy Link

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

@dhiltgen I have been using this program for a long time to manage upgrades for ollama, bypassing the automatic upgrade feature of ollama in a manual way. Currently, it works properly on my computer. At the same time, the built-in upgrade feature of ollama is also working normally, at least on my computer, and there have been no upgrade failures. I also don't know what happened

<!-- gh-comment-id:3038341997 --> @NGC13009 commented on GitHub (Jul 5, 2025): @dhiltgen I have been using this program for a long time to manage upgrades for ollama, bypassing the automatic upgrade feature of ollama in a manual way. Currently, it works properly on my computer. At the same time, the built-in upgrade feature of ollama is also working normally, at least on my computer, and there have been no upgrade failures. I also don't know what happened
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 install needs more info 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#5919
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?