Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] EXDEV on MSIX workspace setup (rootfs.vhdx rename fails) - Win32 workaround from #48362 no longer exists, no fix available

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…

Error Message

Claude Desktop on Windows (MSIX install) fails to set up the Cowork/Code workspace with an EXDEV error when renaming rootfs.vhdx from a temp location to its final path inside the MSIX sandbox. The workspace never initialises. This affects both code sessions and Cowork. The error message shown in the app:

Error Messages/Logs

  1. Observe EXDEV error
  2. Observe same EXDEV error — reinstall also fails

Fix Action

Fix / Workaround

This is the same MSIX virtualisation EXDEV pattern documented in #36642, #30584, #38030, and #48362. However, the workaround described in #48362 — switching to the Win32/Squirrel installer — no longer exists. As of April 2026, ClaudeSetup.exe (from claude.ai/download and downloads.claude.ai/releases/win32/ClaudeSetup.exe) is a bootstrapper that downloads and installs the same MSIX package. There is no non-MSIX installer available. This means there is currently no workaround at all for affected users.

Code Example

> EXDEV: cross-device link not permitted, rename 'C:\Users\[user]\AppData\Roaming\Claude\vm_bundles\claudevm.bundle\.wvm-tmp-R4ckjo\rootfs.vhdx' -> 'C:\Users\[user]\AppData\Roaming\Claude\vm_bundles\claudevm.bundle\rootfs.vhdx'
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?

Claude Desktop on Windows (MSIX install) fails to set up the Cowork/Code workspace with an EXDEV error when renaming rootfs.vhdx from a temp location to its final path inside the MSIX sandbox. The workspace never initialises. This affects both code sessions and Cowork.

This is the same MSIX virtualisation EXDEV pattern documented in #36642, #30584, #38030, and #48362. However, the workaround described in #48362 — switching to the Win32/Squirrel installer — no longer exists. As of April 2026, ClaudeSetup.exe (from claude.ai/download and downloads.claude.ai/releases/win32/ClaudeSetup.exe) is a bootstrapper that downloads and installs the same MSIX package. There is no non-MSIX installer available. This means there is currently no workaround at all for affected users.

The error message shown in the app:

EXDEV: cross-device link not permitted, rename 'C:\Users[user]\AppData\Roaming\Claude\vm_bundles\claudevm.bundle.wvm-tmp-R4ckjo\rootfs.vhdx' -> 'C:\Users[user]\AppData\Roaming\Claude\vm_bundles\claudevm.bundle\rootfs.vhdx'

The real (MSIX-virtualised) path for the bundle is:

C:\Users\[user]\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles\claudevm.bundle\

Inspecting this folder shows only a .auto_reinstall_attempted marker file — no rootfs.vhdx was ever successfully placed. Reinstalling the workspace via the in-app option does not help; it detects the marker and silently gives up.

What Should Happen?

The workspace should initialise successfully and rootfs.vhdx should be placed correctly, regardless of install method.

Error Messages/Logs

> EXDEV: cross-device link not permitted, rename 'C:\Users\[user]\AppData\Roaming\Claude\vm_bundles\claudevm.bundle\.wvm-tmp-R4ckjo\rootfs.vhdx' -> 'C:\Users\[user]\AppData\Roaming\Claude\vm_bundles\claudevm.bundle\rootfs.vhdx'

Steps to Reproduce

  1. Install Claude Desktop on Windows using the installer from claude.ai/download (results in MSIX package Claude_[version]_x64__pzs8sxrjxfjjc)
  2. Open the Code or Cowork tab and attempt to set up a workspace
  3. Observe EXDEV error
  4. Attempt in-app workspace reinstall
  5. Observe same EXDEV error — reinstall also fails
  6. Inspect %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles\claudevm.bundle\ — only .auto_reinstall_attempted is present, no rootfs.vhdx

All paths are on C:. No multi-drive setup is involved.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.116 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Issue #48362 documented this same bug and resolved it by switching to the Win32 installer. That option no longer exists — as of April 2026, ClaudeSetup.exe is a thin bootstrapper that installs MSIX regardless. This closes the only known escape hatch, leaving affected users with no resolution.

extent analysis

TL;DR

The EXDEV error when renaming rootfs.vhdx in the MSIX sandbox on Windows can be addressed by investigating alternative installation methods or modifications to the MSIX package to handle file system operations correctly.

Guidance

  1. Investigate MSIX package modifications: Explore possibilities to modify the MSIX package to correctly handle the renaming of rootfs.vhdx within the sandbox, potentially by adjusting file system permissions or using a different approach to file system operations.
  2. Alternative installation methods: Although the Win32/Squirrel installer workaround is no longer available, investigate if there are other installation methods or versions of Claude Desktop that do not rely on MSIX and might avoid the EXDEV error.
  3. File system and permission analysis: Conduct a detailed analysis of the file system and permissions within the MSIX sandbox to understand why the EXDEV error occurs and if there are any workarounds related to file system configuration.
  4. Contact developer support: Reach out to the Claude Desktop development team or support channels for further assistance, as they may have additional insights or upcoming fixes for this issue.

Example

No specific code example is provided due to the nature of the issue being related to MSIX packaging and file system operations rather than a code snippet.

Notes

The solution to this problem may require collaboration with the developers of Claude Desktop or Microsoft to address the underlying issue with MSIX packaging and file system operations. The absence of a non-MSIX installer limits the immediate workarounds.

Recommendation

Apply workaround: Given the current constraints and the fact that switching to a non-MSIX installer is no longer an option, the best course of action is to investigate and apply any potential workarounds related to MSIX package modifications or alternative installation methods that might become available.

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#logging issue#authentication issue#prompt issue#agent setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING