My solution is hosted in FMS on a Mac and there are a couple of Windows 10 clients. Some layouts include container fields set up to display PDF files (optimized for interactive content). Those pdf files are stored externally in the server but clients run the solution through a local file.

Under Mac it's all right, but under Windows 10 it's a nightmare: it happened before, suddenly those PDFs don't display and it all seems caused by a software update (I can't tell if it's Windows 10 or Adobe Reader). The error message comes from Reader: "There is a problem with Adobe/Reader. If it is running, please exit and try again. (507:507)" it is not running alone, only through FileMaker.

I remember once I fixed it by downgrading Reader to an older version but this time it doesn't work.

So I thought of displaying them through a web viewer instead of a container field, I set it up this way: 

"data:application/pdf;base64," & Base64Encode (myFile::pdfContainer)

This works in Mac but not in Windows, I conclude that there is no difference between using a web viewer or an interactive container, the problem seems to be Adobe Reader.

Do you know of a robust solution to display those PDF files stored in container fields in Mac AND Windows?

see

Windows updates breaks PDF display in FileMaker