EBUSY: resource busy or locked

Another process holds the file or device Claude Code needs.

127 issues · 18 open · 109 resolved (86%) · first seen Aug 26, 2025

First response · local

What to do now

Most likely: The operating system rejected a file or directory operation.

  1. Read the first path in the error and verify that it exists and belongs to the expected user.
  2. Check disk space, permissions, symlinks and whether another process holds the target.
  3. Reproduce with the smallest affected path before changing project-wide permissions.

These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.

Is this getting better or worse?

This class of problem is converging. 37 new reports in the last 90 days vs 52 in the 90 before — -29%. The open backlog peaked at 19 in 2026-07 and sits at 18 today.

0 5 10 14 19 2025-082025-122026-042026-08
2025-08 — First reports2026-04 — Most new reports (19)2026-07 — Peak backlog (19 open)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

67 of these reports name the Claude Code build they were running, spanning 54 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 4 days across 109 closures. Of the 109 closures with a recorded reason, 11% were closed as completed and 97 as not-planned or duplicate. The most recent completed fix landed in 2026-05.

Workarounds reported by the community

35 of these issues post a workaround someone says worked. The highest-engagement ones:

[BUG] [BUG] Cowork VM fails to start on Windows ARM64 (Samsung Galaxy Book4 Edge, Snapdragon)
…in the original post plus: - Installed x64 version via the workaround from 30864 (Add-AppxPackage) — different error: "Microsoft Virtual BIOS — enabling failed with error Not Implemented (0x80004001)" - Enabled Hypervis…
Found in the thread of #40198 · still open
[BUG] Cowork VM guest kernel never boots on Snapdragon X Plus (ARM64) — connection timeout every attempt
…in ARM64 boot, not a hardware incompatibility. Working user workaround: open the workspace → ignore the 60 s error → leave the app open ~25 min (do NOT restart the app/service/PC — that kills the booting VM; the error di…
Found in the thread of #39636 · resolved
[BUG] Cowork ARM64: VM boots but guest never connects — "VM connection timeout after 60 seconds
…l connection — the timer fires before the guest can answer. Workaround: Waiting ~3 min after app launch before using Cowork allows the retry cycle to catch the VM in a ready state. Ask: Increase the guest connection time…
Found in the thread of #39161 · still open
[BUG] GPU process crash (exitCode 101457950) kills Claude Desktop and corrupts MSIX package when Opus 5 performs an in-page browser action (Windows 11)
…A/software rendering). Worth cross-referencing that thread. Workaround in the meantime: avoiding the embedded Browser pane entirely and using curl/WebFetch for anything that needs real web content.
Found in the thread of #81159 · resolved
Cowork: VM connection timeout on Windows ARM64 (Snapdragon X Plus)
…er-V plumbing issue on the Snapdragon X Plus, not something you can fix with wsl --install or a restart. The EBUSY "VM is already running" errors you see later in the log are a downstream symptom, not the cause — after a…
Found in the thread of #45480 · resolved

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 1–100

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. ENOENT: no such file or directory

    1,200 issues
  2. EISDIR: illegal operation on a directory

    495 issues
  3. EACCES / EPERM: permission denied

    415 issues
  4. ENOTEMPTY: directory not empty

    88 issues
  5. EEXIST: file already exists

    138 issues
  6. EXDEV: cross-device link not permitted

    91 issues