Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork VM fails to start on Windows - MSIX path mismatch between VM file location and VM service lookup path [2 comments, 2 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#52540•Fetched 2026-04-24 06:04:27
View on GitHub
Comments
2
Participants
2
Timeline
8
Reactions
0
Author
comyerscomyers
Participants
comyerscomyersgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×5commented ×2closed ×1

Error Message

Error: HCS operation failed: failed to create compute system: Error: failed to set VHDX path: VHDX file not found: Error: path ...vm_bundles is a symlink or junction, refusing to open

Error Messages/Logs

Fix Action

Fix / Workaround

Symlink workaround is blocked by Claude itself: Error: path ...vm_bundles is a symlink or junction, refusing to open

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?

On Windows, Claude Cowork VM fails to start due to a path mismatch between where VM bundle files are written and where the VM service expects to find them. This affects multiple users across different hardware on the same MSIX version (1.3883.0.0).

Two distinct failure patterns observed:

Pattern 1 - Fresh MSIX install: VM files download to MSIX virtualized path: C:\Users<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles\claudevm.bundle\

But VM service boots from: C:\Users<user>\AppData\Roaming\Claude\vm_bundles\claudevm.bundle\

Error: HCS operation failed: failed to create compute system: HcsWaitForOperationResult failed with HRESULT 0x80070569

Pattern 2 - Previous Squirrel install upgraded to MSIX: VM files exist at traditional Roaming path but VM service looks for rootfs.vhdx at the MSIX Local Packages path.

Error: failed to set VHDX path: VHDX file not found: C:\Users<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles\claudevm.bundle\rootfs.vhdx

Symlink workaround is blocked by Claude itself: Error: path ...vm_bundles is a symlink or junction, refusing to open

  • OS: Windows 11, Intune-managed
  • Claude version: 1.3883.0.0 (MSIX from claude.ai/download)
  • Hardware: Multiple models affected (HP Elite x360 G11, Microsoft Surface)
  • Virtual Machine Platform: Enabled
  • HCS Services: Running (hns, vmcompute)

What Should Happen?

Cowork VM starts successfully regardless of whether machine had a previous Squirrel install or is a fresh MSIX install.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

  1. Install Claude 1.3883.0.0 MSIX on Windows 11
  2. Open Claude and click the Cowork tab
  3. Observe VM fails to start

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

Claude 1.3883.0 (93ff6c) 2026-04-21T17:24:01.000Z

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

extent analysis

TL;DR

The most likely fix is to ensure the VM bundle files are written to and read from the same path, either by configuring the VM service to use the MSIX virtualized path or by moving the VM files to the traditional Roaming path.

Guidance

  • Verify the paths where VM bundle files are written and where the VM service expects to find them to identify any mismatches.
  • Consider configuring the VM service to use the MSIX virtualized path (C:\Users\<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles\) if the VM files are written to this location.
  • If the VM files exist at the traditional Roaming path (C:\Users\<user>\AppData\Roaming\Claude\vm_bundles\), consider moving them to the MSIX Local Packages path to match the VM service's expected location.
  • Investigate why the symlink workaround is blocked by Claude itself and explore alternative solutions to resolve the path mismatch issue.

Notes

The issue seems to be related to the transition from Squirrel to MSIX installation, and the different paths used by the VM service and the VM bundle files. The solution may involve configuring the VM service or moving the VM files to a consistent location.

Recommendation

Apply a workaround to ensure the VM bundle files are written to and read from the same path, as the root cause of the issue is a path mismatch between the VM service and the VM bundle files.

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#vector store#embedding generation#cache error#file not found

Still need to ship something?

×6

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

Back to top recommendations

TRENDING