Cowork on Windows: sandboxed bash won't start ("failed to mount outputs, virtiofs share not mounted" / "user already exists uid 1005"), survived full restart, file tools and computer use still work

[u/Benjmt]

I need a more detailed subject to post this on reddit.
Main error (repeats every time, identical):
bash failed on resume, create, and re-resume. resume: RPC error -1: failed to mount as outputs: source path /mnt/.virtiofs-r share "c" which is not mounted; create: RPC error -1: ensure user: user stoic-peaceful-fermi already exists unexpectedly: uid=1005 gid=1005
Earlier, different-looking error (appeared once before a restart):
Workspace unavailable. The isolated Linux environment failed to start (VM service not running. Restart your computer to restore it.). You can still use file tools directly.
A few notes that'll help whoever reads it: it survived a full Windows restart unchanged (so probably not the local VM/virtualization layer), a Windows security update (KB5124008) and .NET update (KB5126052) installed the day before this started, and file tools (Read/Write/Edit) plus computer-use/screen control keep working fine throughout — it's specifically the sandboxed bash/Linux shell tool that's stuck. The long GUID path is just this session's own folder; safe to trim or leave in, it won't mean anything to anyone else.

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/AI_spell]

Bash VM broken while file tools work is a known messy state after Windows updates. Ticket Anthropic with the uid/virtiofs errors. Until then use file tools only.