claude-code - 💡(How to fix) Fix [Windows] Workspace fails to start - tries to mount non-existent D: drive via Plan9 share [1 participants]

Failed to start Claude's workspace
failed to add Plan9 share 'd': HcsWaitForOperationResult failed with HRESULT 0x80070003:
{"Error":-2147024893,"ErrorMessage":""}

HRESULT 0x80070003 = "The system cannot find the path specified."

TL;DR

Modify the workspace initialization to check for existing drives before attempting to mount them, specifically avoiding the non-existent D: drive.

Guidance

• Verify the list of available drives on the system before initializing the workspace to prevent attempting to mount non-existent drives.
• Consider adding a check for the presence of a D: drive specifically, since it's the culprit in this case, and skip the mounting process if it's not found.
• Review the Plan9 share configuration to ensure it's not hardcoded to expect a D: drive, and update it to be more dynamic or configurable if necessary.
• Test the workspace initialization with different drive configurations to ensure the fix is robust and doesn't introduce new issues.

Example

No explicit code example can be provided without more context on the implementation details, but the idea would be to add a conditional check before calling the HcsWaitForOperationResult method to ensure the drive exists.

Notes

The provided error message and HRESULT suggest a straightforward issue of attempting to access a non-existent path. However, without access to the specific code or configuration files, the exact implementation of the fix cannot be determined.

Recommendation

Apply a workaround by modifying the workspace initialization to dynamically check for existing drives, as this directly addresses the root cause of the issue without requiring additional dependencies or upgrades.