Core Updates
Zaparoo Core checks for new releases on its own and tells you when one is available. It only installs a release by itself when you turn automatic installs on, and a build that fails to start is rolled back.
Update checks
Core checks about every 12 hours against a signed release manifest, and posts a message to the Inbox when a newer release exists. The Inbox is available in the Zaparoo App, the Web UI, the terminal UI, and the Decky plugin.
On MiSTer, Core counts as managed by Update All when Downloader is configured with the Zaparoo database, and on Batocera when the Zaparoo package is installed through its package manager. Managed installs still get the Inbox message, but it points at that tool and Core never replaces itself, because the package manager would undo the change. Builds compiled from source never check.
Settings
Update settings live under [updates] in config.toml:
| Key | Default | What it does |
|---|---|---|
check | true | Check for new releases and post Inbox messages. |
install | false | Install new releases automatically. Ignored while check is off. |
channel | "stable" | "stable" or "beta". |
[updates]
check = true
install = false
channel = "stable"
The same settings are updateCheck, updateInstall, and updateChannel on settings.update in the Core API. There is no update screen in the terminal UI or the Windows system tray yet.
Automatic installs
With install = true, Core stages the download, runs the new binary once to confirm it starts, backs up the user database, swaps the binary into place, and restarts. If the new build fails to start within 30 seconds, Core restores the previous one. The result arrives as an Inbox message.
An automatic install waits for a quiet minute on the API before it starts, up to 15 minutes, and refuses to run while:
- A media database update, optimization, or metadata import is running.
- A backup, restore, or cloud upload is in progress.
- A reader is writing a tag.
- The battery is below 40 percent, or Core cannot tell what is powering the device.
Media playing, an active playlist, or a busy API only delay an automatic install. Releases can be rolled out in stages, so a device may wait until the release reaches it.
Installing an update yourself
To install a reported update without turning automatic installs on, call the API from the device:
./zaparoo -api 'update.check'
./zaparoo -api 'update.apply'
update.check reports why an update is blocked and whether force can override it; update.apply accepts force for playing media, playlists, and a busy API. A manual install needs at least 20 percent battery. Paired admin clients and API keys with the update.apply capability can call the same methods.
Platform support
| Platform | Update behavior |
|---|---|
| MiSTer, Batocera | Check only when managed by Update All or the Batocera package manager; otherwise updates in place. Batocera updates carry the EmulationStation hook, multimedia_keys.conf, the Ports entry, the service files, and the write-game script. |
| Windows | Updates in place when Core can write to its install folder and rename Zaparoo.exe; otherwise the Inbox message says to run the installer. |
| All other platforms | Updates in place. |
Beta channel
channel = "beta" includes beta and release candidate builds. Moving back to stable after a beta that changed the media database layout makes Core rebuild the media database on its next start; favorites and launcher overrides are copied to the user database first, and an Inbox message tells you if that copy fails. Import artwork again afterwards with the scraper.
Troubleshooting
An update is reported but nothing installs. Automatic installs are off unless install = true, and managed installs update through Update All or the Batocera package manager. Run update.check to see what is blocking an install.
Core rolled back to the previous version. The new build did not start within 30 seconds. Check the Inbox message and the log file, then try update.apply again or install the release from your platform guide.