Skip to main content
chrisi87781579
chrisi87781579
Participating Frequently
May 7, 2018
Question

Flash Plugin 29.0.0.113 not honoring AutoUpdate settings in mms.cfg file

  • May 7, 2018
  • 1 reply
  • 1365 views

We deploy the Flash Plugin to about 250 machines in our environment.  We use Group policy to place a mmc.cfg file containing the line AutoUpdateDisable = 1 to either c:\windows\system32\macromed\flash or c:\windows\sysWOW64\macromed\flash depending on the target machine's architecture.  We have deployed the plugin and the mms.cfg file in this manner since November of last year with no problems.

Beginning with version 29.0.0.113, when version 29.0.0.140 was released we started getting reports from users that they were getting prompted to update to the new version of Flash that we hadn't deployed yet.  I have checked with a few of those users and verified that they have the mmc.cfg file in the proper location, but they are still getting auto-update prompts.  This is a big problem for us, as our users do not have admin rights so they are unable to update and unable to clear the pop-up prompt to update.  As a result, our Help Desk is getting calls that they can't resolve, and we (third-tier support) can't resolve it either.

Why is 29.0.0.1113 not honoring the settings in the mms.cfg file, and what do we need to do to resolve this?

    This topic has been closed for replies.

    1 reply

    _maria_
    _maria_
    Legend
    May 7, 2018

    This is a known bug only in 29.0.0.113 where the auto-update settings in mms.cfg file are not honored if the file is saved in UTF-8 w/BOM.  The work-around is to save the mms.cfg file as ANSI format. The bug was fixed in 29.0.0.140, so once 29.0.0.140 is installed the bug should not reproduce if the file is saved w/BOM format.

    D
    Dave0034
    Participant
    May 10, 2018

    I have just deployed Adobe Flash Player 29.0.0.171 to my test machines and it has changed the setting again to AutoUpdateDisable=0 just after we corrected this when 29.0.0.113 was deployed. 29.0.0.140 was fine and kept our setting intact but not 29.0.0.171. Will this be fixed soon as I can't keep deploying the updates if the setting doesn't stay the same?

    _maria_
    _maria_
    Legend
    May 10, 2018

    Which installer (EXE or MSI) are you using?

    Which Flash Player types (ActiveX, NPAPI, PPAPI) do you deploy?

    How do you normally deploy Flash Player?

    Please provide the following files:

    • mms.cfg file you normally deploy
    • mms.cfg file after the update (the one where AutoUpdateDisable changes)
    • FlashInstall log file(s) from an impacted system, saved at the following location:
      • 32-bit OS: C:\Windows\System32\Macromed\Flash\FlashInstall32.log
      • 64-bit OS: C:\Windows\System32\Macromed\Flash\FlashInstall64.log AND C:\Windows\SysWOW64\Macromed\Flash\FlashInstall32.log - both files are required from a 64-bit OS

    Upload the files to cloud.acrobat.com/send (seeHow to share a file using Adobe Document Cloud ) or some other file sharing service of your choice that doesn't require user login to access.  Post the link to the uploaded files in your reply.

    Thank you.

    --

    Maria

    Firefly Community Gallery
    Adobe Firefly

    Remix with Firefly Community Gallery

    Thousands of free creations to fall in love with and remix in Firefly.

    Explore now
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices