When adding an image to a Text Area, the content of the image gets converted to png and embedded in the analysis file.
The extension of the file is however kept intact in the links that later as used for the Web Player.
This have the effect that internet Explorer uses this file extension and tried to decode the content as the file extension (e.g. as JPEG if the extension is .jpg).
If you have the console open you will be able to see errors like this:
DOM7009: Unable to decode image at URL: 'https://spotfireserver.testdomain.local:8080/spotfire/wp/render/waIjgvQ5q9z-sRfHAD/GetImage.ashx?waid=z8eqAz_rWkCDZwzLC_ozP-2614337e18G5mc&wavid=0&wvid=0a9beafa-8fc7-4364-ae23-03f95423c259&args=d193b15e7d8d43fbadc09a24306d66ae.jpg'.
Chrome however looks at the content type header instead to figure out what the type it is, that is the reason Chrome does not complain.
The reason this happens is that the Spotfire Server sends a header to prevent analysis of the content:
X-Content-Type-Options nosniff
The reason for this is to make sure the content is read as the type the server sends it as (to prevent some attacks). So removing this to make IE11 work nicely again is not the right solution.