claude-code - 💡(How to fix) Fix Cowork not working -- Virtual Machine not loading [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49178Fetched 2026-04-17 08:48:40
View on GitHub
Comments
2
Participants
2
Timeline
8
Reactions
0
Timeline (top)
labeled ×4commented ×2closed ×1cross-referenced ×1

Error Message

Error Domain=VZErrorDomain Code=1 "The virtual machine failed to start." UserInfo={NSLocalizedFailure=Internal Virtualization error., NSLocalizedFailureReason=The virtual machine failed to start.}

  1. Workspace VM fails to start — error dialog appears with VZErrorDomain Code=1
  • The error occurs before session initialization completes, so debug logging does not capture it (debug log from a 2026-04-16T13:24:29.611Z [WARN] [3P telemetry] Event dropped (no event logger initialized): api_request

Error Messages/Logs

Error Domain=VZErrorDomain Code=1 "The virtual machine failed to start." UserInfo={NSLocalizedFailure=Internal Virtualization error., NSLocalizedFailureReason=The virtual machine failed to start.} 4. Observe: workspace VM fails to start with VZErrorDomain Code=1 error dialog 5. Click OK on the error dialog 6. Repeat steps 2-4 — error is consistent across restarts

Code Example

Error Domain=VZErrorDomain Code=1 "The virtual machine failed to start." UserInfo={NSLocalizedFailure=Internal        
  Virtualization error., NSLocalizedFailureReason=The virtual machine failed to start.}
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Claude Code native app (2.1.83) fails to start the workspace VM on macOS Darwin 25.0.0 (macOS 16 beta) with:

Error Domain=VZErrorDomain Code=1 "The virtual machine failed to start." UserInfo={NSLocalizedFailure=Internal
Virtualization error., NSLocalizedFailureReason=The virtual machine failed to start.}

Environment

  • Claude Code version: 2.1.83 (native)
  • OS: macOS Darwin 25.0.0 (macOS 16 beta)
  • Model: claude-sonnet-4-6
  • CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC is set (auto-updates disabled)

Steps to Reproduce

  1. Open Claude Code (native desktop app)
  2. Start a new session
  3. Workspace VM fails to start — error dialog appears with VZErrorDomain Code=1

/doctor Output

  • Currently running: native (2.1.83)
  • Search: OK (bundled)

Additional Context

  • Restarting Claude Code does not resolve the issue
  • The error occurs before session initialization completes, so debug logging does not capture it (debug log from a successful CLI session attached below for reference)
  • This may be a Virtualization.framework compatibility issue on macOS 16 beta

Debug Log (successful CLI session for reference)

2026-04-16T13:24:26.881Z [DEBUG] Started caffeinate to prevent sleep
2026-04-16T13:24:26.883Z [DEBUG] AutoUpdaterWrapper: Installation type: native 2026-04-16T13:24:26.884Z [DEBUG] LSP Diagnostics: getLSPDiagnosticAttachments called
2026-04-16T13:24:26.884Z [DEBUG] LSP Diagnostics: Checking registry - 0 pending 2026-04-16T13:24:26.884Z [DEBUG] Hooks: Found 0 total hooks in registry
2026-04-16T13:24:26.884Z [DEBUG] Sending 73 skills via attachment (initial, 42 total sent) 2026-04-16T13:24:26.884Z [DEBUG] Skill prompt: showing "hookify:writing-rules" (userFacingName="Writing Hookify
Rules")
2026-04-16T13:24:26.884Z [DEBUG] Hooks: checkForNewResponses returning 0 responses
2026-04-16T13:24:26.885Z [DEBUG] Getting matching hook commands for UserPromptSubmit with query: undefined
2026-04-16T13:24:26.885Z [DEBUG] Found 1 hook matchers in settings 2026-04-16T13:24:26.885Z [DEBUG] Matched 1 unique hooks for query "no match query" (1 before deduplication)
2026-04-16T13:24:26.914Z [DEBUG] StatusLine completed with status 0
2026-04-16T13:24:26.965Z [DEBUG] Hook UserPromptSubmit (UserPromptSubmit) success: {}
2026-04-16T13:24:26.967Z [DEBUG] autocompact: tokens=4293 threshold=167000 effectiveWindow=180000
2026-04-16T13:24:26.968Z [DEBUG] Dynamic tool loading: 0/25 deferred tools included
2026-04-16T13:24:26.969Z [DEBUG] attribution header x-anthropic-billing-header: cc_version=2.1.83.c50;
cc_entrypoint=cli
2026-04-16T13:24:29.611Z [WARN] [3P telemetry] Event dropped (no event logger initialized): api_request
2026-04-16T13:24:34.347Z [DEBUG] Hook output does not start with {, treating as plain text
2026-04-16T13:24:34.347Z [DEBUG] Hook PreToolUse:Bash (PreToolUse) success:
grep: repetition-operator operand invalid

What Should Happen?

Opening Claude Code and starting a new session should successfully start the workspace VM and land in a working
session without errors.

Error Messages/Logs

Error Domain=VZErrorDomain Code=1 "The virtual machine failed to start." UserInfo={NSLocalizedFailure=Internal        
  Virtualization error., NSLocalizedFailureReason=The virtual machine failed to start.}

Steps to Reproduce

  1. Install Claude Code native app version 2.1.83 on macOS Darwin 25.0.0 (macOS 16 beta)
  2. Open the Claude Code desktop app
  3. Start a new session
  4. Observe: workspace VM fails to start with VZErrorDomain Code=1 error dialog
  5. Click OK on the error dialog
  6. Repeat steps 2-4 — error is consistent across restarts

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

❯ last worked early yesterday 4/15/26

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

  • CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC env var is set, disabling auto-updates
    • CLI mode (running claude in terminal) works normally — only the native desktop app workspace VM fails
    • /doctor output: "Currently running: native (2.1.83), Search: OK (bundled)"
    • Issue is specific to the Virtualization.framework (VZErrorDomain) — not a hook, config, or auth issue
    • macOS 16 is pre-release; this may be a Virtualization.framework regression in a recent beta build

extent analysis

TL;DR

The issue is likely due to a compatibility problem between Claude Code's Virtualization.framework and macOS 16 beta, causing the workspace VM to fail to start.

Guidance

  1. Verify macOS version: Ensure that the issue persists across different macOS 16 beta versions to determine if it's a regression in a specific build.
  2. Check Virtualization.framework updates: Look for any updates or patches related to Virtualization.framework in macOS 16 beta that might address the compatibility issue.
  3. Test with CLI mode: Since CLI mode works normally, compare the virtualization setup between CLI and native desktop app modes to identify potential differences.
  4. Disable CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: Temporarily unset this environment variable to see if auto-updates or other traffic affects the issue.
  5. Monitor for updates: Keep an eye on Claude Code and macOS 16 beta updates, as a fix might be included in a future release.

Example

No code snippet is provided as the issue seems related to environment and framework compatibility rather than specific code.

Notes

The issue's reproducibility across restarts and its specificity to the native desktop app on macOS 16 beta suggest a deep-seated compatibility problem. The fact that CLI mode works normally implies that the issue might not be with Claude Code itself but with how it interacts with Virtualization.framework on macOS 16 beta.

Recommendation

Apply workaround: Given the potential for this to be a transient issue due to the beta nature of macOS 16, waiting for or applying updates to either Claude Code or macOS 16 that address Virtualization.framework compatibility might resolve the issue. If possible, using CLI mode as a temporary workaround could be viable.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING