Answer: Enable long-path support for both Git and Windows: run `git config --system core.longpaths true` for Git, and use the PowerShell command to set LongPathsEnabled to 1 for Windows, then restart your system. Status: Overdue (check was due 2026-11-20T13:40:20Z and has not succeeded) Entry: tool/zed/troubleshooting/path-too-long-build-fail Revision: 1 Digest: sha256:fd8adce7224b44f2 (changes whenever the content changes) Timeline: Created: 2026-11-13T04:01:54Z Last changed: 2026-11-13T04:01:54Z Last verified: 2026-11-19T13:40:20Z Next check: 2026-11-20T13:40:20Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Git fix command | git config --system core.longpaths true | [1] | 2026-11-19 Windows registry value | 1 | [1] | 2026-11-19 Restart requirement | You need to restart your system after enabling long-path support. | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/development/windows.md". https://zed.dev/docs/development/windows.md Role: primary. Accessed: 2026-11-19T13:40:20Z Quote: "For git: `git config --system core.longpaths true`" (Supports: Git fix command) Quote: "-Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force" (Supports: Windows registry value) Quote: "(You need to restart your system after enabling long-path support.)" (Supports: Restart requirement) Snapshot SHA-256: e9966eacf815a67555e213868534d6c14946f4533f020b08e1e70f6ddcdeab7a (captured 2026-11-13T04:01:53Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T04:01:54Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:40:20Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:40:20Z Last attempt: 2026-11-19T13:40:20Z Notes and limitations: Extracted automatically from a single official source (section "Build fails: Path too long"). Human-readable page: https://zed.dev/docs/development/windows.html Related: https://latestn.com/tool/zed/troubleshooting/profile-performance-macos How do I profile performance issues in Zed on macOS? https://latestn.com/tool/zed/troubleshooting/quick-cpu-flamechart-profiling How do I do a quick CPU profile of Zed with a flamechart? https://latestn.com/tool/zed/troubleshooting/racket-language-server-support Does Zed support the Racket language server? https://latestn.com/tool/zed/troubleshooting/makefile-extension-issues Where do I report issues with the Makefile extension in Zed? https://latestn.com/tool/zed/troubleshooting/missing-license-ci-failure What happens if a Zed extension has no valid license? https://latestn.com/tool/zed/troubleshooting/open-zed-log How do I open the Zed log to troubleshoot a problem? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T04:01:54Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/troubleshooting/path-too-long-build-fail/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/zed/troubleshooting/path-too-long-build-fail POST: https://latestn.com/dispute/tool/zed/troubleshooting/path-too-long-build-fail with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/troubleshooting/path-too-long-build-fail?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I fix a Zed build that fails because the path is too long on Windows? Revision 1, last verified 2026-11-19T13:40:20Z. https://latestn.com/tool/zed/troubleshooting/path-too-long-build-fail (accessed 2026-11-21T10:01:35Z). @misc{LatestN_tool_zed_troubleshooting_path_too_long_build_fail_r1, title = {How do I fix a Zed build that fails because the path is too long on Windows?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/troubleshooting/path-too-long-build-fail}}, note = {Revision 1; digest sha256:fd8adce7224b44f2; last verified 2026-11-19T13:40:20Z; accessed 2026-11-21T10:01:35Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/zed/troubleshooting/path-too-long-build-fail