.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
You install Hermes Desktop on a Windows machine with an NVIDIA GPU. The app launches, the window opens. What you see: a blank white pane, a flashing display, or sometimes the app crashes before the window even renders. Known interaction between Electron's GPU sandbox and certain NVIDIA driver versions on Windows.
The fix is one environment variable. Below is the setup that works on every machine I've helped someone debug this on.
Quick fix: set HERMES_DESKTOP_NO_SANDBOX
Set HERMES_DESKTOP_NO_SANDBOX=1 as a Windows user environment variable, then relaunch Hermes Desktop.
Through PowerShell (persistent)
[Environment]::SetEnvironmentVariable("HERMES_DESKTOP_NO_SANDBOX", "1", "User")
# close Hermes Desktop completely, then reopenThrough System Properties GUI
- Press Win+R, type
sysdm.cpl, press Enter - Advanced tab, Environment Variables button
- Under User variables, click New
- Variable name: HERMES_DESKTOP_NO_SANDBOX
- Variable value: 1
- OK out of all dialogs
- Restart Hermes Desktop
The app opens cleanly after that on every affected machine I've tested.
Why this fix works
Electron 39 (which Hermes Desktop v0.3.7 uses) ships with a renderer sandbox that isolates GPU operations. On Windows the sandbox interacts with NVIDIA's graphics pipeline through driver shims. Those shims have changed in subtle ways across the past two years of driver releases.
On affected combinations the sandbox can't establish a GPU context. The renderer either gets no surface to draw on (blank window), gets a corrupted surface (flashing) or dies before any surface is ready (crash).
HERMES_DESKTOP_NO_SANDBOX=1 tells Electron to skip the renderer sandbox. GPU context is established without the shim layer that was breaking. Trade-off: slightly larger attack surface inside the renderer process. For a desktop app running on your machine the practical security impact is small.
Community fix repository at the fathah/hermes-desktop issues page tracks this.
If the env var doesn't fix it....
Update NVIDIA drivers
Switch to the "Studio" driver branch through GeForce Experience, or download from NVIDIA's driver page. Studio drivers have fewer GPU pipeline regressions than Game Ready drivers for desktop apps. Reboot after install.
Force the discrete GPU
On laptops with both integrated and discrete GPUs, Windows might be handing Electron the integrated one. Right-click Hermes Desktop shortcut, Run with graphics processor, High-performance NVIDIA processor.
If that fixes it, make it permanent through NVIDIA Control Panel: Manage 3D Settings > Program Settings tab > add Hermes Desktop > set Preferred graphics processor to High-performance NVIDIA processor.
Or force the integrated GPU instead
Sometimes the opposite works. Same Control Panel path, but pick Integrated graphics. The integrated path works while NVIDIA path is broken. Acceptable workaround if you're not doing GPU-heavy work in Hermes (which most people aren't).
Disable GPU acceleration entirely (fallback)
If neither of those work and you need the app open right now, disable GPU acceleration completely:
[Environment]::SetEnvironmentVariable("HERMES_DESKTOP_DISABLE_GPU", "1", "User")The app uses software rendering. Performance is worse (you'll feel it on scrolling and animations) but it works. Treat this as a temporary fix while sorting the GPU properly. Don't leave software rendering on long-term.
Linux and WSL2 equivalents
Same Electron sandbox issue occurs on Linux with some Mesa driver combinations and on WSL2 with WSLg GPU passthrough. Same fix:
export HERMES_DESKTOP_NO_SANDBOX=1
# or for software rendering:
export HERMES_DESKTOP_DISABLE_GPU=1
# add to ~/.bashrc to persistThe Windows path is where most reports come from because affected NVIDIA driver combinations are most common there.
Confirming you have this specific bug
Open Hermes Desktop. Three possible outcomes:
- Workspace UI shows (chat, sidebar, providers): GPU is fine, not this bug
- White pane that never resolves OR window that flickers: yes, you hit this bug
- App crashes before window appears: probably this bug, check Event Viewer for confirmation
Check Event Viewer for crash details
Windows Logs > Application > look for Hermes Desktop or Electron entries. A crash in nvoglv64.dll is NVIDIA pipeline failing. A crash in libGLESv2.dll is similar. Either confirms the env var fix should help.
Crash in something completely different: separate bug, env var fix won't help. Check the project issue tracker.
When to give up on Desktop and switch paths
If you tried the env var, the driver update, both GPU options and software rendering and the app still doesn't work, your time's better spent on a different access path than further GPU debugging.
Use WebUI instead
The community Hermes WebUI runs in a browser, so it doesn't touch local GPU at all. Works on any machine including ones where Desktop refuses to start.
Use WSL2 CLI instead
Terminal-only path. See our Windows comparison. Not what most Desktop users want but it works.
What about Mac?
macOS has its own occasional GPU edge cases (mostly during the M1 transition era) but the NVIDIA Windows issue is a PC-specific thing. If you hit a blank-window or crash on Mac, look for Apple Silicon-specific bugs rather than these env vars. Different fix.
Hybrid pattern still works around the issue
If your laptop is the one with the GPU issue and the agent is on a VPS, the broken Desktop doesn't block you. Keep the agent running via whichever access path works (WebUI, CLI through SSH, Desktop on a different machine) and come back to Desktop after a driver update.
Our Hermes Desktop remote backend over VPS tutorial covers the hybrid setup.
Upstream fix in progress
The Electron sandbox interaction with NVIDIA drivers is being worked on at the Electron level. Future Electron releases handle broken combinations more gracefully. Hermes Desktop inherits the fix when it updates its Electron base. Until then, the env var is the working workaround.
Hosting the agent reliably regardless of laptop quirks
Of all the Hermes parts, Desktop is the most platform-fragile because it has to live with whatever GPU drivers and OS quirks your laptop has. The agent itself runs cleanly on Linux. Running it on a VPS keeps the brain stable while you debug the GUI on the laptop. The LumaDock Hermes Agent template gives you that VPS preinstalled. Unmetered bandwidth, no setup fees. Setup details in our Hermes Agent complete guide.
