We run an internal web application which makes use of the Microsoft Forms 2.0 TabStrip as an ActiveX control.
This has worked perfectly fine year after year, until recently.
A recent update Office Security update from March 2015 (KB2920813) results in the active x failing to load (users just see a red x).
Uninstalling the update solves the problem.
This was fine until another Office Security Update on 12th May (KB2965291) resulted in exactly the same outcome. Again, uninstalling the update resolved the issue.
Both updates make some loose mention of ActiveX security flaws.
The web page is referencing the ActiveX ClassID of EAE50EB0-4A62-11CE-BED6-00AA00611080.
Was it the intention of the security updates to disable/block the execution of this ActiveX? And if so, is there another class id which should be used instead, or a permanent workaround (one which won't be reversed by a future update)?
Windows 7 Enterprise SP1
Office 2010 Professional
Internet Explorer 9
Other recent topics
