[BUG] Claude CoWork does not support Windows 11 setups w/two hard drives and Documents on the D:\ drive.
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?
Trying to get Dispatch and scheduled tasks to work with skills to support my personal system and ran into an issue where cowork is struggling because my documents folder in windows is on the D: drive... Asked Claude to help me understand the cause and it said the fix is trivial for Anthropic. Please fix this.
What Should Happen?
Claude cowork should work seamlessly with windows 11 machines with multiple drives where user documents folder is on the d: drive.
Error Messages/Logs
Asked Claude to help me understand the cause and it said:
The root cause is a Claude Desktop bug: when running a task, it tries to hard-link the SKILL.md from D: to the session folder on C:, and Windows doesn't allow hard links across drive letters. Recreating tasks just creates more D: drive files.
Two things worth knowing:
Your Documents folder is likely redirected to D:. This is common on Windows setups with a secondary drive. Claude Desktop inherits that. You could redirect Documents back to C:, but that's a bigger system change.
This should be reported to Anthropic — the fix is trivial on their end (use fs.copyFile instead of fs.link for cross-device scenarios). You can submit feedback via the thumbs down button in Claude Desktop.
Steps to Reproduce
Not sure of a generic how to recreate this:
My situation is that I have two drives on my Windows PC, with my documents folder defined as being on the D drive.
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
Claude CoWork for Windows - 1.569.0 (49894a)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
_No response_
This issue has 11 comments on GitHub. Read the full discussion on GitHub ↗