[GH-ISSUE #2551] Can we change where the models are stored in windows #1495

New Issue

@zombodotcom commented on GitHub (Jun 29, 2024):

tried this, and also the .\OllamaSetup.exe /DIR=D:\MYDIRECTORY

it still downloads them to the C drive.
Tried moving the models and making the OLLAMA_MODELS Variable does not solve the issue of putting the blobs into the new directory, still tries to download them and doesnt register that they are there.

It does download to the new directory though. which is a plus

@zombodotcom commented on GitHub (Jun 29, 2024): tried this, and also the .\OllamaSetup.exe /DIR=D:\MYDIRECTORY it still downloads them to the C drive. Tried moving the models and making the OLLAMA_MODELS Variable does not solve the issue of putting the blobs into the new directory, still tries to download them and doesnt register that they are there. It does download to the new directory though. which is a plus

GiteaMirror commented

@arfans22 commented on GitHub (Jun 30, 2024):

tried this, and also the .\OllamaSetup.exe /DIR=D:\MYDIRECTORY

it still downloads them to the C drive.
Tried moving the models and making the OLLAMA_MODELS Variable does not solve the issue of putting the blobs into the new directory, still tries to download them and doesnt register that they are there.

It does download to the new directory though. which is a plus

You have to make anothee variable named OLLAMA_ORIGIN and make the value just . (Dot)

@arfans22 commented on GitHub (Jun 30, 2024): > tried this, and also the .\OllamaSetup.exe /DIR=D:\MYDIRECTORY > > it still downloads them to the C drive. > Tried moving the models and making the OLLAMA_MODELS Variable does not solve the issue of putting the blobs into the new directory, still tries to download them and doesnt register that they are there. > > It does download to the new directory though. which is a plus You have to make anothee variable named OLLAMA_ORIGIN and make the value just . (Dot)

GiteaMirror commented

@zombodotcom commented on GitHub (Jun 30, 2024):

still making me redownload the 38gb model

@zombodotcom commented on GitHub (Jun 30, 2024): still making me redownload the 38gb model

GiteaMirror commented

2026-04-12 11:24:16 -05:00

@Kazakuba commented on GitHub (Jul 6, 2024):

Close all ollama tasks
Move whole models folder
Env variable needs to be added for user not as system variable or in path
Or try; mklink /D C:\Users<User>.ollama\models E:\New\Model\Location (for link to work you must first move folder from C)

@Kazakuba commented on GitHub (Jul 6, 2024): Close all ollama tasks Move whole models folder Env variable needs to be added for user not as system variable or in path Or try; mklink /D C:\Users\<User>\.ollama\models E:\New\Model\Location (for link to work you must first move folder from C)

GiteaMirror commented

@zombodotcom commented on GitHub (Jul 6, 2024):

Added to both before posting

@zombodotcom commented on GitHub (Jul 6, 2024): Added to both before posting

GiteaMirror commented

2026-04-12 11:24:16 -05:00

@gary0318 commented on GitHub (Jul 8, 2024):

Nothing was working for me. So, I killed Ollama app.exe and from there on I can not start ollama server. The server log is empty and the main log says server error. I've reinstalled ollama, rebooted the computer checked my environment variables... nothing is working. When it gives me the error it leaves Ollama app.exe running and I have to kill it again..

time=2024-07-08T03:30:58.766-04:00 level=WARN source=server.go:157 msg="server crash 10 - exit code 1 - respawning"
time=2024-07-08T03:30:59.589-04:00 level=INFO source=server.go:135 msg="starting server..."
time=2024-07-08T03:30:59.603-04:00 level=INFO source=server.go:121 msg="started ollama server with pid 11848"
time=2024-07-08T03:30:59.603-04:00 level=INFO source=server.go:123 msg="ollama server logs C:\Users\gary0\AppData\Local\Ollama\server.log"

server log: empty

@gary0318 commented on GitHub (Jul 8, 2024): Nothing was working for me. So, I killed Ollama app.exe and from there on I can not start ollama server. The server log is empty and the main log says server error. I've reinstalled ollama, rebooted the computer checked my environment variables... nothing is working. When it gives me the error it leaves Ollama app.exe running and I have to kill it again.. time=2024-07-08T03:30:58.766-04:00 level=WARN source=server.go:157 msg="server crash 10 - exit code 1 - respawning" time=2024-07-08T03:30:59.589-04:00 level=INFO source=server.go:135 msg="starting server..." time=2024-07-08T03:30:59.603-04:00 level=INFO source=server.go:121 msg="started ollama server with pid 11848" time=2024-07-08T03:30:59.603-04:00 level=INFO source=server.go:123 msg="ollama server logs C:\\Users\\gary0\\AppData\\Local\\Ollama\\server.log" server log: empty

GiteaMirror commented

2026-04-12 11:24:16 -05:00

@amirali-mi10 commented on GitHub (Aug 31, 2024):

if you guys get confused, let me explain step by step:

1-first of all uninstall ollama (if you already installed)

2-then follow this:
Open Windows Settings.
Go to System.
Select About
Select Advanced System Settings.
Go to the Advanced tab.
Select Environment Variables....
Click on New...
And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models)

