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

[GH-ISSUE #13473] In windows11, after updating Ollama from 0.13.2 to 0.13.3, the select model drop-down is stuck on "Loading". #70950

New Issue
Closed
opened 2026-05-04 23:33:21 -05:00 by GiteaMirror · 13 comments
GiteaMirror commented 2026-05-04 23:33:21 -05:00
Owner
Copy Link

Originally created by @kvacha13 on GitHub (Dec 14, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/13473

Originally assigned to: @hoyyeva on GitHub.

What is the issue?

in Windows 11, after updating Ollama from 0.13.2 to 0.13.3, the select model drop-down is stuck on "Loading". I even tried updating to 0.13.4, but the same result. Only the working version is 0.13.2.
Image

Relevant log output

OS

Windows

GPU

Intel

CPU

Intel

Ollama version

0.13.3

Originally created by @kvacha13 on GitHub (Dec 14, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/13473 Originally assigned to: @hoyyeva on GitHub. ### What is the issue? in Windows 11, after updating Ollama from 0.13.2 to 0.13.3, the select model drop-down is stuck on "Loading". I even tried updating to 0.13.4, but the same result. Only the working version is 0.13.2. <img width="992" height="688" alt="Image" src="https://github.com/user-attachments/assets/db75a113-c86c-4053-bbfd-1854269fbe73" /> ### Relevant log output ```shell ``` ### OS Windows ### GPU Intel ### CPU Intel ### Ollama version 0.13.3
GiteaMirror added the appbug labels 2026-05-04 23:33:22 -05:00
GiteaMirror commented 2026-05-04 23:33:26 -05:00
Author
Owner
Copy Link

@jjatem commented on GitHub (Dec 14, 2025):

The same issue is exactly happening while upgrading to version 0.13.3 on Mac. Thanks for reporting. I was only able to fix by downgrading to version 0.13.1.

<!-- gh-comment-id:3651567663 --> @jjatem commented on GitHub (Dec 14, 2025): The same issue is exactly happening while upgrading to version 0.13.3 on Mac. Thanks for reporting. I was only able to fix by downgrading to version 0.13.1.
GiteaMirror commented 2026-05-04 23:33:28 -05:00
Author
Owner
Copy Link

@jay875037671 commented on GitHub (Dec 15, 2025):

1.3.4-rc same,and when I tried to login in settings,it went “Failed to get connect URL”

<!-- gh-comment-id:3652551342 --> @jay875037671 commented on GitHub (Dec 15, 2025): 1.3.4-rc same,and when I tried to login in settings,it went “Failed to get connect URL”
GiteaMirror commented 2026-05-04 23:33:32 -05:00
Author
Owner
Copy Link

@snottyone commented on GitHub (Dec 15, 2025):

same problem on windows since last update

<!-- gh-comment-id:3653423583 --> @snottyone commented on GitHub (Dec 15, 2025): same problem on windows since last update
GiteaMirror commented 2026-05-04 23:33:35 -05:00
Author
Owner
Copy Link

@AlexMultiAgent commented on GitHub (Dec 15, 2025):

I encountered the same issue on Windows 11. It’s worth mentioning that the model files are not stored in the default folder .ollama\models—so I wonder if this is the cause. On another computer, where the models are stored in the default folder, the test worked without any problems.

<!-- gh-comment-id:3653615402 --> @AlexMultiAgent commented on GitHub (Dec 15, 2025): I encountered the same issue on Windows 11. It’s worth mentioning that the model files are not stored in the default folder .ollama\models—so I wonder if this is the cause. On another computer, where the models are stored in the default folder, the test worked without any problems.
GiteaMirror commented 2026-05-04 23:33:38 -05:00
Author
Owner
Copy Link

@snottyone commented on GitHub (Dec 15, 2025):

I encountered the same issue on Windows 11. It’s worth mentioning that the model files are not stored in the default folder .ollama\models—so I wonder if this is the cause. On another computer, where the models are stored in the default folder, the test worked without any problems.

i have the models in
C:\Users\(me)\.ollama\models
which i assume is default, and have the issue (win10)

<!-- gh-comment-id:3654119925 --> @snottyone commented on GitHub (Dec 15, 2025): > I encountered the same issue on Windows 11. It’s worth mentioning that the model files are not stored in the default folder .ollama\models—so I wonder if this is the cause. On another computer, where the models are stored in the default folder, the test worked without any problems. i have the models in C:\Users\\(me)\\.ollama\models which i assume is default, and have the issue (win10)
GiteaMirror commented 2026-05-04 23:33:43 -05:00
Author
Owner
Copy Link

@marcorotondi commented on GitHub (Dec 15, 2025):

Some for me!

And with login form after insert username and password no verification code is sent to my mail

<!-- gh-comment-id:3654338070 --> @marcorotondi commented on GitHub (Dec 15, 2025): Some for me! And with login form after insert username and password no verification code is sent to my mail
GiteaMirror commented 2026-05-04 23:33:49 -05:00
Author
Owner
Copy Link

@kvacha13 commented on GitHub (Dec 15, 2025):

The problem seems to be with the GUI side, as both 0.133 and 0.13.4 versions run OK from a terminal.

<!-- gh-comment-id:3654360344 --> @kvacha13 commented on GitHub (Dec 15, 2025): The problem seems to be with the GUI side, as both 0.133 and 0.13.4 versions run OK from a terminal.
GiteaMirror commented 2026-05-04 23:33:53 -05:00
Author
Owner
Copy Link

@snottyone commented on GitHub (Dec 15, 2025):

The problem seems to be with the GUI side, as both 0.133 and 0.13.4 versions run OK from a terminal.

indeed, i can access models remotely etc, just the GUI is borked

<!-- gh-comment-id:3654477695 --> @snottyone commented on GitHub (Dec 15, 2025): > The problem seems to be with the GUI side, as both 0.133 and 0.13.4 versions run OK from a terminal. indeed, i can access models remotely etc, just the GUI is borked
GiteaMirror commented 2026-05-04 23:33:55 -05:00
Author
Owner
Copy Link

@ManzDev commented on GitHub (Dec 15, 2025):

Same problem here

<!-- gh-comment-id:3656066822 --> @ManzDev commented on GitHub (Dec 15, 2025): Same problem here
GiteaMirror commented 2026-05-04 23:33:57 -05:00
Author
Owner
Copy Link

@snottyone commented on GitHub (Dec 16, 2025):

fix works, thank you!

<!-- gh-comment-id:3659155908 --> @snottyone commented on GitHub (Dec 16, 2025): fix works, thank you!
GiteaMirror commented 2026-05-04 23:33:58 -05:00
Author
Owner
Copy Link

@kvacha13 commented on GitHub (Dec 16, 2025):

Confirming fix (tested on version 0.13.4). Thank you.

<!-- gh-comment-id:3659232289 --> @kvacha13 commented on GitHub (Dec 16, 2025): Confirming fix (tested on version 0.13.4). Thank you.
GiteaMirror commented 2026-05-04 23:33:59 -05:00
Author
Owner
Copy Link

@jjatem commented on GitHub (Dec 18, 2025):

Confirming fix (tested on Mac version 0.13.4). Thank you.

<!-- gh-comment-id:3667908085 --> @jjatem commented on GitHub (Dec 18, 2025): Confirming fix (tested on Mac version 0.13.4). Thank you.
GiteaMirror commented 2026-05-04 23:34:00 -05:00
Author
Owner
Copy Link

@hoyyeva commented on GitHub (Jan 5, 2026):

Yay! Thank you for confirming it! I'll close the issue for now. Please feel free to reopen if it's still happening.

<!-- gh-comment-id:3711470871 --> @hoyyeva commented on GitHub (Jan 5, 2026): Yay! Thank you for confirming it! I'll close the issue for now. Please feel free to reopen if it's still happening.
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 app bug
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#70950
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?