Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork workspace fails to start — CoworkVMService cannot create named pipe due to WIN32_PACKAGED_PROCESS sandbox restrictions [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48468•Fetched 2026-04-16 06:59:18
View on GitHub
Comments
1
Participants
1
Timeline
6
Reactions
0
Author
RussellTaylor83RussellTaylor83
Participants
RussellTaylor83RussellTaylor83
Timeline (top)
labeled ×5commented ×1

Error Message

C:\ProgramData\Claude\Logs\cowork-service.log:

Warning: failed to open service for recovery config: Access is denied. [Server] Starting named pipe server on \.\pipe\cowork-vm-service Service error: failed to start server: failed to create named pipe: open \.\pipe\cowork-vm-service: Access is denied.

Root Cause

Root cause (diagnosed)

Fix Action

Fix / Workaround

Attempted mitigations

Code Example

SERVICE_NAME: CoworkVMService
TYPE         : 210  WIN32_PACKAGED_PROCESS
START_TYPE   : 2    AUTO_START
SERVICE_START_NAME: LocalSystem
BINARY_PATH  : C:\Program Files\WindowsApps\Claude_1.2581.0.0_x64__pzs8sxrjxfjjc\app\resources\cowork-svc.exe

---

C:\ProgramData\Claude\Logs\cowork-service.log:

Warning: failed to open service for recovery config: Access is denied.
[Server] Starting named pipe server on \\.\pipe\cowork-vm-service
Service error: failed to start server: failed to create named pipe:
  open \\.\pipe\cowork-vm-service: Access is denied.

---
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

Environment

FieldValue
Claude version1.2581.0.0
Install methodMSIX package via .exe installer (sideloaded, SignatureKind: Developer)
Install pathC:\Program Files\WindowsApps\Claude_1.2581.0.0_x64__pzs8sxrjxfjjc\
OSWindows 11 (Hyper-V enabled)
Hyper-VEnabled, vmms running, user in Hyper-V Administrators group

Steps to reproduce

  1. Install Claude Desktop via the .exe installer from claude.ai/download
  2. Launch Claude Desktop
  3. Attempt to create or start a Cowork workspace

Expected behaviour

Workspace starts successfully and CoworkVMService creates the named pipe \\.\pipe\cowork-vm-service.

Actual behaviour

Two errors occur in sequence:

  1. Claude Desktop shows: connect EPERM \\.\pipe\cowork-vm-service
  2. After running as administrator, the pipe error is bypassed but workspace setup times out with: Failed to start Claude's workspace — Request timed out: configure

Root cause (diagnosed)

CoworkVMService is registered as TYPE: 210 WIN32_PACKAGED_PROCESS, which inherits MSIX AppContainer sandbox restrictions. This prevents the service from creating a named pipe even when running as LocalSystem.

A standard WIN32_OWN_PROCESS service type would not have this restriction. No Hyper-V VMs are ever created — the service fails before reaching that stage.

Service configuration

SERVICE_NAME: CoworkVMService
TYPE         : 210  WIN32_PACKAGED_PROCESS
START_TYPE   : 2    AUTO_START
SERVICE_START_NAME: LocalSystem
BINARY_PATH  : C:\Program Files\WindowsApps\Claude_1.2581.0.0_x64__pzs8sxrjxfjjc\app\resources\cowork-svc.exe

Relevant log output

C:\ProgramData\Claude\Logs\cowork-service.log:

Warning: failed to open service for recovery config: Access is denied.
[Server] Starting named pipe server on \\.\pipe\cowork-vm-service
Service error: failed to start server: failed to create named pipe:
  open \\.\pipe\cowork-vm-service: Access is denied.

Attempted mitigations

  • Reinstalled Claude Desktop (multiple times) — no change
  • Deleted all local data (%LocalAppData%\Claude, C:\ProgramData\Claude) and reinstalled — no change
  • Verified user is in Hyper-V Administrators group (enabled, mandatory)
  • Verified vmms service is running
  • Running Claude as administrator — bypasses initial pipe error but workspace configure times out

Suggested fix

Register CoworkVMService as WIN32_OWN_PROCESS rather than WIN32_PACKAGED_PROCESS, or explicitly grant the MSIX AppContainer identity permission to create named pipes.

What Should Happen?

Workspace starts successfully and CoworkVMService creates the named pipe \\.\pipe\cowork-vm-service.

Error Messages/Logs

Steps to Reproduce

  1. Install Claude Desktop via the .exe installer from claude.ai/download
  2. Launch Claude Desktop
  3. Attempt to create or start a Cowork workspace

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

1.2581.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

No response

extent analysis

TL;DR

Register CoworkVMService as WIN32_OWN_PROCESS or grant the MSIX AppContainer identity permission to create named pipes to resolve the issue.

Guidance

  • Verify that the CoworkVMService is indeed registered as WIN32_PACKAGED_PROCESS and that this is the cause of the named pipe creation failure.
  • Consider registering CoworkVMService as WIN32_OWN_PROCESS to remove MSIX AppContainer sandbox restrictions.
  • Alternatively, explore granting the MSIX AppContainer identity explicit permission to create named pipes as a potential workaround.
  • Review the service configuration and log output to ensure that the issue is isolated to the named pipe creation.

Example

No code snippet is provided as the issue is related to service configuration and permissions.

Notes

The suggested fix requires administrative privileges and modifications to the service configuration. It is essential to test and verify the changes to ensure they resolve the issue without introducing new problems.

Recommendation

Apply the workaround by registering CoworkVMService as WIN32_OWN_PROCESS or granting the necessary permissions, as upgrading to a fixed version is not mentioned as an option in the issue. This approach directly addresses the identified root cause and may provide a more immediate solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#autograd error#model save/load#optimization#mixed precision

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING