Skip to content

Mestra Player

Requirements

Mestra Player runs on Windows only. When you install it, it checks the PC’s edition and build against Mestra’s approved list before it changes anything. A PC that isn’t on the list is refused with a message that says why.

Windows

Edition Approved builds
Windows 10 Enterprise LTSC 2019 (build 17763), 2021 (19044)
Windows 11 Enterprise LTSC 2024 (26100)
Windows 10 IoT Enterprise LTSC 2021 (19044)
Windows 11 IoT Enterprise LTSC 2024 (26100)
Windows 11 Enterprise 24H2 (26100), then 26200 and 26300
Windows 11 Education 24H2 (26100), then 26200 and 26300
Windows 11 Pro 25H2 (26200), then 26300
Windows Server 2022 with Desktop Experience 20348
Windows Server 2025 with Desktop Experience 26100

The list is built into each player release. A new edition or build is added only after it has been tested.

These are refused:

  • Windows Home. The message says to use Windows 11 Pro, Enterprise, Education or IoT Enterprise.
  • Windows Server without a desktop, and Windows Server 2019.
  • A domain controller. The player signs in automatically, so use a separate PC.
  • Windows 11 Pro 24H2. Microsoft no longer supports it. The message says to run Windows Update to move to 25H2, then install again.
  • Any other edition or build. The message says “Windows … build … isn’t on Mestra’s approved list yet.”

The PC

  • Processor: 64-bit x64 or Arm64. The player program must match the PC’s processor.
  • Microsoft Edge WebView2 Runtime (Evergreen), installed for all users. Install stops before it changes anything if it’s missing. LTSC, IoT and Server PCs often need it installed first. The player runs on the WebView2 runtime that comes with its release, and falls back to the Evergreen one.
  • A display at its native size. The PC measures it and reports the size, and Mestra publishes to that size.
  • Windows time sync working. Bookings start and end on the PC’s clock.
  • Video decode for the formats you book. Each PC tests what it can play and reports it. See Show content on your screens.
  • A TPM 2.0, if you can. A PC with a usable TPM keeps the screen’s key in it. Without one the screen shows No TPM and keeps its key in Windows’ software key store.

Network

Direction To Port Why
Outbound player.withmestra.com HTTPS, TCP 443 Everything the player does: pairing, the schedule, files, updates, play records, screenshots and logs
Outbound Your Windows time source UDP 123 Keeping the PC’s clock right
Inbound None None The player listens only on the PC itself
  • Files and updates come from player.withmestra.com too, so one outbound rule covers the player.
  • The player connects directly to Mestra. If a site must use a proxy or inspect HTTPS, contact support before you install.
  • No VPN, port forward or remote-access tool is needed. Takedowns, schedule changes and remote actions reach the screen on a request it already holds open.
  • If time sync is blocked, the screen reports “The clock can’t be checked” and asks the site to allow UDP port 123.
  • To control a display panel over the network, the PC connects to the panel’s control port on your local network. That connection never leaves the site. See Panel control.

Next: install and connect a screen.