Install Tilecast Player on Windows

Windows preview: release and qualification pending

The native Windows Player targets Windows 10 and 11 on x64 and ARM64. Its release packaging is implemented, but no Windows Player package has been published yet. Physical qualification on both architectures is still in progress. Do not use Windows for unattended production screens until a Tilecast release explicitly supports your setup.

When a Windows release is available, install the signed MSIX package that matches the PC and pair it with your Tilecast Server. Windows uses the same Studio, playlists, Layouts, and pairing flow as other Players.

Before you start

• Use Windows 10 version 1809 or newer, or Windows 11, on an x64 or ARM64 PC. In Settings > System > About, check System type to choose the package for your processor.
• Make sure the PC can reach Tilecast Server at the address set in TILECAST_PUBLIC_URL. Use HTTPS for a public hostname or HTTP only on a trusted local network.
• Check that the Microsoft Edge WebView2 Evergreen Runtime is installed. The Player does not bundle WebView2. If it is missing, get the Evergreen Bootstrapper for a connected PC or the matching Evergreen Standalone Installer for an offline PC from Microsoft’s WebView2 download page.
• Arrange a Windows user session for signage. The Player starts when that user signs in, not before Windows sign-in. Test your own sign-in and reboot setup before leaving a screen unattended.

Find the Windows release

1. Open Tilecast releases on GitHub.
2. Open a release whose notes list a Windows section with download links. Stable releases always include Windows. A Beta may leave it out, and its notes say so. If no release lists a Windows package, the Windows preview is not available for installation yet.
3. Download the signed .msix package for your PC: x86_64 for Windows x64, or aarch64 for Windows ARM64. Do not substitute an Edge/Linux or Android asset.

Only install Windows packages from the Tilecast GitHub repository or your organization’s approved distribution source. A GitHub Actions build artifact is not a published Player release.

Install and start the Player

1. Check the package publisher before trusting or installing it. Windows requires a signed MSIX. If Windows reports that the certificate is not trusted, see Publisher certificate trust below; do not disable signature checking.
2. Open the .msix with App Installer and select Install.
3. Launch Tilecast Player from the Windows Start menu.
4. Enter your Tilecast Server address if discovery does not find it. Follow Pair a display to approve the pairing code in Studio.
5. Assign a playlist or Layout and confirm playback. Restart the PC, sign in, and check that the Player starts again and fills the primary display.

The package declares a startup task for user logon. You can control it in Task Manager > Startup apps. An MSIX installation does not configure Windows automatic sign-in, a dedicated kiosk account, or sign-in before the desktop loads.

Publisher certificate trust

A correctly signed MSIX still cannot install if Windows does not trust the signing certificate.

• Publicly trusted certificate: Windows normally verifies it without a separate certificate-installation step.
• Self-signed or organization-issued certificate: An administrator must trust the publisher certificate on each PC before installing. Obtain the public .cer file from a trusted release or your IT administrator, and confirm its identity and thumbprint through a separate trusted channel. Never distribute a private .pfx signing key to Player PCs.

For a verified test certificate, an administrator can import the public certificate into the local computer’s Trusted People store:

Administrator PowerShell · Trusted test publisher only

Import-Certificate -FilePath .\Tilecast-Publisher.cer -CertStoreLocation Cert:\LocalMachine\TrustedPeople

Do this only for a publisher you trust. Do not import an untrusted publisher certificate into Trusted Root Certification Authorities, and don’t turn off Windows security checks. For background and other deployment methods, see Microsoft’s MSIX signing guide.

Update the Windows Player

In Studio, an Owner can open Settings > Player updates, choose Windows, select Sync from GitHub, and cache a published, verified Windows release. Owners and Administrators can then deploy that release to matching Windows screens.

A Windows Player verifies both the Tilecast-signed update metadata and the Windows MSIX identity before installation. An ARM64 screen receives only ARM64 updates; an x64 screen receives only x64 updates. The signing identity must remain compatible across updates. See Update a Player and Troubleshoot Player updates.

Windows host limits

The Player presents fullscreen on the primary monitor and keeps the system and display awake while it runs. It does not control screen power, HDMI-CEC, or DDC/CI; it does not offer an AirPlay receiver or join Presentation Networks.

Website and YouTube content use WebView2. Remote pages cannot open file-selection dialogs, so avoid assigning sites that require file uploads. Physical testing is still required for video codecs, multi-zone websites, captures, and long-running unattended playback.

Before using the Player for a real installation, verify pairing, offline recovery, restart at user logon, preview and Watch Live, and signed updates on the exact PC architecture you intend to use.