3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file)

4-then on file explorer write cmd to open cmd on that path

5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY

6-after installation everything should works well and both ollama and models will save same drive you defined for it

@amirali-mi10 commented on GitHub (Aug 31, 2024): if you guys get confused, let me explain step by step: 1-first of all uninstall ollama (if you already installed) 2-then follow this: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models) 3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file) 4-then on file explorer write cmd to open cmd on that path 5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY 6-after installation everything should works well and both ollama and models will save same drive you defined for it

GiteaMirror commented

@Luojz commented on GitHub (Sep 11, 2024):

I just started the installer in cmd with the following directive:我刚刚在命令提示符中使用以下指令启动了安装程序：
$ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY

A thumbs-up from China："牛 B"

@Luojz commented on GitHub (Sep 11, 2024): > I just started the installer in cmd with the following directive:我刚刚在命令提示符中使用以下指令启动了安装程序： > > ``` > $ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY > ``` A thumbs-up from China："牛 B"

GiteaMirror commented

@simpleetech commented on GitHub (Oct 11, 2024):

if you guys get confused, let me explain step by step:

1-first of all uninstall ollama (if you already installed)

2-then follow this: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models)

3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file)

4-then on file explorer write cmd to open cmd on that path

5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY

6-after installation everything should works well and both ollama and models will save same drive you defined for it

I'm not sure if it was just me, but it worked when I set the environment variable as a "User Variable" not a "System Variable"

@simpleetech commented on GitHub (Oct 11, 2024): > if you guys get confused, let me explain step by step: > > 1-first of all uninstall ollama (if you already installed) > > 2-then follow this: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models) > > 3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file) > > 4-then on file explorer write cmd to open cmd on that path > > 5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY > > 6-after installation everything should works well and both ollama and models will save same drive you defined for it I'm not sure if it was just me, but it worked when I set the environment variable as a "User Variable" not a "System Variable"

GiteaMirror commented

@zalito12 commented on GitHub (Oct 11, 2024):

OLLAMA_MODELS env variable also didn't work for me - do we have to reboot or reinstall ollama? i assume it would just pick up the new path when we run "ollama run llama2"

Normally, you have to at least reopen the "command line" process, so that the environment variables are filled (maybe restarting ollama is sufficient). If you use PowerShell, you can use $env:OLLAMA_MODELS to check if the environment variable is set. If you use the Windows command prompt ("cmd"), you can use set to get a list of all environment variables.

I can cornfirm you must restart Ollama, opening a new cmd is not enough.
Also, to see a var on cmd you can use echo, as echo %OLLAMA_MODELS%

@zalito12 commented on GitHub (Oct 11, 2024): > > OLLAMA_MODELS env variable also didn't work for me - do we have to reboot or reinstall ollama? i assume it would just pick up the new path when we run "ollama run llama2" > > Normally, you have to at least reopen the "command line" process, so that the environment variables are filled (maybe restarting ollama is sufficient). If you use PowerShell, you can use `$env:OLLAMA_MODELS` to check if the environment variable is set. If you use the Windows command prompt ("cmd"), you can use `set` to get a list of all environment variables. I can cornfirm you must restart Ollama, opening a new cmd is not enough. Also, to see a var on cmd you can use echo, as ``echo %OLLAMA_MODELS%``

