Ok. But I think it's reasonable to ask why flight arrival information displays have to run Windows. And even if they have to run Windows why not some embedded ROM-boot library kiosk version? Why does a sign need to have a fully featured desktop OS?
(I have a picture of said sign displaying its blue screen lest anyone think I'm making this up).
Best answer I can guess: because it's easy and cheap to set up, and the dev team involved was moved to another project years ago.
Windows is dominant for UIs because of a long history of having drivers for all the various peripherals which eases hw procurement issues. Sure that advantage went away long ago but the momentum takes a long time to die out. The brains with the expertise know how to do it on Windows. Combine that with the fact that Windows UI is not something you have to train new hires on and it makes business sense that all the user-facing interfaces ended up Windows applications. Sure, over time they should be migrated to containerized web UIs, but there's a lot of work to be done. Updating the flight arrival display isn't mission critical; it's at the end of the backlog.
I believe I heard one thing that got screwed up was a crew-scheduler product. Like: they couldn't check in crews or get their schedules written in so a system (presumably something on a mainframe) could work out where all the people needed to be at what times. Much more mission critical! The central big brain was (probably) not Windows, but those user inputs at the end were enough to screw up the whole business process.
Maybe because airline traffic is a hard business (airlines make cents per passenger per flight).
And thus airports are pressured by airlines to minimize costs. In the end, the answer is probably, that it's just cheaper to use windows than to invest any more effort into the task.
(I have a picture of said sign displaying its blue screen lest anyone think I'm making this up).