[BUG] Cowork fails with 0x80310000 when BitLocker-locked volume has drive letter F:

Resolved 💬 3 comments Opened Apr 3, 2026 by Simbe Closed May 14, 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?

Claude 1.569.0 fails to start the Cowork workspace with error:
"failed to add Plan9 share 'f': HcsWaitForOperationResult failed with HRESULT 0x80310000"

The VM boots successfully but crashes at the add_plan9_shares step because Claude
is attempting to share drive F:, which is a BitLocker-encrypted locked volume.
0x80310000 is FVE_E_LOCKED_VOLUME — BitLocker refuses access to locked volumes.

Claude should not be attempting to share arbitrary drive letters with the VM.
This worked correctly in version 1.1.9493.0 and broke in 1.569.0.

What Should Happen?

Claude should only share the user's home/workspace folder with the VM,
not enumerate and attempt to share all available drive letters.

Error Messages/Logs

[VM:steps] vm_boot completed (1156ms)
[VM:steps] add_plan9_shares started
[VM:start] VM boot failed: failed to add Plan9 share 'f': HcsWaitForOperationResult 
failed with HRESULT 0x80310000: {"Error":-2144272384,"ErrorMessage":""}

Steps to Reproduce

  1. Have a BitLocker-encrypted volume assigned to drive letter F: in a locked state
  2. Install or update Claude Desktop to version 1.569.0
  3. Open Cowork tab
  4. Workspace fails immediately at add_plan9_shares step

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.569.0

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