{"version":"2.1.283","anchor":"windows-file-sync-error-table-gains-resourceio-ntstatus-cod","canonical_anchor":"windows-file-sync-error-table-gains-resourceio-ntstatus-cod","heading":"More Windows file and I\/O errors are recognised by name","tier":"internal","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/windows-file-sync-error-table-gains-resourceio-ntstatus-cod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### More Windows file and I\/O errors are recognised by name\n\nSix more Windows NTSTATUS error codes, for memory, open-file limits, device and timeout failures, now map to specific POSIX errors\n\n**Unclear.** How Claude Code uses these codes, for example whether it retries on them, is not settled.\n\n**What**\n\nOn Windows, low-level failures are reported as NTSTATUS codes (numeric error codes from the operating system). The table Claude Code uses to turn these into standard POSIX error names, used by file sync among others, gains six entries:\n\n- `NO_MEMORY` and `INSUFFICIENT_RESOURCES` map to `ENOMEM`\n\n- `TOO_MANY_OPENED_FILES` maps to `EMFILE`\n\n- `IO_DEVICE_ERROR` maps to `EIO`\n\n- `DEVICE_NOT_READY` maps to `EAGAIN`\n\n- `IO_TIMEOUT` maps to `ETIMEDOUT`\n\nBefore, these fell through to the default mapping.\n\n**Why**\n\nWhen a Windows file operation fails for one of these reasons, the error now names the actual problem, such as running out of memory, too many open files or a timeout, instead of a generic failure.\n\n- Area: Windows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}