![]() We do try to fix it when we break content, but there are significant architectural changes with Windows 8 and higher (there is *no* ActiveX interface in IE/Edge on Win8+, which is why we're not a standalone product on those platforms) that significantly increase complexity. I would also add that Adobe AIR is the supported vehicle for developing desktop applications using Flash technology, and that embedding Flash content in C++ applications is not a use-case that we directly test or support. ![]() It sounds like you need to re-think your app deployment strategy for Windows 8.1 and Windows 10 customers to take into consideration the fact that Flash Player ActiveX is a component of the OS and assume that the latest version is always installed (especially on Windows 10 where a user cannot disable Windows Updates). Since Flash Player ActiveX is embedded in the browser all ActiveX Control updates are released by Microsoft via Windows Updates (as an IE and/or Edge update). Microsoft has been embedding Flash Player in IE since Windows 8.1, and Edge since the Windows 10 release. The only way to 'fallback' is to uninstall the update that installed 26.0.0.151, but it'll be re-installed again. But if target machine has version 26.0.0.151 there is no way to fallback to version 137. Flash Player is a component of IE and Edge, therefore, whenever IE or Edge are updated, the version of Flash Player is also updated.įor win 10 we can ship windows update package KB4025376 as flash 26.0.0.137 installer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |