Locked

Flash Player prompted me to install an update despite having AutoUpdateDisable=1 in mms.cfg

Explorer ,
Apr 12, 2018 Apr 12, 2018

Copy link to clipboard

Copied

Hi all,

I got the prompt to install an update for Flash Player Plugin on my workstation this morning despite having an mms.cfg file in C:\Windows\SysWOW64\Macromed\Flash with AutoUpdateDisable=1 as its only contents (UTF-8 encoded with a BOM). Is anyone else seeing this issue?

The installed version of Adobe Flash Player 29 NPAPI is 29.0.0.113. I'm on a machine running Windows 10 x64 version 1709.

Thanks!

TOPICS
Download install

Views

787

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct Answer

Adobe Employee , Apr 12, 2018 Apr 12, 2018
There was a bug in the update workflow with mms.cfg files encoded in UTF-8.  This was fixed in 29.0.0.140, released yesterday.

Likes

Translate

Translate
Adobe Employee ,
Apr 12, 2018 Apr 12, 2018

Copy link to clipboard

Copied

There was a bug in the update workflow with mms.cfg files encoded in UTF-8.  This was fixed in 29.0.0.140, released yesterday.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 12, 2018 Apr 12, 2018

Copy link to clipboard

Copied

Thanks Maria, much appreciated.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 12, 2018 Apr 12, 2018

Copy link to clipboard

Copied

you're welcome.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 18, 2018 Apr 18, 2018

Copy link to clipboard

Copied

We are having the issue in version 29.0.0.140.  The ActiveX works, but not the NPAPI for version 29.0.0.140.  It resets the custom MMS.CFG with the default. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 18, 2018 Apr 18, 2018

Copy link to clipboard

Copied

LATEST

ActiveX and NPAPI (and PPAPI) have two different Notification Update workflows, and the bug is present in the NPAPI & PPAPI Notification Update workflows.

If you're experiencing the behaviour (assuming it's the same root cause) in NPAPI, it's in version 29.0.0.113, not 29.0.0.140, as NPAPI version 29.0.0.113 is the version installed on the system performing the update, not 29.0.0.140, which was just released, and therefore won't be performing an update until the next release.

<edited>

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines