Re: [NTSysADM] Chrome 54 and Flash

2017-07-14 Thread Micheal Espinola Jr
Thanks again for following-up! -- Espi On Fri, Jul 14, 2017 at 11:11 AM, Richard Stovall wrote: > Following up on the follow up. > > This has finally been fixed as of SEP 14 MP1 (MP2 is current.) > > From https://support.symantec.com/en_US/article.INFO4193.html > > --- > Chrome Adobe Flash co

Re: [NTSysADM] Chrome 54 and Flash

2017-07-14 Thread Richard Stovall
Following up on the follow up. This has finally been fixed as of SEP 14 MP1 (MP2 is current.) >From https://support.symantec.com/en_US/article.INFO4193.html --- Chrome Adobe Flash component fails to update with SMC started*FIX ID:* 4050141 *Symptom:* Chrome fails to update the Adobe Flash com

Re: [NTSysADM] Chrome 54 and Flash

2017-01-17 Thread Richard Stovall
It was making me more than a little crazy, and I don't have far to reach the end of that road as it is... :) On Mon, Jan 16, 2017 at 8:47 PM, Micheal Espinola Jr < michealespin...@gmail.com> wrote: > WOW, just... wow. Thanks for the follow-up on this! > > -- > Espi > > > On Mon, Jan 16, 2017 a

Re: [NTSysADM] Chrome 54 and Flash

2017-01-16 Thread Micheal Espinola Jr
WOW, just... wow. Thanks for the follow-up on this! -- Espi On Mon, Jan 16, 2017 at 8:02 AM, Richard Stovall wrote: > For anyone else that may be seeing the Flash update issues in Chrome. If > you're using SEP, this may be your issue. > > https://bugs.chromium.org/p/chromium/issues/detail?i

Re: [NTSysADM] Chrome 54 and Flash

2017-01-16 Thread Richard Stovall
For anyone else that may be seeing the Flash update issues in Chrome. If you're using SEP, this may be your issue. https://bugs.chromium.org/p/chromium/issues/detail?id=651945 - Symantec has confirmed that this is a known issue. Below is their response to our case. After reviewing this

Re: [NTSysADM] Chrome 54 and Flash

2016-10-31 Thread Micheal Espinola Jr
Right, for which if I understand the process correctly, you are dependant on Google Updater to update various components after the fact - that are not a part of the core application update. So, you may have download restrictions in place that are preventing the update of the flash component. This

Re: [NTSysADM] Chrome 54 and Flash

2016-10-31 Thread Richard Stovall
Well, this pretty much explains what I'm seeing. https://forums.adobe.com/thread/2221587. On Mon, Oct 31, 2016 at 6:23 PM, Micheal Espinola Jr < michealespin...@gmail.com> wrote: > I cant speak for Ninite-driven upgrades, but have you tested Google > Updater driven upgrades? Perhaps the issue i

Re: [NTSysADM] Chrome 54 and Flash

2016-10-31 Thread Micheal Espinola Jr
I cant speak for Ninite-driven upgrades, but have you tested Google Updater driven upgrades? Perhaps the issue is with Ninite, and not Google Chrome itself. Or perhaps you need to review your methodologies inline with your download restrictions. -- Espi On Mon, Oct 31, 2016 at 2:36 PM, Richard

Re: [NTSysADM] Chrome 54 and Flash

2016-10-31 Thread Richard Stovall
Getting back to this. Sorry for the delay... Google is apparently de-emphasizing Flash's use with an eventual plan to drop it completely. (Which I'm all for.) The problem is that it's still alive and well, but updating to Chrome 54.X no longer automatically updates Pepper Flash along with core

Re: [NTSysADM] Chrome 54 and Flash

2016-10-18 Thread Micheal Espinola Jr
Hasn't Chrome started the phase-out of Flash? However, I'm on 54 and I can see Adobe's Flash test page fine. I'm not aware of any Flash update options relating to current versions of Chrome. -- Espi On Tue, Oct 18, 2016 at 5:07 PM, Richard Stovall wrote: > Does anyone know what is really goi