Claude Code / AI Coding Tools
Claude Code VS Code extension fails on UNC network paths with ENOENT
fix Claude Code extension ENOENT error on network UNC paths Includes evidence for Claude Code troubleshooting demand.
- Category
- AI Coding Tools
- Error signature
ENOENT: no such file or directory, lstat <drive>:\<path>- Quick fix
- Compare the failing environment with a known working setup, then change one configuration value at a time.
- Updated
What this error means
ENOENT: no such file or directory, lstat <drive>:\<path> is a Claude Code failure pattern reported for developers trying to fix claude code extension enoent error on network unc paths. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Claude Code 2.1.131 on Windows fails with ENOENT on UNC paths (e.g., \server\share). Attempts to resolve as mapped drive (G:\Grupos) which doesn’t exist. All workarounds fail including cache clear and reinstall.
Common causes
- Corporate developers using network shares cannot use Claude Code at all. Extension crashes immediately on folder open. Cache corruption persists across reinstalls.
- Claude Code 2.1.131 on Windows fails with ENOENT on UNC paths (e.g., \server\share). Attempts to resolve as mapped drive (G:\Grupos) which doesn’t exist. All workarounds fail including cache clear and reinstall.
Quick fixes
- Confirm the exact error signature matches
ENOENT: no such file or directory, lstat <drive>:\<path>. - Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
- Compare the failing environment with a known working setup, then change one configuration value at a time.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.
Sources checked
Evidence note: Claude Code 2.1.131 on Windows fails with ENOENT on UNC paths (e.g., \server\share). Attempts to resolve as mapped drive (G:\Grupos) which doesn’t exist. All workarounds fail including cache clear and reinstall.
Related errors
- Claude Code REPL crash TypeError Write tool long-path prefix
- Claude Code Cowork Hyper-V Unavailable
FAQ
What should I check first?
Start with the exact ENOENT: no such file or directory, lstat <drive>:\<path> text and the smallest action that reproduces it.
Can I ignore this error?
No. Treat it as a failed Claude Code workflow until the root cause is understood.
Is this guaranteed to have one fix?
No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.
How do I know the fix worked?
Rerun the same command, editor action, or request. The fix is working when that action completes without ENOENT: no such file or directory, lstat <drive>:\<path>.