Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Windows] Runner failing to extract project - Path too long

See original GitHub issue

Describe the bug After succesfully setting up the first runner for our docs website, i moved on to the next. And here the extraction of the project is failing, as the path exceeds the max length allowed on windows.

`Exception calling “ExtractToDirectory” with “2” argument(s): “Could not find a part of the path ‘C:\actions-runner-my-r elewise_work\\\main\b7fc4a2e-4d2a-4ec4-a651-46d82e1b6b6c\ 6004bfaa38b59effe973533d51b9455863\src\Infrastructure.Database.Migrations\M1636740262_RemoveColumnsFromTriggersTables.c s’.” At line:1 char:111

  • … catch { } ; [System.IO.Compression.ZipFile]::ExtractToDirectory('C:\a …`

I noticed the path that the runner is building, is somehow including 2 GUIDs…

Path: C:\actions-runner-my-relewise_work\\\b7fc4a2e-4d2a-4ec4-a651-46d82e1b6b6c\

Why is it doing this? Where are these 2 “GUID” folders coming from? The path it creates for our docs site is:


No double nested GUID folders.

the .tar file it downloads is: b7fc4a2e-4d2a-4ec4-a651-46d82e1b6b6c.tar.gz where is this guid coming from?

Expected behavior Shouldnt extract into these crazy long paths.

Runner Version and Platform


Windows server 2019

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:16 (1 by maintainers)

github_iconTop GitHub Comments

anitakruegercommented, Jun 22, 2022

This seems to happen only when git is not installed on the machine.

The repository will be downloaded using the GitHub REST API
To create a local Git repository instead, add Git 2.18 or higher to the PATH
Downloading the archive
Writing archive to disk
Extracting the archive

After installing git, the checkout action worked fine.

tGrothmannFluffycommented, Jun 29, 2022
Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Fix Zip File Error 0x80010135: Path Too Long? [5 ...
# 1. Extract the File into the Root Folder · # 2. Enable the Long Path Support in Registry Editor · # 3....
Read more >
A file copy operation fails when files or folders have long ...
The copy operation fails and generates a message that states that the path (file name) is too long. The message also suggests that...
Read more >
Runner doesn't support Windows Long File Paths (#125)
Solution. Pull in a library supporting long file paths (like syncthing/internal/osutil) to replace the standard library. Alternatively, manually ...
Read more >
I get a "Path too Long" error when trying to open an ...
If you see this error there are several solutions: 1) Instead of right clicking on the file to extract it, left click on...
Read more >
[Fixed] 0x80010135 Path Too Long While Extracting A ZIP File ...
This error occurs primarily due to files with long names or paths inside an archive. The Win32 API in Windows only supports 260...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found