Pkg2 Read Failed Failed To Launch Hos Jun 2026
: Back up your /Nintendo and /emummc folders (where games/saves are), then delete the existing /atmosphere and /bootloader folders from your SD card.
Bolding whether this started immediately after a firmware update will help narrow down the cause.
: A failed system update or incomplete NAND restoration resulted in BOOT0/1 (pkg1) being a different version than the RAWNAND (pkg2).
: PicoFly chip resistor values should typically be 100Ω . Some cheaper clone chips incorrectly ship with 47Ω resistors, causing unstable eMMC communication. pkg2 read failed failed to launch hos
If you are using an emuMMC (emulated NAND) and the error happens when trying to launch it, the emuMMC itself may be broken. Open Hekate, go to emuMMC -> Manage emuMMC .
By understanding the underlying causes and following the solutions outlined, you can confidently fix the "pkg2 read failed" error, get your console booting again, and keep it stable for the long term.
: This usually happens after an update, when files are copied incorrectly, or when using an old hekate_ipl.ini configuration. : Back up your /Nintendo and /emummc folders
The package2 file or the Atmosphere core files on the microSD card have become corrupted due to improper shutdowns or file transfer errors.
To understand the error, let’s break it down:
The error message "" (Horizon OS) is a common issue for modded Nintendo Switch users, typically appearing when trying to boot into custom firmware (CFW) like Atmosphère using a bootloader like Hekate . : PicoFly chip resistor values should typically be 100Ω
Validate filesystem health
I'm reaching out because I've encountered a frustrating issue that I haven't been able to resolve on my own. I'm hoping someone in the community can offer some advice or a solution.
The most common cause is having a pkg1 version that does not match the pkg2 version. This often happens after a partial or failed system update where the boot components were not updated simultaneously.
Often, this error occurs because your CFW files are too old to understand the new system firmware.