Skip to main content

Fixing "Filename too long" errors on Windows with Git

There's a moment when you clone or pull a repository on Windows and Git throws an error like this:

error: unable to create file some/very/deeply/nested/path/to/a/file.ts: Filename too long

Nothing wrong with your code, nothing wrong with the repo. It's Windows.

Why does this happen?

Windows has a default path length limitation of 260 characters (the infamous MAX_PATH). Git operations that create files with a full path longer than that — cloning, checking out, pulling — will fail with this error. Repositories with deeply nested folder structures (think node_modules, or generated code) hit this constantly.

The fix: enable long paths in Git

Git has a config setting for exactly this: core.longpaths. You have two ways to set it, depending on your rights on the machine.

System-wide (requires Administrator privileges):

git config --system core.longpaths true

User-level (no Administrator required):

git config --global core.longpaths true

If you don't have admin rights on your machine, go for the --global version. It applies to your user account only, but that's usually enough to get you unblocked.

Remark: this only tells Git to support long paths. It doesn't automatically fix everything — Windows itself also needs long path support enabled at the OS level for some tools and APIs to fully cooperate.

Enabling long paths at the Windows level

Git's core.longpaths setting works around the limitation for Git's own file operations, but if you want long paths supported system-wide (other tools, Explorer, etc.), you also need to enable it in Windows itself:

  1. Open the Group Policy Editor (gpedit.msc) — Enterprise/Pro editions only.
  2. Go to Computer Configuration > Administrative Templates > System > Filesystem.
  3. Enable "Enable Win32 long paths".

Or via the registry, if Group Policy isn't available (e.g. Windows Home):

reg add "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v LongPathsEnabled /t REG_DWORD /d 1

A reboot is required for this to take effect.

More information

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more