Preflight Checklist
What's Wrong?
[BUG] Cowork Windows - sandbox-helper fails to mount host share (virtiofs/Plan9) with OneDrive-synced folders
Preflight Checklist
What's Wrong?
Cowork fails at VM startup with a sandbox mount error. The workspace never reaches API connection; it crashes during the host-share mounting phase. My working directories are stored on OneDrive, which may be the root cause since OneDrive uses the Windows Cloud Files API (placeholder/dehydrated files) rather than standard NTFS file access.
Error output:
CLI output was not valid JSON. This may indicate an error during startup.
Output: sandbox-helper: failed to unmount host share (tried both virtiofs and Plan9): invalid argument
The sandbox-helper attempts both virtiofs and Plan 9 (9p) filesystem protocols to mount the shared folder from the Windows host into the Linux VM. Both fail with "invalid argument," suggesting the underlying filesystem (OneDrive's cloud files layer) is incompatible with the host-share mechanism.
Regular Chat mode works without issues. Only Cowork is affected.
What Should Happen?
Cowork should either:
- Successfully mount OneDrive-synced folders via virtiofs or Plan 9, or
- Detect OneDrive paths and provide a clear error message guiding the user to select a local (non-OneDrive) working directory
Steps to Reproduce
- Have a Windows 11 Home system with OneDrive enabled and documents stored in OneDrive-synced folders
- Open Claude Desktop (latest version, Feb 2026)
- Switch to Cowork tab
- Start any task
- Observe: sandbox-helper mount failure before the workspace can start
Suspected Root Cause
OneDrive's Cloud Files API presents files as placeholder/dehydrated stubs on disk. The virtiofs and Plan 9 host-share protocols likely expect standard NTFS file access and cannot traverse OneDrive's filter driver. The mount call returns EINVAL ("invalid argument") because the filesystem at the shared path isn't a conventional local filesystem.
This may also affect other cloud storage providers that use similar virtual filesystem drivers (e.g., Dropbox Smart Sync, Google Drive streaming).
Troubleshooting Attempted
- Verified Windows Features: Virtual Machine Platform ✅, Windows Hypervisor Platform ✅ (Hyper-V not available on Home edition)
- Restarted Claude Desktop multiple times
- No VPN active
- Windows Defender Firewall: Claude allowed on both Private and Public networks
- Have not yet tested with a non-OneDrive local folder (will update if this resolves the issue)
Environment
| Component |
Detail |
| OS |
Windows 11 Home, Version 25H2, Build 26200.7840 |
| Processor |
13th Gen Intel Core i7-13700HX (2.10 GHz) |
| RAM |
32 GB |
| System type |
64-bit, x64-based processor |
| Claude Desktop |
Latest version (downloaded Feb 2026) |
| OneDrive |
Active, documents stored in OneDrive-synced folders |
| Windows Feature Experience Pack |
1000.26100.291.0 |
Claude Model
Opus
Is this a regression?
No, this never worked
Claude Code Version
Claude Desktop latest version (Windows, downloaded Feb 2026). This is Cowork on Claude Desktop, not Claude Code CLI.
Platform
Anthropic API
Operating System
Windows
Additional Context
# [BUG] Cowork Windows - sandbox-helper fails to mount host share (virtiofs/Plan9) with OneDrive-synced folders
Preflight Checklist
What's Wrong?
Cowork fails at VM startup with a sandbox mount error. The workspace never reaches API connection; it crashes during the host-share mounting phase. My working directories are stored on OneDrive, which may be the root cause since OneDrive uses the Windows Cloud Files API (placeholder/dehydrated files) rather than standard NTFS file access.
Error output:
CLI output was not valid JSON. This may indicate an error during startup.
Output: sandbox-helper: failed to unmount host share (tried both virtiofs and Plan9): invalid argument
The sandbox-helper attempts both virtiofs and Plan 9 (9p) filesystem protocols to mount the shared folder from the Windows host into the Linux VM. Both fail with "invalid argument," suggesting the underlying filesystem (OneDrive's cloud files layer) is incompatible with the host-share mechanism.
Regular Chat mode works without issues. Only Cowork is affected.
What Should Happen?
Cowork should either:
- Successfully mount OneDrive-synced folders via virtiofs or Plan 9, or
- Detect OneDrive paths and provide a clear error message guiding the user to select a local (non-OneDrive) working directory
Steps to Reproduce
- Have a Windows 11 Home system with OneDrive enabled and documents stored in OneDrive-synced folders
- Open Claude Desktop (latest version, Feb 2026)
- Switch to Cowork tab
- Start any task
- Observe: sandbox-helper mount failure before the workspace can start
Suspected Root Cause
OneDrive's Cloud Files API presents files as placeholder/dehydrated stubs on disk. The virtiofs and Plan 9 host-share protocols likely expect standard NTFS file access and cannot traverse OneDrive's filter driver. The mount call returns EINVAL ("invalid argument") because the filesystem at the shared path isn't a conventional local filesystem.
This may also affect other cloud storage providers that use similar virtual filesystem drivers (e.g., Dropbox Smart Sync, Google Drive streaming).
Troubleshooting Attempted
- Verified Windows Features: Virtual Machine Platform ✅, Windows Hypervisor Platform ✅ (Hyper-V not available on Home edition)
- Restarted Claude Desktop multiple times
- No VPN active
- Windows Defender Firewall: Claude allowed on both Private and Public networks
- Have not yet tested with a non-OneDrive local folder (will update if this resolves the issue)
Environment
| Component |
Detail |
| OS |
Windows 11 Home, Version 25H2, Build 26200.7840 |
| Processor |
13th Gen Intel Core i7-13700HX (2.10 GHz) |
| RAM |
32 GB |
| System type |
64-bit, x64-based processor |
| Claude Desktop |
Latest version (downloaded Feb 2026) |
| OneDrive |
Active, documents stored in OneDrive-synced folders |
| Windows Feature Experience Pack |
1000.26100.291.0 |
Claude Model
Opus
Is this a regression?
No, this never worked
Claude Code Version
Claude Desktop latest version (Windows, downloaded Feb 2026). This is Cowork on Claude Desktop, not Claude Code CLI.
Platform
Anthropic API
Operating System
Windows
Additional Context
What Should Happen?
Cowork should access the directory and subdirectories
Error Messages/Logs
CLI output was not valid JSON. This may indicate an error during startup. Output: sandbox-helper: failed to unmount host share (tried both virtiofs and Plan9): invalid argument
Steps to Reproduce
- Start Claude Desktop in Windows Home OS
- Select directory or folder (on OneDrive)
- Enter Prompt and click the go arrow
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
Cowork
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
No response
Preflight Checklist
What's Wrong?
[BUG] Cowork Windows - sandbox-helper fails to mount host share (virtiofs/Plan9) with OneDrive-synced folders
Preflight Checklist
What's Wrong?
Cowork fails at VM startup with a sandbox mount error. The workspace never reaches API connection; it crashes during the host-share mounting phase. My working directories are stored on OneDrive, which may be the root cause since OneDrive uses the Windows Cloud Files API (placeholder/dehydrated files) rather than standard NTFS file access.
Error output:
The sandbox-helper attempts both virtiofs and Plan 9 (9p) filesystem protocols to mount the shared folder from the Windows host into the Linux VM. Both fail with "invalid argument," suggesting the underlying filesystem (OneDrive's cloud files layer) is incompatible with the host-share mechanism.
Regular Chat mode works without issues. Only Cowork is affected.
What Should Happen?
Cowork should either:
Steps to Reproduce
Suspected Root Cause
OneDrive's Cloud Files API presents files as placeholder/dehydrated stubs on disk. The virtiofs and Plan 9 host-share protocols likely expect standard NTFS file access and cannot traverse OneDrive's filter driver. The mount call returns EINVAL ("invalid argument") because the filesystem at the shared path isn't a conventional local filesystem.
This may also affect other cloud storage providers that use similar virtual filesystem drivers (e.g., Dropbox Smart Sync, Google Drive streaming).
Troubleshooting Attempted
Environment
Claude Model
Opus
Is this a regression?
No, this never worked
Claude Code Version
Claude Desktop latest version (Windows, downloaded Feb 2026). This is Cowork on Claude Desktop, not Claude Code CLI.
Platform
Anthropic API
Operating System
Windows
Additional Context
- Windows 11 Home does not include Hyper-V; only Virtual Machine Platform and Windows Hypervisor Platform are available. It is unclear whether Cowork's VM layer requires full Hyper-V.
- Possibly related to [BUG] Cowork Windows - Cannot connect to Claude API from workspace (Windows 11 Home) #24918, [BUG] Cowork VM boots successfully but API is unreachable on Windows #24945, Cowork VM fails on Windows 11 Home: wrong DNS config, missing sessiondata.vhdx, no NAT #24962 (other Windows Cowork VM failures), though those report API connectivity issues rather than this specific mount failure.
- The "tried both virtiofs and Plan9" message suggests the sandbox-helper has a fallback path, but both protocols fail against the OneDrive filesystem driver.
- A potential fix or workaround might involve copying files to a local staging directory before mounting into the VM, rather than sharing the OneDrive path directly.
# [BUG] Cowork Windows - sandbox-helper fails to mount host share (virtiofs/Plan9) with OneDrive-synced foldersPreflight Checklist
What's Wrong?
Cowork fails at VM startup with a sandbox mount error. The workspace never reaches API connection; it crashes during the host-share mounting phase. My working directories are stored on OneDrive, which may be the root cause since OneDrive uses the Windows Cloud Files API (placeholder/dehydrated files) rather than standard NTFS file access.
Error output:
The sandbox-helper attempts both virtiofs and Plan 9 (9p) filesystem protocols to mount the shared folder from the Windows host into the Linux VM. Both fail with "invalid argument," suggesting the underlying filesystem (OneDrive's cloud files layer) is incompatible with the host-share mechanism.
Regular Chat mode works without issues. Only Cowork is affected.
What Should Happen?
Cowork should either:
Steps to Reproduce
Suspected Root Cause
OneDrive's Cloud Files API presents files as placeholder/dehydrated stubs on disk. The virtiofs and Plan 9 host-share protocols likely expect standard NTFS file access and cannot traverse OneDrive's filter driver. The mount call returns EINVAL ("invalid argument") because the filesystem at the shared path isn't a conventional local filesystem.
This may also affect other cloud storage providers that use similar virtual filesystem drivers (e.g., Dropbox Smart Sync, Google Drive streaming).
Troubleshooting Attempted
Environment
Claude Model
Opus
Is this a regression?
No, this never worked
Claude Code Version
Claude Desktop latest version (Windows, downloaded Feb 2026). This is Cowork on Claude Desktop, not Claude Code CLI.
Platform
Anthropic API
Operating System
Windows
Additional Context
What Should Happen?
Cowork should access the directory and subdirectories
Error Messages/Logs
Steps to Reproduce
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
Cowork
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
No response