Right-click HyperSpin.exe, select Properties, go to the Compatibility tab, and check Run this program as an administrator. Do the same for RocketLauncher.exe or HyperLaunch.exe.
Why this works: When both processes run at the same integrity level, Windows allows them to find each other’s window handles. Without admin rights, HyperSpin might be blocked from "seeing" the launcher’s hidden window (a security feature called User Interface Privilege Isolation).
Right-click HyperSpin.exe → Properties → Compatibility → Check "Run this program as an administrator." Windows often blocks a frontend from launching a second .exe (the launcher) due to User Account Control. hyperspin cannot find launcher top
Often, the log will show "No default emulator found." Here’s how to fix that:
If you are staring at this error, one of four things has gone wrong: Right-click HyperSpin
1. The Great Path Migration (Most Common)
You moved your HyperSpin folder. Perhaps you migrated from D:\Hyperspin to C:\Retro\Hyperspin. HyperSpin still thinks the launcher lives at the old address. Because HyperSpin uses absolute paths (not relative ones), moving the folder breaks every single link.
2. The RocketLauncher Relocation
You updated RocketLauncher or switched from HyperLaunch to RocketLauncher. The default name changed. HyperSpin is looking for HyperLaunch.exe, but you have RocketLauncher.exe. They are not the same file. Also verify the "HyperLaunch / RocketLauncher Script Path"
3. The Corrupt Settings File
HyperSpin.exe reads its configuration from Settings/Settings.ini. If that file gets a stray character, a missing bracket, or a duplicate entry, the launcher path reverts to null.
4. The "Portable" Paradox
Many download "pre-built" HyperSpin drives from the internet. These builds often hardcode the original creator's drive letter (e.g., E:\). When you plug that drive into your PC, it becomes F:\. The launcher is technically there, but HyperSpin cannot see it.
.ahk or .exe).If the error specifically mentions "launcher top" or similar pathing errors, check your HyperLaunch.ini (or RocketLauncher.ini) manually.