Claude Cowork startup or VM error: diagnose the problem step by step
By Dorian Laurenceau
A Claude Cowork startup or VM error does not identify one universal cause. The message can relate to the application version, a session, a permission, an organization setting or a temporary service problem. Start by recording the exact failure rather than applying a collection of unrelated fixes.
This is a diagnostic workflow, not a repair certified for every error. References were checked on October 14, 2026. Cowork’s interface and execution model are evolving, so older local-VM advice may no longer fit the version you use.
Record the message and context
Copy the exact error text, its timestamp and the step that triggered it. Note your operating system, application version, plan and whether the failure affects one task or all sessions. Remove secrets and personal file paths before sharing logs with support.
Distinguish an application that will not launch from a task that fails after launch. Also distinguish a session-creation problem from a folder-access problem. These failures need different evidence; calling all of them “the VM error” can send the investigation in the wrong direction.
Check official status and current availability
Open Anthropic’s service status and compare the incident time with your failure. A green status page does not prove your local setup is healthy, but a relevant incident may explain a widespread failure.
Read the current Cowork getting-started guide for the surface and plan you use. Do not assume a months-old tutorial still describes today’s architecture or menus. Check whether organization administrators control access.
Try a minimal, non-sensitive task
Start a fresh session with a short text-only request. If that works, try a single fictional document in a dedicated test folder. Avoid testing with a large production directory: too many variables make the result hard to interpret.
| Result | Next investigation |
|---|---|
| Application cannot launch | Version, installation and operating-system compatibility |
| Text-only session fails | Account access, service status, network or organization settings |
| Text works but file access fails | Folder selection, permissions and file format |
| Only a large task fails | Input size, unsupported structure or task-specific limits |
This table narrows the investigation; it does not prove the cause. Keep the exact observations so you can explain what changed between tests.
Change one variable at a time
If an official update is available, install it through the supported channel and repeat the same minimal task. If the problem concerns file access, select only the test folder and verify its contents. A successful result after changing several things at once does not show which change mattered.
Do not disable your firewall, antivirus or organization protections as a generic remedy. Do not delete virtual-machine folders or application data on the basis of an old forum post. Those actions can destroy evidence or data without resolving the failure. The Cowork safety guidance is a better starting point for permissions.
Build a support-ready diagnostic note
Prepare your instruction here. This module sends no data to a model: copy your brief into your chosen tool.
View the starter instruction
Organize my observations into error text, time, operating system, application version, account plan, failing step and minimal reproduction. Separate observations from possible causes. Suggest one non-destructive test at a time. Do not recommend disabling security controls or deleting VM data.
Escalate with evidence
Prepare a short support report containing the reproduction steps, expected behavior, actual behavior and tests already performed. Include the error timestamp and relevant screenshots after redaction. Ask your administrator when the failure appears connected to managed access.
Use a supported alternative workflow while the issue is investigated, such as summarizing an uploaded test document in an available interface. Avoid implying that the fallback proves the original failure is resolved.
Download the troubleshooting checklist. For a first safe task after recovery, follow the document-summary tutorial.
Test Your Knowledge
0 / 3 answered
Q1.What should you record first?
3 questions remaining
Sources
Module 8 — Ethics, Security & Compliance
Navigate AI risks, prompt injection, and responsible usage.
Dorian Laurenceau
Full-Stack Developer & Learning DesignerFull-stack web developer and learning designer. I spent 4 years as a freelance full-stack developer and 4 years teaching React, JavaScript, HTML/CSS and WordPress to adult learners. Today I design learning paths in web development and AI, grounded in learning science. I founded learn-prompting.fr to make AI practical and accessible, and built the Bluff app to gamify political transparency.
One practical AI workflow in your inbox
Methods, resources and new exercises. Free, unsubscribe at any time.