Install: #295
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
beanstalk: approved @ 1697603
beanstalk: approved @ 2c5a62e
beanstalk: approved @ 4fd82b7
beanstalk: approved @ 64d6d09
beanstalk: approved @ 6f91fae
beanstalk: approved @ 70a78f9
beanstalk: approved @ 8015c9a
beanstalk: approved @ 8d361dc
beanstalk: approved @ 9d8356e
beanstalk: approved @ abf2227
beanstalk: approved @ d82f202
beanstalk: approved @ e5f1e40
beanstalk: approved @ ee8ab5f
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#295
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What you used
Longshot Launcher
Version
LongshotLauncher-v1.0.0-rc.3-windows-x64
Channel
Release candidate
Where it stopped
Reading the game files
The error
Operating system and free space on the output drive
WINDOWS 11 26H2 PRO 250GB
Visual Studio or Build Tools version, and Windows SDK version
No response
Log
No response
Before you send it
The inline traceback narrows this to a read from the already-open input .nup (
self.f.read(...)inNup.copy_to), after roughly 4.8 GiB had been extracted. It is not a traceback from opening the destination file. The output drive's reported free space therefore does not explain this particular error. This does not establish corruption, an antivirus cause, or a Longshot extraction bug.To distinguish the remaining causes, could you add metadata only: whether the input .nup is on a local disk, removable/network storage or a cloud-synced folder; that input volume's file system; whether the failures already observed stop at the same point; and any matching Windows disk or protection event? Please omit private paths and do not upload the .nup or extracted game files. No elevation or protection changes are needed for this diagnosis.
Triage: S0 install/build blocker; one reporter, confidence 0.4 under the workflow, affected reach unmeasured. No patch or cause is claimed yet. Current main still passes unrelated PermissionError through; changing that into a retry would not establish why this read was denied.