Install: nup.py: "unsafe path in the package: 'Event/EventFlow/'" – title 1 romfs size parsed as ~791 billion GB #1240

Closed
opened 2026-11-16 21:43:02 +00:00 by Ryka · 2 comments

What you used

Longshot Launcher

Version

v1.0.0-rc.9 (Windows 10.0.26300, x64, .NET 10.0.15)

Channel

Release

Where it stopped

Reading the game files

The error

Title 0 (0400486024dec000 v65536) is read normally. Extraction of title 1
(0400486024dec800 v131072) stops after ~11k–15k files with:
  unsafe path in the package: 'Event/EventFlow/'
  error: nup.py stopped (exit status 1)

Operating system and free space on the output drive

Windows 11 Pro 26H2 internal ssd with 426GB free space

Visual Studio or Build Tools version, and Windows SDK version

icrosoft Windows 10.0.26300, X64, .NET 10.0.15

Log

Title: nup.py: "unsafe path in the package: 'Event/EventFlow/'" – title 1 romfs size parsed as ~791 billion GB

Environment:

  • Launcher: v1.0.0-rc.9 (Windows 10.0.26300, x64, .NET 10.0.15)
  • PC: 31 GB RAM, 16 threads, NVIDIA + AMD GPU
  • Builds tried: v3.0.0-rc.5 (rc) and nightly-363-0cab3548 – same result
  • Game file: The Legend of Zelda - Ocarina of Time.nup
    25.62 GB, 2 titles, 1199 dirs, 372587 files
    SHA256: <HASH HIER EINFÜGEN>
  • Game file check: "Supported: This is the version Longshot supports (build e0f3ccfa)"

What happens:
Title 0 (0400486024dec000 v65536) is read normally. Extraction of title 1
(0400486024dec800 v131072) stops after ~11k–15k files with:
unsafe path in the package: 'Event/EventFlow/'
error: nup.py stopped (exit status 1)

Notable in the log:

  • title 1 romfs is reported as 186583 files, 791395369173.34 GB
    (title 0: 185994 files, 26.23 GB)
  • "85 romfs files with two different sizes"

What I ruled out:

  • Same result on every run with launcher rc.9, for both the rc.5 build and nightly-363
  • workers 1 vs. automatic: no difference
  • .nup on the internal SSD: no difference
  • SHA256 of the .nup is identical across multiple runs (Get-FileHash),
    so the file is read consistently
  • Leftover .game folders were deleted before each new attempt

The same .nup file works fine in Hookshot: it extracts and the game runs
without problems. So the file itself seems to be OK, and the problem looks
specific to Longshot's nup.py.

Additional observation:
With Launcher 1.0.0 (not rc.9) the error occurred at a different path:
unsafe path in the package: 'PreComputedCulling/RuntimeId/'
title 1 romfs: 466421810928.50 GB, 48 files with two different sizes

Guess:
It looks like a directory entry (trailing slash) in the update title's romfs
is parsed as a file, which also breaks the size calculation.

Logs attached:
1_launcher-rc9_build-rc5_workers-auto.txt
2_launcher-1.0.0_build-rc5_PreComputedCulling.txt
3_launcher-rc9_build-rc5_workers-1.txt
4_launcher-rc9_build-nightly-363_workers-1.txt

Before you send it

  • It still fails on the newest release.
  • I searched the open issues for this error.
  • I'm not attaching game files or anything built from them.
### What you used Longshot Launcher ### Version v1.0.0-rc.9 (Windows 10.0.26300, x64, .NET 10.0.15) ### Channel Release ### Where it stopped Reading the game files ### The error ```text Title 0 (0400486024dec000 v65536) is read normally. Extraction of title 1 (0400486024dec800 v131072) stops after ~11k–15k files with: unsafe path in the package: 'Event/EventFlow/' error: nup.py stopped (exit status 1) ``` ### Operating system and free space on the output drive Windows 11 Pro 26H2 internal ssd with 426GB free space ### Visual Studio or Build Tools version, and Windows SDK version icrosoft Windows 10.0.26300, X64, .NET 10.0.15 ### Log Title: nup.py: "unsafe path in the package: 'Event/EventFlow/'" – title 1 romfs size parsed as ~791 billion GB Environment: - Launcher: v1.0.0-rc.9 (Windows 10.0.26300, x64, .NET 10.0.15) - PC: 31 GB RAM, 16 threads, NVIDIA + AMD GPU - Builds tried: v3.0.0-rc.5 (rc) and nightly-363-0cab3548 – same result - Game file: The Legend of Zelda - Ocarina of Time.nup 25.62 GB, 2 titles, 1199 dirs, 372587 files SHA256: <HASH HIER EINFÜGEN> - Game file check: "Supported: This is the version Longshot supports (build e0f3ccfa)" What happens: Title 0 (0400486024dec000 v65536) is read normally. Extraction of title 1 (0400486024dec800 v131072) stops after ~11k–15k files with: unsafe path in the package: 'Event/EventFlow/' error: nup.py stopped (exit status 1) Notable in the log: - title 1 romfs is reported as 186583 files, 791395369173.34 GB (title 0: 185994 files, 26.23 GB) - "85 romfs files with two different sizes" What I ruled out: - Same result on every run with launcher rc.9, for both the rc.5 build and nightly-363 - workers 1 vs. automatic: no difference - .nup on the internal SSD: no difference - SHA256 of the .nup is identical across multiple runs (Get-FileHash), so the file is read consistently - Leftover .game folders were deleted before each new attempt The same .nup file works fine in Hookshot: it extracts and the game runs without problems. So the file itself seems to be OK, and the problem looks specific to Longshot's nup.py. Additional observation: With Launcher 1.0.0 (not rc.9) the error occurred at a different path: unsafe path in the package: 'PreComputedCulling/RuntimeId/' title 1 romfs: 466421810928.50 GB, 48 files with two different sizes Guess: It looks like a directory entry (trailing slash) in the update title's romfs is parsed as a file, which also breaks the size calculation. Logs attached: 1_launcher-rc9_build-rc5_workers-auto.txt 2_launcher-1.0.0_build-rc5_PreComputedCulling.txt 3_launcher-rc9_build-rc5_workers-1.txt 4_launcher-rc9_build-nightly-363_workers-1.txt ### Before you send it - [x] It still fails on the newest release. - [x] I searched the open issues for this error. - [x] I'm not attaching game files or anything built from them.
Collaborator

Possibly related, for context:

  • #1010 Install: Builder compiler cannot compile test program while checking .nup — Related installation-time failure while Longshot validates/reads a supported .nup file, though it is a different failure.
  • MagicBeanDev/LongshotLauncher#116 Launcher: Random crashes on Windows 11 Insider with FAST_FAIL_SET_CONTEXT_DENIED — Also reports Windows failure during extraction of a .nup in the launcher, but with a distinct crash symptom.
Possibly related, for context: - #1010 Install: Builder compiler cannot compile test program while checking .nup — Related installation-time failure while Longshot validates/reads a supported .nup file, though it is a different failure. - MagicBeanDev/LongshotLauncher#116 Launcher: Random crashes on Windows 11 Insider with FAST_FAIL_SET_CONTEXT_DENIED — Also reports Windows failure during extraction of a .nup in the launcher, but with a distinct crash symptom.
Author

Did work again

Did work again
Ryka closed this issue 2026-11-17 09:52:45 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#1240
No description provided.