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 #3312] More choices with in Windows Installation #64073

New Issue
Closed
opened 2026-05-03 16:04:37 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-03 16:04:37 -05:00
Owner
Copy Link

Originally created by @nightboysfm on GitHub (Mar 23, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3312

What are you trying to do?

I want to have some controls on how and where the software is installing itself.

For various reasons I think it's not pretty good because it install itself in your user profile which is bad for numerous reasons:

  • You'll get insanely huge AD roaming profiles....
  • Same FSLogix profiles
  • Space on disk C: ?
  • Since it's in the user profile, no admin right is required, this not a good thing in a corporate or educational environnement because you have no control on what users are doing. Well solutions exist to block it but not in a simple way.

I mean is there technical reasons to do it like this ? Like 95% of softwares let you choose where you want to install them and where they put their datas.

How should we solve this?

  • Asking admin rights, so simple users can't install it without asking to an admin.
  • Let us choose the installation path
  • It would be wonderful if we can also chose the models installation path
  • Or install models into a subfolder of the installation path
  • If not possible at least let us set the model path in a config file instead of environment variable
  • Command line arguments would be the amazing, imagine if we can deploy software like this: OllamaSetup.exe --install_path=D:\Ollama --models_path=E:\Ollama_Datas /SILENT

What is the impact of not solving this?

(How) Are you currently working around the issue?
To be frank I don't want to bother with tricks to get around this right now, I'm going to use alternative softwares. But I think the software would greatly benefit from theses additions.

Anything else?

I'm aware of https://github.com/ollama/ollama/issues/2621 but I think it's more a workaround than a proper solution.

Originally created by @nightboysfm on GitHub (Mar 23, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3312 ### What are you trying to do? I want to have some controls on how and where the software is installing itself. For various reasons I think it's not pretty good because it install itself in your user profile which is bad for numerous reasons: - You'll get insanely huge AD roaming profiles.... - Same FSLogix profiles - Space on disk C: ? - Since it's in the user profile, no admin right is required, this not a good thing in a corporate or educational environnement because you have no control on what users are doing. Well solutions exist to block it but not in a simple way. I mean is there technical reasons to do it like this ? Like 95% of softwares let you choose where you want to install them and where they put their datas. ### How should we solve this? - Asking admin rights, so simple users can't install it without asking to an admin. - Let us choose the installation path - It would be wonderful if we can also chose the models installation path - Or install models into a subfolder of the installation path - If not possible at least let us set the model path in a config file instead of environment variable - Command line arguments would be the amazing, imagine if we can deploy software like this: OllamaSetup.exe --install_path=D:\Ollama --models_path=E:\Ollama_Datas /SILENT ### What is the impact of not solving this? (How) Are you currently working around the issue? To be frank I don't want to bother with tricks to get around this right now, I'm going to use alternative softwares. But I think the software would greatly benefit from theses additions. ### Anything else? I'm aware of https://github.com/ollama/ollama/issues/2621 but I think it's more a workaround than a proper solution.
GiteaMirror commented 2026-05-03 16:04:39 -05:00
Author
Owner
Copy Link

@FilkerZero commented on GitHub (Mar 23, 2024):

I would also suggest adding an option to not start ollama server at boot and to have the model directory in another location from the application itself.

<!-- gh-comment-id:2016558483 --> @FilkerZero commented on GitHub (Mar 23, 2024): I would also suggest adding an option to not start ollama server at boot and to have the model directory in another location from the application itself.
GiteaMirror commented 2026-05-03 16:04:40 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Mar 24, 2024):

We're tracking custom installation for windows in #2776

<!-- gh-comment-id:2016916576 --> @dhiltgen commented on GitHub (Mar 24, 2024): We're tracking custom installation for windows in #2776
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
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#64073
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?