GiteaMirror commented

2026-04-12 11:24:18 -05:00

@angusgee commented on GitHub (Nov 4, 2024):

I just started the installer in cmd with the following directive:
$ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY

This is the one thank you for sharing 🔥🔥🔥

@angusgee commented on GitHub (Nov 4, 2024): > I just started the installer in cmd with the following directive: > > ``` > $ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY > ``` This is the one thank you for sharing 🔥🔥🔥

GiteaMirror commented

@mumangguo commented on GitHub (Dec 12, 2024):

nice

@mumangguo commented on GitHub (Dec 12, 2024): nice

GiteaMirror commented

2026-04-12 11:24:18 -05:00

@AdityaAdaki21 commented on GitHub (Dec 17, 2024):

I just started the installer in cmd with the following directive:
$ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY
What a life saver! It works great, thanks for sharing!

THANK YOU!!!!

@AdityaAdaki21 commented on GitHub (Dec 17, 2024): > > I just started the installer in cmd with the following directive: > > ``` > > $ .\OllamaSetup.exe /DIR=D:\MYDIRECTORY > > ``` > > What a life saver! It works great, thanks for sharing! THANK YOU!!!!

GiteaMirror commented

2026-04-12 11:24:18 -05:00

@jiriehrlich commented on GitHub (Dec 21, 2024):

Uninstall Ollama
Create System Variable OLLAMA_MODELS
Run OllamaSetup.exe /DIR=:\Ollama

@jiriehrlich commented on GitHub (Dec 21, 2024): Uninstall Ollama Create System Variable OLLAMA_MODELS Run OllamaSetup.exe /DIR=<your drive>:\Ollama

GiteaMirror commented

@omesh845 commented on GitHub (Dec 26, 2024):

Uninstall Ollama Create System Variable OLLAMA_MODELS Run OllamaSetup.exe /DIR=:\Ollama

thanks man!! it worked!!!

@omesh845 commented on GitHub (Dec 26, 2024): > Uninstall Ollama Create System Variable OLLAMA_MODELS Run OllamaSetup.exe /DIR=:\Ollama thanks man!! it worked!!!

GiteaMirror commented

@codeisnotcode commented on GitHub (Jan 5, 2025):

if you guys get confused, let me explain step by step:
1-first of all uninstall ollama (if you already installed)
2-then follow this: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models)
3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file)
4-then on file explorer write cmd to open cmd on that path
5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY
6-after installation everything should works well and both ollama and models will save same drive you defined for it

I'm not sure if it was just me, but it worked when I set the environment variable as a "User Variable" not a "System Variable"

I did the above and it did not work until I realized it is important for the original id_ed25519 and id_ed25519.pub key files to be retained in order to be able to see the moved Ollama Models. If you moved these with the models, when you reinstall ollama, it will create new a new set of keys (these two files) in C:\users<username>.ollama and then the previously loaded models can't be read by Ollama. The solution is to copy these two files from your moved model subdirectory back into C:\users<username>.ollama, overwriting the newly created keys.

@codeisnotcode commented on GitHub (Jan 5, 2025): > > if you guys get confused, let me explain step by step: > > 1-first of all uninstall ollama (if you already installed) > > 2-then follow this: Open Windows Settings. Go to System. Select About Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Click on New... And create a variable called OLLAMA_MODELS pointing to where you want to store the models(set path for store models) > > 3-after adjusting that then open the path that you downloaded OllamaSetup.exe (setup file) > > 4-then on file explorer write cmd to open cmd on that path > > 5-on cmd write--> OllamaSetup.exe /DIR=D:\MYDIRECTORY > > 6-after installation everything should works well and both ollama and models will save same drive you defined for it > > I'm not sure if it was just me, but it worked when I set the environment variable as a "User Variable" not a "System Variable" --- I did the above and it did not work until I realized it is important for the original id_ed25519 and id_ed25519.pub key files to be retained in order to be able to see the moved Ollama Models. If you moved these with the models, when you reinstall ollama, it will create new a new set of keys (these two files) in C:\users\<username>\.ollama and then the previously loaded models can't be read by Ollama. The solution is to copy these two files from your moved model subdirectory back into C:\users\<username>\.ollama, overwriting the newly created keys.

