[BUG] Cowork — Failed to create scheduled task when Windows Documents folder is redirected to UNC path via Group Policy
Status Fixed / completed
Reported on v2.1.123
Maintainer reply None cached
Activity 3 comments · opened May 4, 2026 · closed May 12, 2026
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?
Creating a scheduled task in Cowork always fails with the toast message "Failed to create scheduled task. You can try again." The issue is reproducible 100% of the time on machines where the Windows Documents folder is redirected to a UNC path via Group Policy (Folder Redirection). Colleagues on the same org/tenant whose Documents folder is NOT redirected can create scheduled tasks without any issues.
What Should Happen?
Scheduled task should be created
Error Messages/Logs
Failed to create scheduled task. You can try again.
Steps to Reproduce
Create a scheduled task in Cowork
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.123 (Claude Code)
Platform
Other
Operating System
Windows
Terminal/Shell
Other
Additional Information
_No response_
3 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Same issue — Windows Server 2019 domain, GPO folder redirection. Documents folder redirected to \\\server\Users\username\ via Group Policy. Both create_scheduled_task and update_scheduled_task fail with "Invalid file path: path traversal detected" (Cowork returns this via the MCP tool, not the UI toast). Manual task creation via the Cowork UI also fails with a generic error — no event log available (Windows Store app packaging). Path is fully accessible and writable — confirmed via Windows Explorer and full share permissions. Claude Desktop - Claude 1.6608.0 (f65729) 2026-05-07T14:16:09.000Z), Windows 10 Pro.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.