Smarter Update Handling for Multiple or Portable LaunchBox Installs
š Summary
Modernize the LaunchBox update process to better support users with multiple or portable installations. This includes detecting existing update files to avoid redundant downloads and allowing the installer to target and update portable setups.
šÆ Feature Overview
Shared Update File Support:
If an update file already exists in a designated Updates folder, LaunchBox should verify (via size/hash) and use itāsaving bandwidth and storage when managing multiple installs.
Portable Install Update Support:
Enhance the installer to:
Detect nearby portable installations automatically.
Allow users to manually select a portable LaunchBox directory to update.
Offer the same seamless update experience as standard installs.
š¦ Benefits
Saves time and bandwidth for users with multiple installs.
Reduces redundant downloads and SSD wear.
Simplifies maintenance for users with both installed and portable setups.
Makes LaunchBox more flexible in varied deployment scenarios (e.g. cabinets, multi-user setups, dev/test environments).

Log in to comment and vote
Comments2
Jul 17, 2025
PinnedHi there!
Thanks so much for submitting this request and for taking the time to explain your use case ā that context is always super helpful.
Iāve gone ahead and fleshed out the main idea using the info you provided, and Iām opening it up to the community for further discussion and feedback. Please let me know if this fleshed-out version doesnāt match your original intended request.
Feel free to let me know if you have any extra thoughts, examples, or edge cases you think might be relevant!
Cheers,
The LaunchBox team
NULUSIOS
Jul 17, 2025
Modernize updates to support multiple installs or already downloaded update file
Right now, LB update process doesnāt things that could do:
1) Check if in āupdateā folder there is an existing update file. Can of course be size/hash checked. For people that have multiple LB installs, it is not just a time saver (after all there could be a single update folder linked between unstalls, so update file could just exist once), it also reduces disk wear, is better for bandwidth limited environments etc.
2) Support portable installs, right from the install executable. Some of us have more than on installs (which are not really installs, they are portable) or even have an install AND portable setups on the same machine. The install executable, could detect an existing install (that already does), detect a portable install in own folder (like it already does when a portable install automatically runs from within LB itself), but also allow for user to point to a portable install (that it doesnāt do now).