GiteaMirror commented

@manotawi commented on GitHub (Jan 27, 2025):

All my AI apps and models are installed in a ssd so I can move them with me. So to preserve that, here was my method:
1- Move the ollama installation where desired, example F:\AI\OLLAMA
2- Inside the ollama installation folder create a folder for the models, example F:\AI\OLLAMA\MODELS
3- create a bat file and add the following to it:
SET OLLAMA_MODELS=%~dp0MODELS
start "" "ollama app.exe"

and tada, with that you have a portable version of ollama, that does not care about the drive or folder it is installed in

@manotawi commented on GitHub (Jan 27, 2025): All my AI apps and models are installed in a ssd so I can move them with me. So to preserve that, here was my method: 1- Move the ollama installation where desired, example F:\AI\OLLAMA 2- Inside the ollama installation folder create a folder for the models, example F:\AI\OLLAMA\MODELS 3- create a bat file and add the following to it: SET OLLAMA_MODELS=%~dp0MODELS start "" "ollama app.exe" and tada, with that you have a portable version of ollama, that does not care about the drive or folder it is installed in

GiteaMirror commented

@JTMarsh556 commented on GitHub (Jan 30, 2025):

Am I reading this correctly, you cannot move all of the existing models you have? You need a fresh install?

You can't just set the variable and then copy the models in the new path?

@JTMarsh556 commented on GitHub (Jan 30, 2025): Am I reading this correctly, you cannot move all of the existing models you have? You need a fresh install? You can't just set the variable and then copy the models in the new path?

GiteaMirror commented

@pratyush0898 commented on GitHub (Feb 2, 2025):

thanks you, but more you can do is:

Move ollama: (folder) C:\Users\ADMIN\AppData\Local\Programs\Ollama to /path/to/Ollama
Change env variable:
- press Win + R
- type systempropertiesadvanced & perss enter
- Go to Environment variables
- Under User variables Doble-click (open) PATH (enviorment variable)
- Locate C:\Users\ADMIN\AppData\Local\Programs\Ollama & change it to `/path/to/Ollama/

here, you go, now your whole OLLAMA is in different location/drive you'd like

@pratyush0898 commented on GitHub (Feb 2, 2025): thanks you, but more you can do is: - **Move ollama**: (folder) C:\Users\ADMIN\AppData\Local\Programs\Ollama to /path/to/Ollama - **Change env variable**: - press `Win + R` - type `systempropertiesadvanced` & perss enter - Go to Environment variables - Under `User variables` Doble-click (open) PATH (enviorment variable) - Locate `C:\Users\ADMIN\AppData\Local\Programs\Ollama` & change it to `/path/to/Ollama/ here, you go, now your whole OLLAMA is in different location/drive you'd like

GiteaMirror commented

@ChanduTadanki commented on GitHub (Mar 5, 2025):

For those the custom path is not considered even after adding OLLAMA_MODELS environment variable and restarting the Terminal. Try restarting the OS once, then it is working. Might be the environment variables are stored in memory of the running Ollama process.

This worked for me. Thanks.

@ChanduTadanki commented on GitHub (Mar 5, 2025): > For those the custom path is not considered even after adding OLLAMA_MODELS environment variable and restarting the Terminal. Try restarting the OS once, then it is working. Might be the environment variables are stored in memory of the running Ollama process. This worked for me. Thanks.

GiteaMirror commented

@buffos commented on GitHub (Mar 22, 2025):

It depends if ollama was installed as system wide or just for the user.
You have two options when you create the Env variables in windows. System and User. Start with the user env, which will probably work and not a system env variable.

@buffos commented on GitHub (Mar 22, 2025): It depends if ollama was installed as system wide or just for the user. You have two options when you create the Env variables in windows. System and User. Start with the user env, which will probably work and not a system env variable.

GiteaMirror commented