[GH-ISSUE #10270] Environment Variable Not Used - On Install #68801

Open
opened 2026-05-04 15:12:41 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @Justinius on GitHub (Apr 14, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10270

What is the issue?

This may be related to #4749.

On windows, if you have an environment variable set like OLLAMA_MODELS or OLLAMA_NOHISTORY, after the install is done and the service is started it doesn't respect the environment variable and uses the default.

If you stop the application and restart, it pulls the environment variables correctly. For managed deployments this requires the application to be started/stopped during the deployment to make sure it picks up the values correctly.

Relevant log output


OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.6.5

Originally created by @Justinius on GitHub (Apr 14, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10270 ### What is the issue? This may be related to [#4749](https://github.com/ollama/ollama/issues/4749). On windows, if you have an environment variable set like OLLAMA_MODELS or OLLAMA_NOHISTORY, after the install is done and the service is started it doesn't respect the environment variable and uses the default. If you stop the application and restart, it pulls the environment variables correctly. For managed deployments this requires the application to be started/stopped during the deployment to make sure it picks up the values correctly. ### Relevant log output ```shell ``` ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.6.5
GiteaMirror added the bug label 2026-05-04 15:12:41 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#68801