I realize this scenario has been on shaky ground for some time, but we have an application that does not run on an intranet, that requires the hosting of a .NET control to interact with some hardware that is not supported through browser API's. We are in the process of rewriting this application from scratch, but it has taken longer than expected. In the meantime we have to support the existing application.
We have so far always been able to work around changes to IE that interfered with the ability to host the .NET controls, but this latest update so far has us stumped. We can put our site in compatibility mode, and it will work. At least one of our customers has indicated that this is not an acceptable solution so we are trying to work around it. Specifying an X-UA-Compatible meta tag on the page also works, but only if we push the mode all the way to IE=7. Previous to this recent change on Windows 10 anniversary update we could run without specifying a legacy document mode or a setting the URL up in compatibility mode in the browser.
Can someone explain to me what was changed? Are there other settings that allow us to work around this problem? Is there any way to make this work while specifying IE=10 as the document mode so the rest of the page doesn't have rendering issues?