Pick bare Linux when a screen only plays content and you manage the stack yourself. Pick Android, provisioned in device owner mode, when a screen takes touch or you run the fleet with one management tool. Pick Windows 10 IoT Enterprise LTSC 2021 when the player must live on a Windows PC and suppressing system dialogs is the hard part.
The operating system decides who gets called when a sign misbehaves at opening time. For a signage player the split is short. Bare Linux for screens that only play content and that you or your installer keep updated. Android for anything with touch, and for fleets managed with one tool. Windows 10 IoT Enterprise LTSC 2021 when the player has to live on a Windows PC and the hard part is keeping desktop dialogs off the screen. Driver support, boot behavior and update control all follow from those three answers, so this page compares the three on what matters on site: unattended playout, touch, dialogs, and who fixes what at 7 a.m.
What decides the operating system
Four questions sort it:
- Does any screen take touch? Touch pushes the choice to Android. It was designed for touch input, and most touch-first player and lockdown tools target it.
- Who maintains it, and how many screens? Two or three screens with an owner who swaps content on a card need no management system at all. Twenty screens across sites need silent updates, which means Android in device owner mode, or a Linux stack you already know how to run.
- Does a Windows PC already sit in the job? A ticket booth counter, or a factory PC that feeds a status board while it runs other software: the OS is already chosen, and the work is keeping dialogs off the player.
- What happens at boot? Whatever you pick has to reach playing content with nobody present: an autostart entry on Linux, the home app on Android, a locked-down shell on Windows.
The OS choice sits next to the screen choice, and the screen comes first if you are still sizing panels. The screen size and viewing distance guide covers that with the viewing-distance math.
The three systems side by side
| Bare Linux | Android | Windows 10 IoT Enterprise LTSC 2021 | |
|---|---|---|---|
| Best at | Lean playout you control end to end | Touch first, appliance behavior | A quiet player on a PC that must stay that way |
| Boot to content | Your build: autostart entry or kiosk session | Player set as the home app, full screen at power-on | Locked-down shell, dialogs suppressed |
| Touch | Works, more of a project | Built for it | Works, heaviest stack |
| Dialogs and pop-ups | None unless you add them | Hidden by the home app or the EMM lockdown | The main reason to pick this edition |
| Updates | You schedule them | Silent, pushed by the EMM in device owner mode | Security fixes only, to Jan 14, 2032 |
| Watch out for | Board support: confirm mainline video decode | Vendor builds differ between boxes | Only the IoT LTSC edition; regular Windows 10 is past standard support |
| Pick it when | No touch, small fleet, someone owns the boxes | Any touch, managed fleet | Windows-only player software, or a PC already in the job |
Where bare Linux wins
Bare Linux turns the whole system into the player. There is no launcher, no status bar and no home screen to hide, because the media player runs as the whole UI. Updates happen when you decide, a nightly check at 3 a.m. if you like, and nothing on the system argues.
Hardware is the part to check before you buy. The old driver swamp has largely drained on current ARM boards: open graphics and video decode drivers sit in the mainline kernel. A board that still needs a vendor kernel fork puts you back on the old treadmill, so confirm mainline support for the video decoder on the maker's page, then buy.
Boot to content is your build too. Set the player or browser to start on boot: the chromium kiosk autostart walkthrough covers the browser path on a Linux panel, and the embedded Linux kiosk boot splash article keeps the console text behind a splash so nobody sees it.
Pick Linux when the screens have no touch, the fleet is small, and someone on your side can ssh in. Pick something else when nobody owns the boxes.
Where Android wins
Android is the practical pick the moment input is part of the job. Touch works the way the OS expects, and the app base covers players, browsers and lockdown tools.
The lockdown route to use is device owner mode. The device is provisioned through your EMM, and the management app owns the OS-level jobs: it pins the player fullscreen and pushes silent updates while the device stays unrooted. Keep the piece that touches system functions small. A thin launcher wrapping the OS jobs, with the player as a separate app, stays easier to maintain than one huge app doing both.
For a single appliance with no fleet to manage, the simple version is enough: set the player up as the home app and the show comes up full screen at power-on, with no launcher and no keyboard. That is how the included player works on the panel-mount all-in-ones, playing images and MP4 files from microSD or USB with no network and no subscription.
Three things to watch. Vendor-modified builds mean two boxes with the same Android version can behave differently, so standardize on one model per fleet. Background and power-saving restrictions assume a phone, so exempt the player. Video decoding depends on the chip inside the box; H.264 MP4 is the master format that survives, and the Android signage player black screen on video article walks the check for a box that shows black instead of the first clip.
Android TV is a different product from Android on a signage panel. The Android TV for digital signage article sorts out which parts transfer to a player install.
Where Windows 10 IoT Enterprise LTSC 2021 wins
Desktop Windows has one old, well-known problem in signage: the OS keeps trying to talk. Update prompts, notifications and error pop-ups land over the player, including prompts asking you to restart, and they sit on top of a player that is designed to restart itself within seconds after a stop and get back to playing. LTSC 2021 is the edition that answers the rest of it. It takes no feature updates, so no half-finished upgrade lands mid-week, and it tunes down to a minimal service set with dialogs suppressed and updates scheduled in the middle of the night.
The dates come from Microsoft's lifecycle page: released November 16, 2021, mainstream support ended January 13, 2027, security fixes to January 14, 2032. Deploy a player on this edition in March 2027 and the arithmetic runs 2032 - 2027 = 5 years, less the 2 months between January and March, which leaves 4 years and 10 months of cover. A consumer Windows 10 install hands you the opposite: standard support for the regular editions ended in October 2025 on Microsoft's calendar.
Choose this path when the player software is Windows-only, or when the PC already has a day job. A ticket booth counter and a factory PC feeding a status board are Windows machines by default; the shop-floor screens category covers the screen side of that layout.
Suppressing dialogs and pinning the shell is configuration work with a known shape; a walkthrough of kiosk startup and Windows lockdown shows the pieces in order. When the player fails to appear in the kiosk app list at all, the article on why a signage player is missing from Windows 10 kiosk mode explains the cause.
One security note: keep a network-connected player PC on the security-update train for the whole window. The unsupported install attached to a store or plant network is the risk here.
Example: two menu boards and one touch kiosk in a cafe
The case: three screens in a cafe. Two counter menu boards take no input; one self-order kiosk has a touchscreen. Content is 1920 × 1080 slides and MP4 clips, the usual Full HD signage format. The boards are on from 7 a.m. to 7 p.m., 12 hours a day. The menu changes every 2 weeks. The owner has no IT staff.
The rule in words: any screen that takes touch runs Android in device owner mode. Screens that only play take the leanest path someone on site can keep alive: bare Linux if an installer owns them, an appliance player if not. Windows enters only when a Windows PC is already part of the job, and this job has none.
The arithmetic:
- Touch: 1 of the 3 screens takes touch, so at least that screen runs Android. Keeping all three on one image leaves one update path and one spare.
- Content updates: 52 weeks / 2 weeks per change = 26 updates per board per year, each done at the counter by swapping the USB stick or microSD card. Nothing in that path needs a management system.
- On-time: 12 h/day × 7 days = 84 on-hours per board per week, all unattended, which is why each screen has to reach playing content on its own at power-on: home app on Android, autostart entry on Linux.
Result: one Android image covers all three screens, with the kiosk pinned in device owner mode and the two boards running the player as the home app. Bare Linux loops would also serve the two boards and leave less running in the background; with nobody on site to maintain them, the appliance path is the safer bet.
Decision: touch anywhere in the plan means Android. Pure playout with someone who can ssh means bare Linux. A Windows PC already in the job means Windows 10 IoT Enterprise LTSC 2021.
The decision
Recommendation: Choose bare Linux when the screen only plays and someone on your side keeps it current over ssh; a couple of no-touch screens with a card-swap workflow is the classic case. Choose Android, provisioned in device owner mode through your EMM, as soon as one screen takes touch or the fleet grows past what walking around with a USB stick can feed, call it a dozen screens. Choose Windows 10 IoT Enterprise LTSC 2021 when the player must run on a Windows PC, and take that edition for the dialog control and the security fixes that run into 2032. When you want none of this maintenance, an all-in-one signage display with the player set up as the home app is the appliance version of the Android path; the current range sits in the displays catalog and its software comes confirmed in the quote.
Questions
Android is built on Linux, so is it the same choice?
The kernel underneath is the same. Android replaces the rest of a desktop Linux stack with its own C library, Bionic, the ART runtime, and a UI layer built for touch. A player on Android runs as an app inside that stack, so you manage apps, vendor builds and background limits. Bare Linux strips all of that away and runs the media player as the whole UI.
What is device owner mode on Android?
It is an Android Enterprise provisioning mode. Applied the first time a device starts, it hands your EMM the authority to pin the player fullscreen, push silent app updates and hold the settings that matter, all with the device left unrooted. It is the supported route to a locked-down Android player on panels and boxes alike.
Which operating system do IMD Signage displays run?
The panel-mount all-in-one series runs Android and comes with a free player. Set up as the home app, it is designed to bring the show up full screen at power-on, playing images and MP4 files from microSD or USB with no network and no subscription. The newer wall, counter and floor range is quoted per project, with its software confirmed in the quote.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.