Claude Desktop task stopped mid-run?

A local Cowork task can end when Claude Desktop closes or the computer sleeps. On Windows, missing virtualization services can prevent Cowork from starting at all. Diagnose the desktop layer first, then preserve the project state before retrying.

Preserve first: Record whether the app closed, the machine slept, or a tool failed. Save the last task output and inspect files before retrying; a stopped interface does not establish whether earlier actions completed.

Match the failure before retrying.

The app closed or the computer slept

Anthropic states that local Cowork sessions need Claude Desktop open throughout the task. Closing the app or sleeping the computer can end the session.

Cowork will not start on Windows

Missing HNS, vmcompute, or related Virtual Machine Platform services can block Cowork even when Claude Desktop itself installed.

A connector or extension is stale

Restart or update Claude Desktop and inspect extension settings when tools are installed but unavailable.

Safe recovery path.

Check whether the project files changed and capture git status, git diff, and the last command output.

Open Help, Troubleshooting, Show Logs and identify whether the failure is app state, permissions, connector state, or Windows virtualization.

Update and restart Claude Desktop. On Windows, verify Virtual Machine Platform and its services using Anthropic's deployment guidance.

Restart with one bounded task and one verification step; do not assume a stopped desktop task completed safely.

What the next AI should receive.

Include operating system, Desktop version, local or remote task type, sleep/app-close timing, relevant troubleshooting logs, and actual file changes. Keep startup failures separate from interrupted running tasks.

How ShardStitch works with Claude Desktop.

ShardStitch prepares a Claude Desktop continuation packet from local project truth. When desktop Recall is unavailable or unverified, it stays honest about that scope and relies on the files, Git state, notes, and checks that can be proven.

Source trail.

Desktop diagnosis starts with the exact client surface and the permissions of the stopped task.

FAQ.

Does a stopped Desktop task mean no files changed?

No. Earlier actions may have completed. Inspect the destination files and available command output before repeating writes or assuming the task succeeded.

Should every stopped task be treated as a Windows virtualization failure?

No. A failure to start Cowork and an interruption after a task began are different symptoms. Match the logs and operating system before changing platform settings.

Scope note: Desktop behavior differs by operating system, deployment method, permissions, and whether a task is local or remote.