IMHO: They pay, and they sure have the right to add something like "region lock" or "activation check". What is crossing the red line is to add "HelperService, which displays ads" or "Service, which phones home with system info". That is malware and that isn't right. BTW: Is there anything newer than KB4580325, ActiveX v32-0-0-445 via WU? Non-ActiveX and ActiveX for W7 is v32-0-0-465. Also by comparing the same version: ActiveX for W10 and W81 distributed via WU are different from ActiveX for W7 distributed via installer.exe.
Flash v32-0-0-445 IE ActiveX Patched arm32 This replaces the KB4580325 arm32, it is the latest available arm32 version, patched and resistant to removal via CUs. (It can be easily re-applied.)
Flash v32-0-0-445 IE ActiveX Patched arm32OS and x32OS I can't help myself and stop playing with it. Now the thing covers arm32OS and x32OS. 64-bit OSes will be the next step. It will go hand in hand with my "Recover IE" pack" for W11.
LOL: \HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes Too many obsolete substitutions and redirects. Also: a) classes like: \HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.sor \HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MacromediaFlashPaper.MacromediaFlashPaper \HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MIME\Database\Content Type\application/futuresplash ...never have double key in WOW6432Node, b) classes like: \HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\FlashUtil_ActiveX.exe \HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B019E3BF-E7E5-453C-A2E4-D2C18CA0866F} \HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{299817DA-1FAC-4CE2-8F48-A108237013BD} \HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{57A0E746-3863-4D20-A811-950C84F1DB9B} ...always have double key in WOW6432Node; c) while in .Manifest nearly everything (every key) is doubled (between x64 and x32 - only one key for x32 CPL.exe isn't) and also everything (x64 and x32) is viewed as it would be the main architecture (so there is always \HKEY_LOCAL_MACHINE\SOFTWARE\Classes and never \HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node in .Manifest even for wow64). Also, Adobe is stupid, as it writes values using HKEY_CLASSES_ROOT (merged-view-substitution), so value can be written either to HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER depending on if the key already exists (in HKEY_CURRENT_USER). Anyway, it is experiencing to dig into it.
Thanks, that Windows is so tolerant (and maybe it even actively searches for those files), because otherwise it wouldn't even run: [HKEY_CLASSES_ROOT\WOW6432Node\TypeLib\{57A0E746-3863-4D20-A811-950C84F1DB9B}\1.1\0\win32] @="C:\\Windows\\System32\\Macromed\\Flash\\Flash.ocx\\2" [HKEY_CLASSES_ROOT\WOW6432Node\TypeLib\{D27CDB6B-AE6D-11CF-96B8-444553540000}\1.0\0\win32] @="C:\\Windows\\System32\\Macromed\\Flash\\Flash.ocx" [HKEY_CLASSES_ROOT\WOW6432Node\TypeLib\{FAB3E735-69C7-453B-A446-B6823C6DF1C9}\1.0\0\win32] @="C:\\Windows\\System32\\Macromed\\Flash\\FlashUtil_ActiveX.exe" [HKEY_CLASSES_ROOT\WOW6432Node\TypeLib\{FAB3E735-69C7-453B-A446-B6823C6DF1C9}\1.0\HELPDIR] @="C:\\Windows\\System32\\Macromed\\Flash\\FlashUtil_ActiveX.exe" [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Control Panel\Extended Properties\System.ControlPanel.Category] "C:\\Windows\\system32\\FlashPlayerCPLApp.cpl"=dword:0000000a