Windows path too long: distinguish a shorter install root from long-path support

Scope and symptoms

An extraction, Git checkout or node build can fail because of one long path. Identify the failing tool before changing system policy or relocating an existing Python environment.

Search fragments; wording and context vary:

File name too long
WinError 206

Source-supported context

Microsoft's file-path documentation makes long-path behavior conditional on both system settings and application support. LongPathsEnabled is not a universal switch for every archive utility, native extension or older executable. V04-WINPATH

Distinguish these cases

1. A new installation has accumulated extra download and archive wrapper directories before reaching the node's own folders.

2. An established installation works, but a particular checkout or build creates a longer nested path.

3. The system setting is already enabled, while the program performing the operation does not support the required behavior.

Suggested diagnostic sequence

This sequence is editorial guidance, not a diagnosis of your machine.

1. Record the exact error, failing path and executable. Redact personal path components before sharing the report. Separate extraction from checkout and compilation.

2. For a new, unused installation, choose a shorter writable dedicated directory and extract a verified archive again. Leave the working installation untouched.

3. If only one new checkout, extraction or build fails, test that operation in a separate short, writable location supported by its tool; keep the working installation intact. If the installation root itself must change, first back up workflows and configuration, then recreate a short-path environment from declared dependencies and reconnect weights through supported external model paths. Python virtual environments are not generally movable. Python venv

4. Where long-path support is required, have an authorized administrator check the Microsoft requirements and the application's support. Restart the affected process and repeat the single operation that failed.

Completion checks

The previously failing file can now be created or checked out, and the resulting environment starts from its intended entry point. A newly created directory alone does not prove that extraction completed.

Limits and cautions

Access denial, insufficient disk space and archive corruption require separate investigation. Managed-device policy may not be yours to change; running every custom node as administrator is not a substitute for diagnosis.

Source and English-language review: 2026-09-27. No installation, checkout, GPU inference or user-environment repair was executed.

Original sources

• Microsoft: maximum file path limitation · checked 2026-09-27
• Python: venv creation and non-portability · checked 2026-09-27

Related guides

• Model or runtime download failed: separate transport, access, integrity and storage
• Keep a reproducible ComfyUI repair record without exposing secrets