[GH-ISSUE #12057] Blank window when running ollama via GUI (not via CLI) #70066

Open
opened 2026-05-04 20:15:24 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @GAC-Machine on GitHub (Aug 23, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12057

What is the issue?

Just a blank window when trying to run ollama.exe (without using a terminal (ollama > ollama run [model]).

Image

Relevant log output

N/A (where to find it?)

OS

Windows 23H2 22631.5624 (winver in command prompt)

GPU

Intel(R) UHD Graphics 750 (integrated) (Task manager > Perfomance > GPU > [top-right corner])

CPU

11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (Task manager > Perfomance > CPU > [top-right corner])

Ollama version

0.11.6 (ollama -v in command prompt)

Originally created by @GAC-Machine on GitHub (Aug 23, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12057 ### What is the issue? Just a blank window when trying to run `ollama.exe` (without using a terminal (`ollama `> `ollama run [model]`). <img width="1241" height="1290" alt="Image" src="https://github.com/user-attachments/assets/ce690d41-97f3-46ee-96b6-e71c51c1e7f6" /> ### Relevant log output ``` N/A (where to find it?) ``` ### OS Windows 23H2 22631.5624 (`winver` in `command prompt`) ### GPU Intel(R) UHD Graphics 750 (integrated) (`Task manager` > `Perfomance` > `GPU` > `[top-right corner]`) ### CPU 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (`Task manager` > `Perfomance` > `CPU` > `[top-right corner]`) ### Ollama version 0.11.6 (`ollama -v` in `command prompt`)
GiteaMirror added the bug label 2026-05-04 20:15:24 -05:00
Author
Owner

@rgw87 commented on GitHub (Oct 9, 2025):

I encountered the same issue. After testing, it may be related to the Exploit Protection Settings. My system version is WIN10 PRO 22H2 19045.6396. In Windows Settings → Update & Security → Windows Security → App & Browser Control → Exploit Protection Settings → Program Settings → Add Program to Customize, add msedgewebview2.exe, locate "Hardware-enforced stack protection," select "Override system settings," ensure its status is set to "Off," and leave the other two checkboxes unchecked. The GUI will then display properly.

Based on my past experience, this setting can also prevent 64-bit Chromium-based browsers (such as Chrome and Edge) from functioning correctly. The browser may fail to connect to the internet, and system logs may report errors related to ws2_32.dll. However, after overriding the default settings for programs like chrome.exe and msedge.exe using the method described above, the issue is resolved.

<!-- gh-comment-id:3385701384 --> @rgw87 commented on GitHub (Oct 9, 2025): I encountered the same issue. After testing, it may be related to the Exploit Protection Settings. My system version is WIN10 PRO 22H2 19045.6396. In Windows Settings → Update & Security → Windows Security → App & Browser Control → Exploit Protection Settings → Program Settings → Add Program to Customize, add msedgewebview2.exe, locate "Hardware-enforced stack protection," select "Override system settings," ensure its status is set to "Off," and leave the other two checkboxes unchecked. The GUI will then display properly. Based on my past experience, this setting can also prevent 64-bit Chromium-based browsers (such as Chrome and Edge) from functioning correctly. The browser may fail to connect to the internet, and system logs may report errors related to ws2_32.dll. However, after overriding the default settings for programs like chrome.exe and msedge.exe using the method described above, the issue is resolved.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#70066