Short Answer
If a game you copied to KNULLI does not appear in EmulationStation, check these items in order:
- Confirm which storage device KNULLI is currently using for
/userdata. - Put the game in the existing folder for its system under
/userdata/roms/. - Match the folder name exactly. KNULLI is Linux-based and names are case-sensitive.
- Confirm that the file format is supported by that system.
- Wait until the copy is completely finished and disconnect the transfer cleanly.
- On KNULLI, open Start → Game Settings → Update gamelists.
- Return to the intended system and look for the exact filename or title.
The key distinction is simple: copying a file changes storage, while Update gamelists tells EmulationStation to rescan the game folders. A file in the wrong storage location or wrong system folder will still remain missing after a rescan.
This guide is scoped to the RG CubeXX and KNULLI Scarab 20260511, using current official KNULLI documentation. It is externally researched unless a later Retro Fix Lab revision explicitly identifies a completed device test.
Problem: The File Exists, but the Game Is Missing
The usual symptom is that a transfer appears to succeed on a computer, but one of the following happens on the handheld:
- the expected system does not appear in EmulationStation;
- the system appears, but the new game is absent;
- an old library is visible instead of the files just copied;
- the game remains missing after returning to the system list.
This is a discovery problem, not automatically an emulation problem. Do not start by changing cores, BIOS files, shaders, or RetroArch settings. First prove that KNULLI is scanning the same storage and system folder that contains the file.
Version and Evidence Scope
KNULLI Scarab 20260511 is the named stable version for this guide. The official Scarab release includes an RG CubeXX image dated May 11, 2026. The KNULLI documentation repository describes its website as intended to stay aligned with the latest public KNULLI version.
Menu wording can still differ on earlier releases, translations, themes, or customized systems. Gladiator II and Scarab also differ in parts of their storage and configuration layout. Use the functions named here—Storage, /userdata/roms, and Update gamelists—as the landmarks rather than assuming every screen is identical.
No hands-on test result is claimed in this article.
Cause: KNULLI Scans One Active Userdata Tree
Only one storage device is active as /userdata
KNULLI stores games, saves, BIOS files, themes, and settings under /userdata. In a single-card setup, /userdata points to the SHARE partition on the primary card. In a configured dual-card setup, it points to the selected secondary card instead.
KNULLI does not combine SD 1 and SD 2 into one game library. Only one of them is mounted as /userdata at a time. If you copy a game to the inactive card, EmulationStation will not find it in the active game tree.
Games must be inside the correct roms subfolder
The game folders live below /userdata/roms/. KNULLI creates separate subfolders for supported systems, such as snes or gb. The official storage guide states that files outside the predefined roms subfolders are not recognized as games.
Use the existing KNULLI-created folder for the intended system. Do not guess a new folder name from a console's marketing name.
Folder and filename case matters
KNULLI is Linux-based and case-sensitive. A folder named SNES is not guaranteed to be treated as the expected snes folder. This matters especially when a library was migrated from Windows or another custom firmware.
A copied file is not immediately the same as a refreshed game list
After a transfer, KNULLI's official network and USB instructions tell the user to run Start → Game Settings → Update gamelists. That action rescans the game folders and makes newly added games available in EmulationStation.
Supported formats are system-specific
There is no safe universal extension list for every platform. A file can be in the right folder and still remain absent if its extension or structure is not supported by that system definition. Confirm the format using the relevant official KNULLI system documentation where available, or the system reference that KNULLI directs users to.
Solution: Make One Known File Discoverable
Step 1: Confirm the active storage device
On the RG CubeXX:
- Press Start to open the main menu.
- Open System Settings.
- Find the Storage section.
- Record the selected storage device.
If a secondary SD card is selected, that card supplies /userdata; the SHARE partition on SD 1 is not simultaneously used as another game library. If internal storage is selected, KNULLI is using the SHARE partition on the primary card.
Do not change the storage selection merely to search for a file. First compare the selection with the location where the file was actually copied.
If a secondary card is involved, confirm which second SD card KNULLI is actually using before moving files.
Step 2: Open the active /userdata/roms location
Use the transfer method already configured for the device:
- For a Windows network transfer, open the KNULLI SHARE folder from Windows; it maps to the active
/userdatafolder. - SCP or SFTP can expose more of the filesystem; use
/userdatafor persistent user files. - A directly mounted secondary card should show the KNULLI-created userdata folder structure.
Do not edit paths outside /userdata for this fix.
Step 3: Use the existing folder for the intended system
Open roms, then open the folder KNULLI created for the console. For example:
/userdata/roms/snesfor Super Nintendo games;/userdata/roms/gbfor Game Boy games.
Match the existing folder name exactly, including lowercase letters. For the cleanest diagnostic, place one known supported test file directly in that system folder. Avoid deep nesting until the game has been detected once.
Step 4: Confirm the file format
Check that the file's real extension is supported by the intended system. Do not rely only on a Windows display name that may hide extensions.
If the platform uses playlists, disc descriptors, paired files, or a particular archive structure, follow that platform's system instructions. This article does not convert a multi-file game into a single-file format and does not claim that every archive is supported.
Step 5: Finish and close the transfer cleanly
Wait until the copy is complete before asking KNULLI to rescan. Do not run a game, scrape media, sync saves, or start another write operation during a USB MTP transfer. Current official KNULLI documentation warns that concurrent writes through MTP can corrupt the filesystem and recommends other transfer paths.
For a normal network copy, confirm that the destination file has the expected name and non-zero size before leaving the computer.
Step 6: Update the game lists
On KNULLI:
- Press Start.
- Open Game Settings.
- Select Update gamelists.
- Wait for EmulationStation to finish rescanning.
- Return to the system list.
The intended system should now appear if it contains at least one recognized game, and the new game should be available inside it.
Verification: Prove Storage, Discovery, and Launch Separately
Use three separate checks:
- Storage verification: The exact file is present under the active
/userdata/roms/<system>folder. - Discovery verification: After Update gamelists, the game appears in the intended EmulationStation system.
- Launch verification: The game starts with the selected emulator or core.
Passing the first two checks proves that the missing-list problem is fixed. Launch failure is a different troubleshooting branch involving the file, BIOS requirements, emulator/core selection, or platform-specific setup.
Related Guides
Do not describe the fix as verified merely because the file is visible on a computer. EmulationStation must show the game after the rescan.
If the Game Is Still Missing
The wrong card is active
Recheck System Settings → Storage. In a dual-card setup, KNULLI uses either SD 1 or SD 2 for /userdata, not both simultaneously. Compare the selected device with the card or share where the file exists.
The folder name is wrong
Move the test file into the existing KNULLI-created folder for that system. Correct differences in spelling or case. Do not create parallel folders such as SNES, Super Nintendo, or Nintendo SNES when the expected folder is snes.
The file is outside roms
A file placed beside roms, inside downloads, or elsewhere under the share will not be discovered as a game. Put it under the proper /userdata/roms/<system> path.
The extension or file structure is unsupported
Confirm the platform's supported formats. A renamed extension does not convert a file. Multi-disc and computer platforms may require companion files or playlists that a simple cartridge-system ROM does not.
The file is nested too deeply
For diagnosis, move one test file directly into the system folder and rescan. This removes folder-depth and custom system-definition variables without reorganizing the whole library.
The transfer did not finish cleanly
Compare the destination filename and size with the source. Recopy only the one test file using a stable transfer method, then run Update gamelists again. Do not assume that an incomplete or damaged file is a gamelist problem.
The game appears but does not launch
Stop treating it as a discovery issue. The correct next checks depend on the platform: valid dump, supported format, BIOS, emulator/core, and any required companion files. If a firmware warning appears, check a KNULLI Missing BIOS warning. Do not reflash KNULLI or format a card solely because one listed game fails to launch.
What Not to Do First
- Do not reflash KNULLI before confirming the active storage and correct folder.
- Do not format either SD card as a first troubleshooting step.
- Do not move the entire ROM library to test one missing game.
- Do not edit EmulationStation XML files for a normal newly copied game.
- Do not rename an unsupported file extension and assume the format changed.
- Do not restore an older
systemfolder into Scarab; the official Scarab release warns that many files and paths changed from Gladiator II. - Do not call the problem fixed until the game appears after a gamelist update.
Limitations
This guide addresses discovery in EmulationStation. It does not verify ROM legality, dump integrity, BIOS completeness, emulator compatibility, performance, achievements, scraping, or save behavior.
System definitions and accepted extensions can change between KNULLI releases. Earlier releases may use different menu labels or storage behavior. KNULLI Scarab is a major update, and the official release warns that configuration paths changed from Gladiator II.
The article intentionally avoids a universal extension table. Check the documentation for the exact system instead of generalizing one console's formats to another.
FAQ
Why does KNULLI show games from the other SD card?
KNULLI mounts one selected device as /userdata. In a dual-card configuration, changing the selected storage changes which card supplies the active games and other user data.
Do I need to reboot after copying a game?
The official transfer instructions specify Start → Game Settings → Update gamelists after the transfer. Use that rescan first. A reboot should not replace checking the active storage, folder, and file format.
Why is the whole system missing from EmulationStation?
If KNULLI finds no recognized games for a system, that system may not appear. Confirm that at least one supported file is in the exact KNULLI-created folder, then update the game lists.
Can KNULLI use games from SD 1 and SD 2 at the same time?
No. Official KNULLI storage documentation says only one card can supply /userdata at a time.
Does changing .zip to another extension make a game supported?
No. Renaming an extension does not convert the underlying format. Use a format and file structure supported by the intended system.
The game is listed but will not start. Is this guide's fix incomplete?
No. Listing and launching are separate checkpoints. Once the game is listed, investigate the platform's file, BIOS, emulator/core, and companion-file requirements.