Hermes Agent Windows support now comes in two parts: a signed desktop app shipped as an MSIX package for Windows 11 22H2 or newer, and a command-line install that runs natively on Windows 10 and 11 or inside WSL2. Since Hermes Agent v0.22.0, published on GitHub on 14 October 2026, the old NSIS and MSI desktop installers are gone.
📺 Watch: Hermes Agent V0.22 Just Changed AI Agents Forever!
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
That change trips people up. Old guides tell you to grab an .exe and click Next. That's not how it works anymore. Here's what changed, which install route fits your PC, how the CLI behaves on Windows, what the local-model fixes mean for your laptop, and how to fix the problems people actually hit.
What changed for Hermes on Windows in v0.22
Nous Research calls v0.22.0 "The Threshold Release", and a big part of it is packaging. Per the release notes, the desktop app is now a sealed, signed package that carries its own Python and Node and updates itself, so first launch builds nothing. On Windows that package is a signed MSIX for both x64 and ARM64, delivered through App Installer or the Microsoft Store.
The breaking-changes list is blunt about it: the Windows desktop is MSIX-only, it needs Windows 11 22H2 or newer, and the NSIS and MSI installers are gone. If you're on Windows 10, the desktop package isn't for you. The command-line install still is.
A few smaller Windows wins landed in the same release:
- Faster startup on Windows, per the desktop notes.
- Updates that finish while the old runtime is still in use, so a running Hermes doesn't block an upgrade.
- Install scripts that handle Windows 10 and Unicode Windows paths, so a user folder with non-English characters no longer breaks setup.
- Packaged installs work end to end: the agent's own terminal can run hermes, and plugins that need Python dependencies install inside the MSIX.
If you want someone to walk you through the whole thing on a call, the AI Profit Boardroom ($69/mo) has the Agent OS, a 30-day AI agent roadmap, daily tutorials as new tools drop, 4 coaching calls a week and the prompt library. 3,400+ members are in there.
📺 Watch: Hermes3D Is INSANE: AI Agents Now Have a 3D Office
Hermes Agent Windows install options compared
There are four supported ways to get Hermes onto a Windows machine. Pick based on your Windows version and whether you want the desktop app.
| Route | What you get | Windows version | How it updates |
|---|---|---|---|
| MSIX via App Installer | Signed desktop app with bundled Python, Node and CLI aliases | Windows 11 22H2 or newer (x64 or ARM64) | The app's Update control and Windows App Installer |
| Microsoft Store | The same desktop app under a Store identity | Windows 11 22H2 or newer | Microsoft Store updates |
| Native CLI (install.ps1) | Hermes CLI, TUI and gateway, no WSL needed | Windows 10 or 11 | hermes update |
| WSL2 (install.sh) | Hermes inside a Linux VM, same as Ubuntu | Windows 10 22H2+ or Windows 11 with WSL2 | hermes update inside WSL |
Install the desktop app (MSIX)
Download the Windows package from the Hermes website, then open the .appinstaller file with Windows App Installer. The installation docs say it installs the signed MSIX bundle and records the update source, so future updates come from the same place.
The Store version is the same app with separate Store ownership. It updates through the Store and doesn't use the sideload feed. Pick one and stick with it.
The MSIX gives you three command aliases: hermes, hermes-agent and hermes-acp. So after installing the desktop app you can open PowerShell and type hermes straight away. For a click-by-click desktop walkthrough, my Hermes Desktop installation guide covers the first-run screens.
Not sure whether you even need the desktop app? Book a free AI strategy session and we'll work out the right setup for you.
One warning from the docs: Hermes-Setup.exe is a different thing. It's a bootstrap installer that builds a source checkout. Don't confuse it with the self-contained MSIX.
Install the CLI natively on Windows
Open PowerShell or Windows Terminal and run:
iex (irm https://hermes-agent.nousresearch.com/install.ps1)
No admin rights needed. The installer puts Hermes in a hermes folder under %LOCALAPPDATA% and adds hermes to your User PATH. Open a new terminal when it finishes, then run hermes to start chatting. Want the desktop app later? The docs say to run hermes desktop after a CLI-only install.
📺 Watch: Hermes AI Agents Just Went Portable
WSL vs native: which CLI should you run?
The docs say Hermes now supports both. Native is fine for most people. Chat, the messaging gateway, the cron scheduler, the browser tool, MCP servers and local model servers all run natively on Windows. On native Windows, Hermes runs shell commands through Git Bash, the same approach Claude Code takes.
The WSL2 guide says to pick WSL2 when:
- You do POSIX-heavy development work and want Hermes to share the same filesystem and paths as your Linux dev tools.
- You already have a WSL2 setup and don't want to maintain a second install.
For WSL2, run wsl --install from an admin PowerShell, reboot, then check wsl --list --verbose shows VERSION 2. The docs say Hermes doesn't work reliably on WSL1. Inside your Ubuntu shell, run:
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
Then source ~/.bashrc and type hermes. The installer treats WSL2 as plain Linux.
Both can live on one PC. Native data sits under %LOCALAPPDATA%, WSL data sits in ~/.hermes inside Linux. Just remember they're two separate agents with separate memory.
Running local models on Windows
v0.22 added one-click local models, and Windows is a first-class target. Go to Settings, then Providers, then Local Models in the desktop app. On Windows the managed engine runs on CUDA for supported NVIDIA cards, Vulkan on x64, or CPU. The full walkthrough of that feature is in my Hermes llama.cpp guide.
Three Windows-specific fixes matter here:
- v0.22.0: the managed llama-server no longer crashes on Windows with error 0xC0000374, and it no longer inherits your credentials.
- v0.22.0: Windows local-model servers are contained, and orphaned servers are recovered safely.
- v0.22.2 (15 October): on Windows unified-memory machines, model launch and the prompt cache are sized to free memory. The same patch made local requests stream with prompt-reading progress, made stall timers skip time the machine was asleep, and stopped compression timing out on long conversations.
That last one is the laptop fix. Close the lid mid-task, open it again, and the turn doesn't die on a stall timer.
Not sure local or cloud is right for your work? Grab a free AI strategy session and we'll look at your hardware and use case together.
Common Hermes Windows problems and fixes
These all come from the Windows docs.
The desktop package won't install
Check your Windows version. The MSIX needs Windows 11 22H2 or later. The docs are clear that Windows 10 support for the CLI script doesn't mean the MSIX supports Windows 10. On Windows 10, use the native CLI or WSL2 instead.
hermes: command not found after installing
Open a new PowerShell window. The installer added Hermes to your User PATH, but terminals that were already open don't see it.
The wrong hermes runs
If you have both the MSIX and a CLI install, one can shadow the other. Run Get-Command hermes -All to see every copy. You can turn the MSIX aliases on or off in Windows Settings under Apps, Advanced app settings, App execution aliases.
Strange characters show as question marks
Your console host doesn't support UTF-8. The docs say switch to Windows Terminal, which comes with Windows 11.
The gateway won't stay running
Run hermes gateway status. It shows the scheduled task, any Startup-folder entry and the live process in one view. Group policy can block logon triggers. To run the gateway at login with no admin rights, use hermes gateway install.
Features missing on ARM64
Native Windows ARM64 skips a few optional parts: the Google Chat SDK extra, the openWakeWord engine and local Faster-Whisper speech-to-text. The bundled Chromium is the x64 build running under emulation. If desktop window context fails on ARM64, the docs suggest the x64 desktop build under emulation.
And one thing not to do: the docs say never disable Windows security controls to work around a packaged-app error. Use the package's own launcher instead.
Once Hermes is running, the Agent OS guide shows how to turn it into a full system, and Goldie Bench helps you pick a model that handles real agent work. Want to run separate agents for coding and personal tasks on the same PC? Read my guide to Hermes multiple profiles.
FAQ
Does Hermes Agent work on Windows 10?
Yes, through the command-line installer or WSL2. The signed desktop MSIX needs Windows 11 22H2 or newer.
Is there still a Hermes .exe or .msi installer?
No. The v0.22.0 notes say the NSIS and MSI installers are gone. The desktop app ships as a signed MSIX through App Installer or the Microsoft Store.
How do I update Hermes on Windows?
A Store install updates through the Store. A sideloaded MSIX uses the app's Update control. A CLI install uses hermes update.
How do I uninstall the Windows desktop app?
Go to Windows Settings, then Apps, then Installed apps. For a CLI install, the docs say run hermes uninstall and check hermes uninstall --dry-run first.
Want Hermes set up right on your Windows machine the first time? Join the AI Profit Boardroom for the Agent OS and step-by-step tutorials, or book a free AI strategy session and we'll map out your setup.
