I recently managed to get a newer version of a PS5 game (Ghost of Yotei v2) working on firmware 13.60, using PS5 Library 0.7.39 and ShadowMountPlus 1.7beta11. I finished the game on v1.0, and today I was trying to download de v2 (dlc+ new modes) without losing my progress, I ran into several issues along the way, including failed extraction, missing game files, duplicate copies, and ShadowMount+ loading an older version instead of the newer one. Here's exactly what worked for me. My setup PS5 firmware: 13.60 PS5 Library: 0.7.39 ShadowMountPlus: 1.7beta11 Game format: Extracted folder dump Original installed version: 01.008.000 New version: 02.002.000 1. Fixing the "No installable package found" error I downloaded a game through the PS5 Library catalog (Folder format). The download completed, but the unpacking process failed with: No installable package, image, or sce_sys/param.json game folder found. When I checked the downloaded file under: /data/ps5-library/downloads/ I noticed something strange. The downloaded archive was around 122 GB, but its filename was just a random string with no file extension. For example: PEpuXQjiMR I renamed it to: PEpuXQjiMR.rar Then I manually started the unpacking process again from the PS5 Library file manager. It worked! The extraction started processing thousands of files, and eventually produced the expected PS5 game folder structure. This doesn't prove that every unpacking failure is caused by a missing extension, but it fixed my specific case. 2. Verify the extracted game folder After extraction, my folder looked roughly like this: PPSAxxxxx-app/ ├── cache_ps5/ ├── fakelib/ ├── movies/ ├── sce_module/ ├── sce_sys/ │ └── param.json ├── sounds/ ├── ui/ ├── eboot.bin └── ... The important things to check are: eboot.bin exists. sce_sys/param.json exists. The extraction actually finished. PS5 Library created the .ps5library-unpacked marker in the parent extraction folder. Initially, I couldn't find eboot.bin or param.json, because the extraction was still running. So don't assume your dump is incomplete just because those files haven't appeared yet. 3. ShadowMountPlus detects a duplicate and ignores the newer version After extracting the new version, I attempted to register it with ShadowMountPlus. However, I received a notification saying: Duplicate copy of PPSAxxxxx ignored ShadowMountPlus continued displaying the older version, even though the new folder was present. I enabled debug logging and checked: /data/shadowmount/debug.log The log revealed that ShadowMountPlus had already mounted an older image: /data/homebrew/PPSAxxxxx.exfat And was ignoring the newer extracted folder: /data/homebrew/PPSAxxxxx-app Both sources had the same Title ID. The older .exfat image was being prioritized over the extracted folder. 4. Switching from the old EXFAT image to the new folder Here's what I did: Made sure no game or installation process was running. Opened PS5 Library's file manager. Navigated to /data/homebrew/. Located the older game's .exfat image. Renamed it from: PPSAxxxxx.exfat to: PPSAxxxxx.exfat.old Kept the newer PPSAxxxxx-app folder unchanged. Restarted the PS5 and reloaded ShadowMountPlus. Scanned the game library again. Important: Renaming the old image does not immediately unmount it. ShadowMountPlus may continue displaying the old source until its mounts and game registrations are refreshed. Do not delete the original image until you've confirmed the new version works. 5. Confirming that the newer version is running In my case, ShadowMountPlus initially continued showing the older version number. However, after switching sources, the game launched successfully and featured content that was exclusive to the newer update. The game also launched noticeably faster. I later confirmed that ShadowMountPlus was pointing to: /data/homebrew/PPSAxxxxx-app Instead of the older .exfat image. The newer game's sce_sys/param.json also confirmed its content version. So if ShadowMountPlus displays unexpected version information, check both the actual source path and the content available in-game before assuming that the switch failed. 6. Recovering storage space After confirming that the newer extracted folder was working, I cleaned up the old files. In my case, the older .exfat image was around 154 GB. Before deleting it, I verified that ShadowMountPlus was using the newer -app folder. I then deleted the renamed .exfat.old file through PS5 Library. My available storage increased from: 842.3 GiB → 987.6 GiB That's 145.3 GiB recovered just by removing the old image. You can also check PS5 Library's storage management for leftover archives, failed downloads, and duplicate extraction folders. Be careful not to delete your active game source or files belonging to other ongoing downloads. TL;DR If you're having problems with PS5 Library and ShadowMountPlus: Download finished but unpacking failed? Check whether the archive is missing its extension. If it's actually a RAR archive, rename it to .rar and try manual extraction. Wait until extraction finishes before checking for eboot.bin and sce_sys/param.json. If ShadowMountPlus reports a duplicate, inspect /data/shadowmount/debug.log. Check whether an older .exfat image is taking priority over your newer -app folder. Preserve the old image by renaming it rather than deleting it immediately. Refresh or restart ShadowMountPlus and verify which source is actually being used. Test the newer version before removing the older game image. Clean up old downloads and redundant sources only after confirming everything works. This was tested on firmware 13.60 with PS5 Library 0.7.39 and ShadowMountPlus 1.7beta11. It solved my issue, but compatibility and results may vary depending on the game, dump format, and payload version. Hope this helps someone avoid downloading and extracting 100+ GB multiple times!   submitted by   /u/Minimum-Composer-160 [link]   [comments]