5.0
Major update — browser engine upgraded to version 143
The Windows client's built-in browser engine (Chromium) has been upgraded to version 143. This is the headline change of the 5.0 release and the reason for the new major version: it modernizes web rendering and brings the engine in line with current web standards.
5.0.149
June 29, 2026
New features
- Devices now report their physical screen size in inches, read from the display's EDID.
- Added an advanced configuration option to override the browser engine's device scale factor, resolving rendering problems (blank areas and missing video) on high-resolution multi-screen setups running at high Windows display scaling. The same setting also allows disabling hardware acceleration and GPU vsync.
Improvements
- Each screen's refresh rate is now included in the device's startup log, alongside its resolution, for easier diagnostics.
- Reduced misleading error messages in device logs during screen rotation by skipping displays that aren't attached to the desktop.
Bug fixes
- Fixed an issue where a malformed update schedule sent from the server would erase a device's existing, working automatic-update schedule.
- Fixed an issue where display scaling settings were not applied to the kiosk user during first-time kiosk setup on fresh Windows devices, causing content layout to shift on the first boot.
- Fixed an issue where accented and other non-English characters appeared garbled in device logs.
- Fixed an issue where kiosk devices could enter a continuous restart loop after a client auto-update.
5.0.102
June 11, 2026
Improvements
- Improved support for displaying embedded content served from local or on-premise network addresses, including HTTP streams such as IP cameras or media servers, on the new browser engine.
5.0.91
June 9, 2026
New features
- Added the ability to set a custom NTP (time) server for a device from Advanced Configuration, with automatic fallback to the connected server when none is set.
Improvements
- Upgraded the built-in browser engine (Chromium) to version 143, modernizing web rendering and improving compatibility with current web content.
- Updated the local database engine and other bundled components to current versions for improved stability; existing device data is migrated automatically on update.
Bug fixes
- Fixed an issue where on-premise deployments served over HTTP could stop loading content after the browser engine upgrade.
- Fixed an issue where a server error combined with no previously cached copy of the content left the screen blank and stuck in a reload loop.
- Fixed a crash that could occur when loading certain cached content.
- Fixed a gradual memory increase on devices with serial sensors that reconnect frequently.
- Fixed an issue where devices could report negative memory usage.
- Fixed an issue where some devices reported no Hardware ID.
- Fixed an issue where uploading logs from a device with a large amount of accumulated logs could fail.
- Fixed an issue where saving logs to some USB drives did not work.
- Fixed an issue where a device with a daily scheduled reboot could go offline after its first automatic reboot and stop receiving content updates.
- Fixed window positioning and screen-count reporting on multi-monitor setups when displays were connected or powered on after startup.
- Fixed an issue where a window spanning multiple monitors could stay shrunk to a single monitor after a display was temporarily disconnected and reconnected, instead of returning to its configured size.
- Fixed an issue where device preview uploads could hide a real server error by retrying an older endpoint.
- Fixed an issue where the application could fail to start automatically at logon after a fresh installation.
- Fixed kiosk mode setup being incorrectly blocked on fresh Windows Enterprise devices.
- Fixed an issue where clearing a device's scheduled update rule did not fully take effect.
- Fixed crashes in MQTT sensor connections when the broker address or sensor configuration was incomplete.