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

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?

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.