{"version":"2.1.283","anchor":"win32-dirsync-anchor-transient-io-errors-now-propagate-ins","canonical_anchor":"win32-dirsync-anchor-transient-io-errors-now-propagate-ins","heading":"Temporary file system errors on Windows now surface instead of being silently ignored","tier":"internal","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/win32-dirsync-anchor-transient-io-errors-now-propagate-ins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Temporary file system errors on Windows now surface instead of being silently ignored\n\nOn Windows, busy, too-many-open-files, out-of-memory, timeout and similar errors are now reported instead of quietly switching to a weaker fallback\n\n**Unclear.** It is not known what happens next once one of these errors is reported.\n\n**What**\n\nOn Windows, Claude Code tries to keep a firm hold on your working folder (an anchored backend). If that fails to start, it can fall back to a mode without that hold. It now reports these errors instead of falling back:\n\n- `EBUSY`\n\n- `EMFILE`\n\n- `ENFILE`\n\n- `ENOMEM`\n\n- `EAGAIN`\n\n- `ETIMEDOUT`\n\n- `EIO`\n\nThe log line written on fallback now ends \"no anchored backend here\" instead of \"by name\".\n\n**Why**\n\nOn Windows, temporary resource problems now show up as errors instead of quietly weakening how Claude Code holds on to your working folder.\n\n- Area: Windows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}