Source review: October 11, 2026. Follow the linked DSi Guide and DS-Homebrew documentation for your exact setup. Their supported installers and procedures can change.
Know what changes on the console
Unlaunch is installed on the DSi's internal storage and runs early in the boot process. It is different from copying an application to an SD card. Installing, updating or uninstalling it writes NAND and carries a possibility of failure. Make a console-specific NAND backup and complete the SD preparation checks before using a permanent installer. An unstable battery or a malfunctioning SD card is a reason to resolve the hardware or storage problem first.
Use the currently supported installer
The reviewed DSi Guide links to the Safe Unlaunch installer maintained in edo9300's repository. Follow that complete guide for the exact setup, including its version-specific branches; do not mix an old video tutorial with a new installer screen. The retail DSi Guide explicitly excludes development consoles, while the installer repository describes development-console support. Treat a development unit as a separate workflow and verify the exact release's instructions instead of applying this retail guide. The repository also lists firmware-specific installation restrictions; check that branch before proceeding. A program containing the word safe is not a guarantee that every damaged system or incorrect input is recoverable. Preserve the downloaded release information and read each warning before starting the write.
Configure a simple boot arrangement
Hold A and B during startup to reach the Unlaunch Filemenu. The DSi Guide documents this as the hardcoded way to reach its menu. Its options can assign a default NO BUTTON target and targets for individual buttons. Launcher refers to the original DSi menu; a TWiLight Menu++ target should point to the intended BOOT.NDS on the SD card. Record the file path shown rather than choosing the first similar-looking title in the list.
Keep a fallback and test it
Choose a useful LOAD ERROR behavior for a missing or failed default target, following the guide. Save the configuration, then test the normal boot and the alternate button route. Power off before removing the SD card and verify what happens when the normal target is unavailable. This gives you a documented recovery route for an ordinary missing-file problem. A boot menu that still opens proves a different state from a machine with no accessible boot code; describe that distinction accurately when seeking help.
Avoid turning configuration fixes into NAND repairs
If the system boots into the wrong application, change the target from the Filemenu. If a menu stops loading after files are renamed or a card is removed, restore the correct SD package and path. Do not routinely uninstall Unlaunch or restore NAND to recover a theme, menu file or mistaken shortcut. Some original-menu effects can also depend on the installer options, so loss of a splash or background sound should be investigated as configuration before a speaker repair. Keep a brief record of the chosen default, fallback and tested buttons. A repeatable boot configuration is easier to maintain than several undocumented overlapping startup routes.
Sources and project documentation
- DSi Guide: supported Unlaunch installation and boot options
- edo9300: Safe Unlaunch installer source
- DSi Guide: boot-target and configuration troubleshooting
Next, read TWiLight Menu++ and homebrew.