Windows
Windows is a beta platform: Core installs and runs, but some launchers and setup paths are still being completed.
Zaparoo Core on Windows runs in the system tray and supports Steam, LaunchBox, Big Box, and custom launcher configurations.
File paths
| Item | Path |
|---|---|
| Config file | %localappdata%\zaparoo\config.toml |
| Data directory | %localappdata%\zaparoo |
| Log file | %localappdata%\zaparoo\logs\core.log |
| Mappings directory | %localappdata%\zaparoo\mappings |
| Launcher directory | %localappdata%\zaparoo\launchers |
Access these paths by pasting them in Explorer's address bar or in a Win+R dialog.
Install
Download Zaparoo Core for Windows from the Downloads page.
Installer: Run the setup executable and follow the wizard. Options include running on startup, creating a desktop icon, adding a Windows Firewall rule so Core is reachable on every network profile, and installing the ViGEmBus driver for virtual gamepad input (not offered on ARM64).
Manual: Extract Zaparoo.exe from the zip and run it. It starts in the system tray.
Once running, use the Zaparoo App on your phone or the built-in web UI to manage your setup and write tokens.
Uninstall
Open Windows Settings > Apps > Installed apps, find Zaparoo Core, and select Uninstall. This removes the installed application and its firewall rule but leaves your Core configuration and user data under %localappdata%\zaparoo. The ViGEmBus driver stays installed in case other software uses it; remove it from the same list, where it appears as ViGEm Bus Driver.
Updates
Core checks for new releases on its own and can install them in place when it is able to write to its install folder; when it cannot, the notice says to run the Windows installer again. See Core updates.
System tray
Right-click the Zaparoo icon in the system tray to access the following options:
| Menu Item | Description |
|---|---|
| Open | Opens the Zaparoo web UI in your browser |
| Address | Shows the local IP address and copies it to clipboard |
| Edit Config | Opens config.toml in your default text editor |
| Mappings | Opens the mappings directory in Explorer |
| Launchers | Opens the custom launchers directory in Explorer |
| Reload | Reloads Core settings and files without restarting |
| View Log | Opens the log file for troubleshooting |
| Upload Log | Uploads the log for support and copies the link to the clipboard |
| Pair Device... | Shows a PIN for pairing a phone, tablet, or browser |
| Check for Updates | Shows the update state and installs a waiting release; the label changes to Install with the version when one is waiting |
| Quit | Stops the Zaparoo service and exits |
Client security
Windows requires encrypted connections from remote clients. Pair a phone, browser, or other client with the six-digit PIN that Core shows under Pair Device... in the tray menu. The PIN expires after five minutes. See encryption for how paired clients and their permissions work.
Readers
| Type | Reader | Support | Setup | Notes |
|---|---|---|---|---|
| NFC/RFID | PN532 USB | Supported | Auto-detected | |
| NFC/RFID | PN532 Module | Supported | Depends on wiring | UART can auto-detect. I2C is supported. |
| NFC/RFID | ACR122U | Limited | Auto-detected | Can scan tags, but cannot write them through PCSC. |
| NFC/RFID | RC522 | Limited | Via Simple Serial | Requires a microcontroller; not a direct USB reader. |
| Barcode and QR | Zaparoo App camera | Supported | Via Zaparoo App | |
| Barcode and QR | RS-232 scanner | Supported | Manual config | |
| Optical and Media | Optical Drive | Not supported | Linux only | |
| Optical and Media | External Drive | Supported | Manual enable | |
| Custom and Virtual | MQTT Reader | Supported | Manual config | |
| Custom and Virtual | Simple Serial | Supported | Manual config | |
| Custom and Virtual | File Reader | Supported | Manual config | |
| Displays and Integrations | TTY2OLED | Supported | Manual enable |
Each reader's page has setup steps and troubleshooting. See readers to compare them, or the setup guide to pick one for your setup.
Launchers
| Launcher | Systems | Notes |
|---|---|---|
| Steam | PC | Auto-detected from registry |
| LaunchBox / Big Box | 100+ | Both interfaces use the same required plugin |
| RetroBat | 80+ | Auto-detected, requires running with web API enabled |
| Flashpoint | PC | Manual token creation |
| Kodi | Video, Music | Local files and library media |
| PinUP Popper | Pinball | Auto-detected, launches through Popper |
| Web Browser | Any | Opens URLs in default browser |
| Executables | Any | .exe files (requires allow list) |
| Scripts | Any | .bat, .cmd, .lnk, .a3x, .ahk (requires allow list) |
Executables and Scripts require an allow_file configuration in your config.toml before they can be launched. See Launchers for setup instructions and configuration.
Input
ZapScript input commands send keyboard presses to the active window. They cannot reach windows running as administrator or the lock screen. Virtual gamepad input needs the ViGEmBus driver from the installer and gamepad_enabled = true in config.toml; it is off by default because an extra controller changes the controller order in games.
Troubleshooting
Core stops applying settings after you edit config.toml. One syntax error makes Core ignore the whole file. Open it from the tray menu (Edit Config), check it against the config reference, and remember that backslashes in Windows paths must be escaped or written in single-quoted strings.
Core is not running. Start Zaparoo.exe; it lives in the system tray. Use View Log in the tray menu to see why it stopped, or Upload Log to get a link you can share when asking for help. If Core stopped because a newer version had upgraded its data, the Web UI address shows a page saying which version to reinstall.
A reader is not detected. Some PN532 USB readers need a USB serial driver on Windows. See the PN532 USB page.
Steam, LaunchBox, or PinUP Popper games do not launch. See Windows launchers for the required setup for each launcher.