[BUG] spawn EPERM

Resolved 💬 1 comment Opened Apr 15, 2026 by ComodoMelih Closed May 25, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Title: spawn EPERM error on Windows when starting local sessions in Claude Code desktop app
Environment:

OS: Windows 10 (10.0.19045.6456)
Claude Code desktop app version: 2.1.108
Claude CLI version: 2.1.108 (native install at C:\Users\admin\.local\bin\claude.exe)
Install method: Native (via irm https://claude.ai/install.ps1 | iex)

Description:
The Claude Code desktop app fails to start any local session with spawn EPERM. The error appears immediately when clicking Local or selecting any local folder. The CLI itself works perfectly fine when launched directly from PowerShell.
Steps to reproduce:

Install Claude Code desktop app on Windows 10
Open the app and click "New session"
Select "Local" or any local folder
See spawn EPERM error immediately

Expected behavior:
Local session starts successfully.
Actual behavior:
spawn EPERM error, session never starts.
Additional context:

CLI works fine in terminal: claude launches successfully as Opus 4.6 (1M context) · Claude Max
SSH remote sessions also fail with Claude Code process exited with code 1 and Unauthorized: invalid or missing auth token
Previously worked on an older version of the desktop app
Tried: reinstalling, removing Store version, adding PATH entries, setting CLAUDE_CODE_BIN env var, SHELL and ComSpec env vars — none resolved the issue
/doctor shows: Currently running: native (2.1.108), Stable version: 2.1.92
Downgrading to stable (2.1.92) may resolve — unable to test as install script doesn't accept --channel stable flag on Windows

What Should Happen?

Title: spawn EPERM error on Windows when starting local sessions in Claude Code desktop app
Environment:

OS: Windows 10 (10.0.19045.6456)
Claude Code desktop app version: 2.1.108
Claude CLI version: 2.1.108 (native install at C:\Users\admin\.local\bin\claude.exe)
Install method: Native (via irm https://claude.ai/install.ps1 | iex)

Description:
The Claude Code desktop app fails to start any local session with spawn EPERM. The error appears immediately when clicking Local or selecting any local folder. The CLI itself works perfectly fine when launched directly from PowerShell.
Steps to reproduce:

Install Claude Code desktop app on Windows 10
Open the app and click "New session"
Select "Local" or any local folder
See spawn EPERM error immediately

Expected behavior:
Local session starts successfully.
Actual behavior:
spawn EPERM error, session never starts.
Additional context:

CLI works fine in terminal: claude launches successfully as Opus 4.6 (1M context) · Claude Max
SSH remote sessions also fail with Claude Code process exited with code 1 and Unauthorized: invalid or missing auth token
Previously worked on an older version of the desktop app
Tried: reinstalling, removing Store version, adding PATH entries, setting CLAUDE_CODE_BIN env var, SHELL and ComSpec env vars — none resolved the issue
/doctor shows: Currently running: native (2.1.108), Stable version: 2.1.92
Downgrading to stable (2.1.92) may resolve — unable to test as install script doesn't accept --channel stable flag on Windows

Error Messages/Logs

Steps to Reproduce

just run and type anything

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.108

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

<img width="875" height="183" alt="Image" src="https://github.com/user-attachments/assets/50eedaae-4e95-4346-909b-6fa203fc76ca" />

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