[GH-ISSUE #11808] Ollama GUI not working on Windows 10 Pro (22H2) #69894

Open
opened 2026-05-04 19:44:06 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @shrideh on GitHub (Aug 8, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11808

Originally assigned to: @jmorganca on GitHub.

What is the issue?

The Ollama GUI does not launch or work properly on my Windows 10 system. When I try to open it, nothing happens (or it closes immediately without showing the interface).

System Information:

  • Edition: Windows 10 Pro
  • Version: 22H2
  • Installed on: ‎8/‎5/‎2025
  • OS Build: 19045.6093
  • Ollama version: 0.11.4

Steps to Reproduce:

  1. Install Ollama on Windows 10 Pro.
  2. Attempt to open the Ollama GUI.
  3. The application fails to start or display the interface.

Expected Behavior:
The Ollama GUI should launch normally and display its interface.

Additional Context:

  • No error message is displayed.
  • Running as Administrator does not fix the issue.

Relevant log output


OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.11.4

Originally created by @shrideh on GitHub (Aug 8, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11808 Originally assigned to: @jmorganca on GitHub. ### What is the issue? The Ollama GUI does not launch or work properly on my Windows 10 system. When I try to open it, nothing happens (or it closes immediately without showing the interface). **System Information:** * **Edition:** Windows 10 Pro * **Version:** 22H2 * **Installed on:** ‎8/‎5/‎2025 * **OS Build:** 19045.6093 * **Ollama version:** *0.11.4* **Steps to Reproduce:** 1. Install Ollama on Windows 10 Pro. 2. Attempt to open the Ollama GUI. 3. The application fails to start or display the interface. **Expected Behavior:** The Ollama GUI should launch normally and display its interface. **Additional Context:** * No error message is displayed. * Running as Administrator does not fix the issue. ### Relevant log output ```shell ``` ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.11.4
GiteaMirror added the appbug labels 2026-05-04 19:44:06 -05:00
Author
Owner

@jmorganca commented on GitHub (Aug 8, 2025):

Sorry about this, looking into it!

<!-- gh-comment-id:3169448376 --> @jmorganca commented on GitHub (Aug 8, 2025): Sorry about this, looking into it!
Author
Owner

@shrideh commented on GitHub (Aug 11, 2025):

The issue is that msedgewebview2 is not installed by default on the system. For the Ollama user interface to work, it must be installed. A window may appear prompting you to install msedgewebview2; however, if you ignore the installation, the UI will not work and no error message will be shown.

<!-- gh-comment-id:3174812560 --> @shrideh commented on GitHub (Aug 11, 2025): The issue is that **msedgewebview2** is not installed by default on the system. For the Ollama user interface to work, it must be installed. A window may appear prompting you to install **msedgewebview2**; however, if you ignore the installation, the UI will not work and no error message will be shown.
Author
Owner

@SlugFiller commented on GitHub (Dec 24, 2025):

I think the bigger question is why it's a dependency. Not that I'd prefer Electron, but if a GUI uses web technology, I'd rather it popped up a browser (Browser Tamer makes that much less of a pain) pointing at a localhost address than have a dependency on Edge (which just wraps Chromium anyway). An even better option would be a native UI, which Go is more than capable of, but that might be asking for too much.

Barring any of that, this at least needs better documentation, or a visible error message. Push comes to shove, msedgewebview2 is a very quick install via winget. But with no clear clue on what went wrong, one just has to pray to be lucky to stumble onto this issue, and find the comment right above.

<!-- gh-comment-id:3688518229 --> @SlugFiller commented on GitHub (Dec 24, 2025): I think the bigger question is why it's a dependency. Not that I'd prefer Electron, but if a GUI uses web technology, I'd rather it popped up a browser (Browser Tamer makes that much less of a pain) pointing at a localhost address than have a dependency on Edge (which just wraps Chromium anyway). An even better option would be a native UI, which Go is more than capable of, but that might be asking for too much. Barring any of that, this at least needs better documentation, or a visible error message. Push comes to shove, `msedgewebview2` is a very quick install via `winget`. But with no clear clue on what went wrong, one just has to pray to be lucky to stumble onto this issue, and find the comment right above.
Author
Owner

@garylavayou commented on GitHub (Mar 8, 2026):

Maybe add Microsoft.EdgeWebView2Runtime for Ollama.Ollama as a dependency for the winget package. So when we download Ollama with winget download for offline usage, the dependecy can be downloaded at the same time.

<!-- gh-comment-id:4018536533 --> @garylavayou commented on GitHub (Mar 8, 2026): Maybe add `Microsoft.EdgeWebView2Runtime` for `Ollama.Ollama` as a dependency for the winget package. So when we download Ollama with `winget download` for offline usage, the dependecy can be downloaded at the same time.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#69894