Can't extract when LOCALAPPDATA is symlinked #1148

Closed

opened 2026-11-09 14:45:04 +00:00 by Adrenesis · 1 comment

Adrenesis commented

2026-11-09 14:45:04 +00:00

(Migrated from github.com)

Builder version

v2.0.7

How you built

Hookshot Builder app (Windows)

Game files given to it

A .nup

The error

text
My LOCALAPPDATA is symlinked toward another hard drive. HookshotBuilder crashes on unpacking the first zip and thinks there is not enough space on C (I've 40GB free).

I get the error "unpacking part 1 of 8 failed (windows' tar.exe) is there enough free space on C:"

To fix it, I had to create another user where LOCALAPPDATA was not symlinked and it worked well.

Visual Studio or Build Tools version, and Windows SDK version

No response

Operating system and free space on the output drive

Win 10 x64 22h2 19045.6466, 40 GB free on C, 90GB free on G (for the game)

Before you send it

I'm on the newest release, or it still fails on it.
I searched the open issues for this error.
I'm not attaching game files or anything built from them.

### Builder version v2.0.7 ### How you built Hookshot Builder app (Windows) ### Game files given to it A .nup ### The error text My LOCALAPPDATA is symlinked toward another hard drive. HookshotBuilder crashes on unpacking the first zip and thinks there is not enough space on C (I've 40GB free). I get the error `"unpacking part 1 of 8 failed (windows' tar.exe) is there enough free space on C:"` To fix it, I had to create another user where LOCALAPPDATA was not symlinked and it worked well. ### Visual Studio or Build Tools version, and Windows SDK version _No response_ ### Operating system and free space on the output drive Win 10 x64 22h2 19045.6466, 40 GB free on C, 90GB free on G (for the game) ### Before you send it - [x] I'm on the newest release, or it still fails on it. - [x] I searched the open issues for this error. - [x] I'm not attaching game files or anything built from them.

NotRexed commented

2026-11-11 21:22:14 +00:00

(Migrated from github.com)

Thanks for the report. Reports of the same problem are now collected in #2505, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2505 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.

Commenting is not possible because the repository is archived.