Explanation
Software updates
How a new version of BoothIQ reaches a booth without anyone at it. When the booth looks, what it checks before it trusts a download, why it waits for an idle moment, what Restart to apply does, and what an update leaves alone.
A booth is a Windows computer that nobody sits at, so BoothIQ updates itself. The kiosk checks for a new version on its own, downloads it, and proves it came from BoothIQ, all while no customer is using the booth; the install itself happens at a restart, one you start or the one the booth makes at three in the morning. You can watch this from the Settings tab, and you can bring the last step forward, but none of it needs you. This page explains the sequence and the reasons for it.
The booth looks on its own
Five minutes after it starts, and every six hours after that, the kiosk asks BoothIQ's release service for the newest version. Most checks end with nothing to do: there is no newer version, or the newest one is a pre-release that booths never take. A check is given ten minutes at most, so a stalled connection cannot hold anything up, and a booth that is offline simply tries again at the next interval. The timing is on Timeouts and limits.
Check for updates on the Settings tab runs the check at once, whether or not a customer is at the screen, and its result is the one line you read: "BoothIQ is up to date.", an update that could not be downloaded or could not be verified, or a version ready to install.
Idle means no customer at the screen
The automatic check never runs while a customer session is in progress. A check that finds a session under way stops and waits for the next interval, and a download that finishes during a session is neither verified nor staged until a later check finds the booth idle. Nothing is shown for any of this; the booth simply tries again later. Only the manual check runs regardless of a session, because you are standing at the admin screen when you ask for it. The booth runs around the clock, so quiet moments are frequent, and there is no reason to hurry an update past a paying customer.
Nothing runs until it is proven
A downloaded installer lands in the booth's Updates folder, listed on Where the kiosk keeps its files. Before it is used, the kiosk checks the file's signature against BoothIQ's own signing certificate, which is built into the kiosk. A file that fails the check is deleted; if you asked for the check yourself, the Settings tab reads "This update couldn't be verified, so it wasn't installed." Either way the booth keeps running the version it has and tries again later. An update that passes is staged: the kiosk writes a marker that says which installer is ready, and nothing more happens until the booth is restarted.
The check is repeated at install time. BoothIQ's update task, which runs under the system account, does not trust the marker the kiosk wrote; it verifies the installer's signature again itself before anything runs.
Restart to apply, or wait for the night
A staged update installs during a restart, and the restart happens one of three ways.
- You tap Restart to apply on the Settings tab. A confirmation, "Restart to apply update", warns that BoothIQ installs the update and restarts at once and that no customer should be using the booth; Restart now hands over to the update task, which installs the new version and restarts the kiosk, one restart in all.
- The update task runs on its own every day at three in the morning and installs anything staged. It does not wait for a customer: it asks the kiosk to close, gives it thirty seconds, and restarts the computer, so a session under way at that moment is lost. The hour cannot be moved. If customers can be at your booth at three in the morning, tap Restart to apply yourself at a quiet moment instead: a staged update installs at the next restart, and the three o'clock run then finds nothing to do.
- The task also runs when the computer starts, so a booth restarted for any other reason comes back on the new version, with the same thirty-second close.
During the install the kiosk is asked to close rather than being killed, so that on a production booth, where the kiosk is the Windows shell and Windows would otherwise relaunch it at once, it stays down long enough for the installer to run. Once the kiosk has been taken down this way, the sequence always ends in a restart, whether the install succeeded or not, so the booth is never left with a blank screen.
What you see
The Settings tab has a Software update line under the About card. It normally reads "BoothIQ checks for updates automatically." While a check runs it reads "Checking for updates…". When a version is staged it reads "An update is ready to install. Select “Restart to apply” to install it now." and the Restart to apply button appears; after a manual check the line names the version and says whether it installs now or at the next restart. The About card itself shows the version the booth is running. There is no changelog on the booth; the version history is on Changelog.
What an update leaves alone
An update replaces the program, not the booth's records. The database with the sales, credits, cash collections, templates, settings, and admin accounts stays where it is, and so do the license and the cloud link; see Offline first and what syncs. The nightly backup is separate from updating and is described on Backups.
Last verified against the software on 2026-10-26.