Some more observations, as result from testing on my Vista SP2 32-bit laptop:
1. The mms.cfg method with LATEST Flash 32.0.0.465 (unmodified) will work ONLY when that file is located in its designated location (for me it's "C:\Windows\system32\macromed\Flash\") and it will ONLY be observed/honoured by the ActiveX and NPAPI varieties...
My file currently reads:
DisableAnalytics=1
SilentAutoUpdateEnable=0
AutoUpdateDisable=1
EOLUninstallDisable=1
EnableAllowList=1[ignored]
AllowListRootMovieOnly=1
AllowListUrlPattern=file:*
AllowListUrlPattern=https://wwwimages.adobe.com/
AllowListUrlPattern=https://helpx.adobe.com/
AllowListUrlPattern=*://chat.kongregate.com/
AllowListUrlPattern=*://www.screamingstatue.com/
with
SilentAutoUpdateEnable=0
AutoUpdateDisable=1
probably being redundant now...
The NPAPI dll will read mms.cfg whether it's properly installed (in "%windir%\system32\macromed\Flash\") or from another "portable" location; the PPAPI dll, however, will NOT read mms.cfg no matter if it's properly installed (for Chromium browsers that don't bundle Flash) or itself part of Google Chrome (inside the appdir or userdatadir).
What was somewhat not expected by me is the fact a patched NPAPI dll (e.g. "NPSWF32_32_0_0_465.dll"), regardless of location, will STILL observe mms.cfg ; so, if you have patched the NPAPI dll to remove the killswitch/timebomb, for it to work on ALL sites you'll have to rename/remove/delete your customised mms.cfg file!
["%SystemDrive%\Users\<username>\AppData\Local" = "%localappdata%" ]
Under Vista SP2 32-bit [No ExtKernel], the highest version of Google Chrome that can launch is the first build of the 51 branch, v51.0.2679.0 (a hard-to-find release, it was shared long time ago by a fellow MSFN member in the Vista subforums...); I have it set up as a portable installation in the PAF format, so the folder hierarchy is
G:\PortableApps\GoogleChromePortable\GoogleChromePortable.exe [=launcher]
G:\PortableApps\GoogleChromePortable\App\Chrome-bin\chrome.exe [=main .exe]
G:\PortableApps\GoogleChromePortable\App\Chrome-bin\51.0.2679.0\PepperFlash\pepflashplayer.dll [=originally bundled PPAPI Flash, v21.0.0.182]
G:\PortableApps\GoogleChromePortable\Data\profile\PepperFlash\32.0.0.465\pepflashplayer.dll [=manually updated PPAPI Flash, located inside User Data dir, aka "profile"]
With the last PPAPI v32.0.0.465 in place as detailed, Chrome 51 ignores the built-in old 21 version (which, obviously, does not contain a timebomb) and loads v32; but the DLL does not read mms.cfg file (if present), so I always get the following outcome:
For latest PPAPI Flash to work inside Google Chrome (tested versions 49/50/51), I have to use a patched DLL:
FTR: