Disabling Flash Update Notification through VbScript

Introduction : The AutoUpdate Notification for Adobe Flash can only be disabled by creating a UTF-8 encoded text file named mms.cfg in the appropriate folder. In this post, we will go through the steps of creating the mms.cfg file, creating a VbScript to copy the file, and a GPO (Group Policy Object) to deploy the solution.

Part 1: Creating mms.cfg 

The file mms.cfg controls many aspects of flash. Today, we will be focusing soley on disabling the AutoUpdate feature. For the other commands that can be added, please visit the Adobe Administration Guide (Chapter 4). Ok, lets get started.
  1. Open Notepad
  2. Type in the following line “AutoUpdateDisable=1”



  3. Save the File. Name the file mms.cfg and change the encoding to UTF-8 
    Important : This will not work unless it is in UTF-8 ecoding. 
    Save File as : Name - mms.cfg Encoding - UTF-8

    Save File as : Name - mms.cfg Encoding - UTF-8

  4. Copy the file to a network share. (This is needed for the script to run).

Part 2 : Creating the Script 

Depending on the operating system, the mms.cfg file will need to be copied in to a specific place. Below is a listing of the various locations:

  • Windows NT, 2000— C:\WINNT\System32\Macromed\Flash
  • Windows XP, Vista —C:\WINDOWS\System32\Macromed\Flash
  • Windows 95, 98, or ME–C:\Windows\System\Macromed\Flash
  • Windows 7, Vista 64-bit — C:\Windows\SysWOW64
  • Copy the following code into Notepad. On line 5, insert the location of mms.cfg on the network share inside the quotes. Save it as DisableFlashNotification.vbs

    '====Disable Flash Notification VbScript=====
    'Location of mms.cfg on network share
    dim mmsConfigFile
    mmsConfigFile = "!!!INSERT NETWORK SHARE PATH FOR mms.cfg FILE!!!"
    '_________Do not edit below this line___________________________
    'File System Variables
    dim filesys
    set filesys=CreateObject("Scripting.FileSystemObject")
    'Create array of all places that mms.cfg can be.
    dim flashLocArray(4)
    flashLocArray(0) = "C:\WINNT\System32\Macromed\Flash\" 	 'Windows NT, 200
    flashLocArray(1) = "C:\WINDOWS\System32\Macromed\Flash\" 'Windows XP, Vista
    flashLocArray(2) = "C:\Windows\System\Macromed\Flash\"	 'Windows 95, 98, ME
    flashLocArray(3) = "C:\Windows\SysWOW64\"		 'Windows 64bit
    'Check to see if mms.cfg file exists
    If filesys.FileExists(mmsConfigFile) Then
    	For Each location in flashLocArray
    	flashCopyFile location, mmsConfigFile
    End If
    '==== Function Copy File =======================
    Function flashCopyFile(strLocation, mmsConfigFile)
    dim filesys
    set filesys=CreateObject("Scripting.FileSystemObject")
    	If filesys.FolderExists(strLocation) Then
    	Const OverwriteExisting = True
    	filesys.CopyFile mmsConfigFile, strLocation, OverWriteExisting
    	End if
    End Function
    '==== END Function Copy File ===================

    NOTE: This script works great on the many flavors of Windows when deployed through Group Policy. If the script is started manually on Windows 7 64bit, the script will crash. This happens due to insufficient rights to copy a file to the C:\Windows\SysWOW64 folder. Only Windows 7 64bit has this problem when ran manually. If deployed through a GPO (Group Policy Object), the script will function nicely regardless of the client operating system (include Windows 7 64bit).

    Part 3: Creating a GPO to deploy the script

    1. Start Group Policy Management
    2. Right Click on Group Policy Objects and click New

      Create a new GPO

      Create a new GPO

    3. Type in a name. This example used “Disable Flash Update Notification”

      GPO Title

      GPO Title

    4.  Expand the Group Policy Objects and right click on the newly created GPO “Disable Flash Update Notification” and click Edit.
    5. Click on Computer Configuration,  Policies,  Windows Settings,  Scripts (Start/Shutdown)

      Group Policy Management Editor

      Group Policy Management Editor

    6. Double click on Startup
    7. Click Add

      Startup Properties

      Startup Properties

    8. Click on Add
    9. Paste the DisableFlashNotification.vbs into the window so the screen looks like the picture below. Once the file has been pasted, click open.

      Upload Script into the GPO

      Upload Script into the GPO

    10. Click Ok on all following windows.
    11. Apply the GPO to the appropriate OU (Organizational Unit).

    Summary :

    The only way to test if this is working is to use a packet sniffer. Flash does have a settings manager; however, it will not reflect the changes made inside the mms.cfg. Using a packet sniffer to test this is beyond the scope of this article, and it is a very cumbersome process. Directions on how to do this can be found here at Adobe’s website. I have found it best to look inside the various Window’s directories to see if the mms.cfg was copied over. Please ask questions in the comments below.

    About Constantine Krick

    Once a teacher, now a word press blog
    This entry was posted in Computer, Computers. Bookmark the permalink.

    5 Responses to Disabling Flash Update Notification through VbScript

    1. Mike Eller says:

      Followed the instructions exactly….but the mms.cfg file does not get copied to the client machine. Can you provide any troubleshooting advice?

    2. OdgeUK says:

      Does this script terminate if MMS.CFG already exists?

    3. If the script finds mms.cfg, it will not copy it again and the script will continue to run. Let me know if there is anything else. ~Constantine

    4. Ben Krause says:

      Is there not a way to make the script create the mms.cfg file and add the appropriate values? I think that would be easier than having to store a file on a network location to copy over.

    5. I opted for the network location as it would keep the code concise. Also, creating the required UTF-8 config file requires some non standard VbScript. Please check the following link for code that will generate the UTF-8 file in VbScript.

    Leave a Reply

    Your email address will not be published. Required fields are marked *