Auto Update of 64 Bit Flash 11 on Vista Turns Zombie

Early this morning there was an update of Flash 11 on my Vista Home Premium system. In this case, it was Flash 11, 64-Bit Plugin. Everything went fine and it completed successfully. However, Flash has disappeared from my system - kind of. It's there and it's not there too.
The graphic below shows that my system thinks Flash 11 is installed. However, nothing can find it including a file/directory search and my browser, which is Firefox in my case. Note that the file size of the plugin install and the Flash 11 player updated a few days ago are now both zero. The Flash help center can't find it either and thinks it's not installed on my system at all.
Anyone else having a similar problem? All components of Flash 11 were working last night before the update.
Cheers,
Lonnie

The answer to the first question is that the Abobe help site does not see anything installed for Flash. That is, the box is empty as if you have noting installed.
Here are the visual answers to the System32 and SysWOW64 questions:
Obviously, they are not empty, but noting in the OS or the Adobe help site sees the content here.
Thanks for responding.

Similar Messages

Lack of weekly auto-update prevents installation of Flash 11.7

Previously every Monday, I would get a prompt to update Flash Player on start-up. Click okay, it would remind me that I'm doing this manually, then it would automatically update the version. Done in five minutes.
For 2 weeks I've come in, and the Download button not only opens a browser(!) but asks for the re-download procedure on http://get2.adobe.com/flashplayer/ -- which I have in the past reported to be inoperable for me. The downloaded exe will fail to initialize no matter if all my anti-virus and firewalls are down. Which is dangerous in the first place. You can read all my other discussions on the matter. I do have administrative access, I have been through the checklist scores of times. Let me reiterate: there is no other way to download a new version of Flash other than to use the automatic update. There were no issues with the automatic update in the past. If you're pushing security updates on us, eliminating the auto-update is not ideal. Windows XP, latest Firefox.

tagsulat wrote:
Let me reiterate: there is no other way to download a new version of Flash other than to use the automatic update.
I do not quite understand this; can you elaborate?

ANN: Javascript utility to make auto-updating apps a bit easier

I'm new around here, apologies if this isn't the right place
to post this.
I had to make a few separate AIR apps recently
(HTML/Javascript) that would each be capable of auto-updating
themselves (check a website for new version, if so download &
install). I put something together that lets me do this with a
small amount of code & uploaded it to Google Code to share:
air-simple-updater.
Hopefully it can save at least someone a few minutes... :)

Douglas --
Back in OS 8.6, I used to create folders to keep similar apps together, too. I also used to "clean up" fonts a lot.
After deleting several System fonts and rendering my Mac useless, I decided to stop cleaning up. If you can arrange them in Launchpad, good. But don't go rearranging apps in the Applications folder, OK? Updates will not work if you put apps within a self-created folder.

Flash player silent auto update not working

I was glad to read the news about the new feature of silent auto updates of the Adobe Flash player, but unfortunately this is not working on my machine. Has anyone had the same problems and was able to solve them?
Some information on my setup:
I had previously installed Flash player version 11.1.102.63, both ActiveX and Plugin version (installed through the .msi files, deployed via Active Directory/GPO - no further configuration, just plain original .msi files).
To test the auto update feature, I decided to install the new 11.2.202.228 version, but only the ActiveX version. I installed this via the .exe installer (install_flash_player_11_active_x_32bit.exe) manually, choosing "Install updates automatically when available (recommended)" in the last step of the installation, as seen here:
http://www.adobe.com/devnet/flashplayer/articles/background-updater-windows.html
When I open Control Panel -> Flash Player, under the "Advanced" tab I see:
"Install updates automatically" is chosen, but greyed out (no admin rights with this windows user)
ActiveX version: 11.2.202.228
Plug-In version: 11.1.102.63
The file "mms.cfg" under C:\WINDOWS\system32\Macromed\Flash\ contains:
AutoUpdateDisable=0
SilentAutoUpdateEnable=1
The task "Adobe Flash Player Updater" was created and is scheduled to run every 1 hour. I can see that it is started ("last start time"), the result code is 0x0 which means "no error".
So everything as expected. But the auto update is not working, since the plugin version of flash player never gets updated!
I edited the "mms.cfg" and added:
SilentAutoUpdateVerboseLogging=1
After manually starting the task, there are some lines added to "FlashInstall.log" in the same directory:
2012-4-4+7-20-48.814 [info] 1614
2012-4-4+7-20-48.829 [info] 1615
2012-4-4+7-20-48.829 [info] 1618
2012-4-4+7-20-48.829 [info] 1619 1063
2012-4-4+7-20-48.876 [info] 1614
2012-4-4+7-20-48.876 [info] 1615
2012-4-4+7-20-48.876 [info] 1618
2012-4-4+7-20-48.876 [info] 1608
2012-4-4+7-20-48.876 [info] 1604
2012-4-4+7-21-10.425 [warning] 1403 12029
2012-4-4+7-21-10.425 [warning] 1407 183
2012-4-4+7-21-10.425 [warning] 1408
2012-4-4+7-21-10.456 [info] 1624
2012-4-4+7-21-10.456 [info] 1612
2012-4-4+7-21-10.456 [info] 1621
What does this mean?
Some more information:
Windows XP SP3, all windows updates installed, german
Avira Professional Security anti-virus software
Machine is behind a proxy server, but this is set up in Control Panel -> Internet Options
I suppose this is a problem with our proxy server. Does the auto updater not use the proxy information from the Windows Control Panel settings?
Kind Regards,
Martin

Hey Hans,
After reading of your sucsess I attempted to replicate it.
I am happy to say that I managed to update from Adobe Flash 11.2.202.228 to 11.2.202.233 on serveral different windows 7 notebooks and desktops sliently.
I went into the windows task scedular and ran the Adobe Flash Player Updater task (I didn't need to change anything in the task or the service for it to work).
The only issue I found was that if I ran the task again without restarting the computer no requests from the client would show up in the logs from my web server but if I restarted my computer and then reran the task it would work again. I'm assuming that it will only sent requests out every 24hours is talked about in page 18 of the Flash Player 11.2 Administration Guide.
My Web Servers logs look like this:
2012-04-27 05:45:01 W3SVC1967680676 10.135.12.38 GET /pub/flashplayer/update/current/sau/11/xml/version.xml - 443 - 10.135.13.17 Get+Flash+Player+version+xml/1.0 200 0 0
2012-04-27 05:45:05 W3SVC1967680676 10.135.12.38 GET /pub/flashplayer/update/current/sau/11/install/install_all_win_ax_sgn.z - 80 - 10.135.13.17 Download+Flash+Player+Installer/1.0 200 0 0
My mms.cfg looks like this:
AutoUpdateDisable=0
SilentAutoUpdateEnable=1
SilentAutoUpdateServerDomain=proxy.tallangatta-sc.vic.edu.au
I think the biggest issue I had during testing was that I forgot to my web servers certificate into the windows certificate stores trusts root certs of my notebooks/desktops. EG: http://blogs.adobe.com/livecycle/2012/04/rights-management-how-to-get-windows-7-to-trust-a -self-signed-server-certificate.html
I have since deployed the mms.cfg file and added my web servers certificate into the trusted root certs via group policy to all my clients and it is working very well. I have also writen a batch file to download the needed files from adobe for that backgroup updater and to put them on my web server. I created a daily task on my web server to run the batch file. If anyone wants the batch file or shell script please email me and I'll forward it on.
My batch file pretty much looks like this:
@echo off
:::::::::: INFOMATION ABOUT SCRIPT ::::::::::
:: This Script Titled adobe-flash-background-updates and was written by Tyrone Wyatt of www.cloudportal.org.
:: This Script is open to use by everyone and is not under any licence.
:: See flash_player_11_2_admin_guide.pdf for more infomation on how this script is required to function.
:::::::::: SCRIPT CONFIG ::::::::::
:: The TITLE option is the scripts name
set TITLE=adobe-flash-background-updates
:: The LOG option is the log file.
set LOG=./%TITLE%.log
:: The SOURCE option is the mirror on which you would like to download the flash files from.
set SOURCE=http://fpdownload2.macromedia.com
:: The DESTINATION option is where you would like your downloaded files to go so they are accessable by your web service.
set DESTINATION=d:\wwwroot\Proxy
:: The VERSION option is the current major version of Flash Player (for Flash Player 11.2, the major version is 11).
set VERSION=11
:: The Proxy settings for wget to use
set HTTP_PROXY=http://edupass.tallangatta-sc.vic.edu.au:8080
:::::::::: SCRIPT CORE ::::::::::
echo Welcome to %TITLE% Script!
echo =O====== %date% %time% ======== >> %LOG% 2>&1
if exist %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\xml (
echo Skipping destination folder structure creation.
) else (
echo Creating destination folder structure.
mkdir %DESTINATION%\pub >> %LOG% 2>&1
mkdir %DESTINATION%\pub\flashplayer >> %LOG% 2>&1
mkdir %DESTINATION%\pub\flashplayer\update >> %LOG% 2>&1
mkdir %DESTINATION%\pub\flashplayer\update\current >> %LOG% 2>&1
mkdir %DESTINATION%\pub\flashplayer\update\current\sau >> %LOG% 2>&1
mkdir %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION% >> %LOG% 2>&1
mkdir %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\xml >> %LOG% 2>&1
mkdir %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install >> %LOG% 2>&1
echo Downloading files...
wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/xml/version.xml -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\xml\version.xml >> %LOG% 2>&1
wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install_all_win_ax_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\install_all_win_ax_sgn .z >> %LOG% 2>&1
wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install_all_win_pl_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\install_all_win_pl_sgn .z >> %LOG% 2>&1
wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install_all_win_64_ax_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\install_all_win_64_ax_ sgn.z >> %LOG% 2>&1
wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install_all_win_64_pl_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\install_all_win_64_pl_ sgn.z >> %LOG% 2>&1
echo Script complete! See log file for more infomation %LOG%
echo =X====== %date% %time% ======== >> %LOG% 2>&1
echo. >> %LOG% 2>&1
:::::::::: END OF SCRIPT ::::::::::
Thanks for your help,
Tyrone Wyatt.

Auto-update not working on 64-bit Windows Firefox Aurora

I realize the correct directory to download Aurora builds would be http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora-l10n/, but it does not have 64-bit Windows build which is unfortunately the only way to solve severe stuttering problems in Flash.
Previously I had used nightly builds, while they did work fine most of the time sometimes there issues that forced me back to standard builds, and stuttering Flash.
So instead I've been trying to use 64-bit Aurora I downloaded from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora/. It's been a smooth experience otherwise but auto-update doesn't work. First it attempts to install small patch, which fails. Then it tries to install full update, which again fails.
Here's a screenshot of the full update failure message: http://i.imgur.com/8HmPjTE.jpg

Thanks for the feedback. The topic linked above suggests that the problem with auto-update lies with CA certificate. I've submitted feedback to Moziilla and linked here just in case.
If the cause of failing auto-update is the CA certificate, hopefully Mozilla is willing to correct the problem.
Stuttering Flash in 32-bit Firefox is simply unbearable and I have to either use 64-bit Nightly or Aurora builds, or go Chrome.

Must be Auto update flash Player/AIR [No update alert]

Every second day Adobe are improving the flash player and AIR, so Flash Player must be Auto update to newer versions and (Major and minor) [No update alert]. It should auto check, and auto download and auto update the flash player. There should not be any user interaction needed. And no administration rights as Flash player is already installed on system, Adobe is just auto updating it. So no alert or dialog box to update player just auto update with out any message as Google Chorme is doing right now (Google chrome update the browser application without any alert to user). So Please follow it.
Why it's required: Every second day Adobe programmers are improving and adding new features, but Flash/Flex developers around the globe can not use those features as their target customers (users) don't have the updated version of flash player/AIR. We can show the alert but we know most of users pick the "NO" as their preferred option.
How can Adobe implement this, there are privacy issue: Adobe can implement this by changing their Adobe flash player agreement (for new installations). They can add one "Flash player policy" web page to their website and link at their home page. Adobe can add one more menu element in their setting tab (right click flash player menu). It's will take little time but for future, it will be really easy for developers to adopt the new feature and software from Adobe.
Please think about it.

Hi ersatyle,
Thanks for clarifying.
will flash player be automatically updated while a standard user is connected (no admin rights) and without any notifications.
By pointing the Background Updater to an internal server, yes.
Are those settings will work as I intended?
The AutoUpdateInterval setting in the mms.cfg has no effect on the Background Updater. AutoUpdateInterval can only be used for the notification updater. If you're setting up background updates from an internal server, this property is best dropped from the mms.cfg to avoid confusion. The other settings will work as expected. Once you have your clients set up and tested, I also recommend dropping SilentAutoUpdateVerboseLogging, since this will reduce the size of the log file.
As we'll use 32 bits browsers do I need to put the mms.cfg file also in c$\Windows\System32\Macromed\Flash, If it wont work, is it doable?
There is only one location for the mms.cfg. The same file is used for 32-bit and 64-bit browsers. From the administration guide, page 22:
mms.cfg file location:
Assuming a default Windows installation, Flash Player looks for the mms.cfg file in the following system directories:
•32-bit Windows - %WINDIR%\System32\Macromed\Flash
•64-bit Windows - %WINDIR%\SysWow64\Macromed\Flash
Note: The %WINDIR% location represents the Windows system directory, such as C:\WINDOWS.
I hope this answers your questions. Let us know if there's anything else.
-Stephen

Air Auto Update Error -- Flash Builder Burrito.

This is my first attempt at this, so I may be missing something simple.
I'm not having any luck getting an Air app to automatically update.
If I manually go to http://localhost/air1/air1.air and redownload the file I will get a popup that asks if I want to update the app, but when I say ok I get this error.
"There was an error checking for updates. Error# 16816"
I haven't found a reason yet,
Any ideas?
update.xml
<?xml version="1.0" encoding="UTF-8"?>
<update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
<version>2.0</version>
<url>http://localhost/air1/air1.air</url>
<description>1.0 - First version</description>
</update>
file -- air1.mxml
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                       xmlns:s="library://ns.adobe.com/flex/spark"
                       xmlns:mx="library://ns.adobe.com/flex/mx"
                       applicationComplete="init()">
    <fx:Declarations>
        
    </fx:Declarations>
    <fx:Script>
        <![CDATA[
            import air.update.events.UpdateEvent;
            import air.update.ApplicationUpdaterUI;
            import mx.controls.Alert;
            protected var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI(); // Used for auto-update
            protected function init():void
                // Check for update
                this.checkUpdate();
                Alert.show("checking update");
            // This function is triggered when the application finished loading.
            // Initialize appUpdater and set some properties
            protected function checkUpdate():void
                // set the URL for the update.xml file
                appUpdater.updateURL = "http://localhost/air1/update.xml";
                appUpdater.addEventListener(UpdateEvent.INITIALIZED, onUpdate);
                appUpdater.addEventListener(ErrorEvent.ERROR, onUpdaterError);
                // Hide the dialog asking for permission for checking for a new update.
                // If you want to see it just leave the default value (or set true).
                appUpdater.isCheckForUpdateVisible = true;
                appUpdater.initialize();
            // Handler function triggered by the ApplicationUpdater.initialize.
            // The updater was initialized and it is ready to take commands.
            protected function onUpdate(event:UpdateEvent):void
                // start the process of checking for a new update and to install
                appUpdater.checkNow();
            // Handler function for error events triggered by the ApplicationUpdater.initialize
            protected function onUpdaterError(event:ErrorEvent):void
                Alert.show(event.toString());
        ]]>
    </fx:Script>
    <s:Button x="47" y="55" label="Button"/>
    <mx:ColorPicker x="61" y="119"/>
    <s:ComboBox x="77" y="216"/>
    <s:ComboBox x="77" y="185"/>
    <s:ComboBox x="77" y="154"/>
</s:WindowedApplication>
file -- air1-app.xml
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<application xmlns="http://ns.adobe.com/air/application/2.5">

    
    <id>air1</id>
    
    <filename>air1</filename>
    
    <name>air1</name>
    
    <versionNumber>2.0.0</versionNumber>
    
    
    
    
    
    
    
    
    
    <initialWindow>
        
        
        <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
    <autoOrients>false</autoOrients>
    <fullScreen>false</fullScreen>
    <visible>false</visible>
</initialWindow>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        
        
            
            
            
            
            
            
            
            
            
            
        
    
    
    
    
</application>

This appears to be a Flex question. Please try posting to the Flex forums here http://forums.adobe.com/community/flex/flex_general_discussion for better response.

Adobe Flash Auto-update

Adobe's long policy of aggressive auto update lacks the quality one would expect from Adobe.
This is simply because one can be in the middle of a process that can't be interrupted by restarting the computer.
This is specially true of developers or traders as just two categories of users.
Please stop playing forcing people to choosing auto-update Adobe flash. I rather disable Adobe flash permanently than to allow my computer restart whilst i am in the middle of a work process.

See:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=630199 Bug 630199] – Flash crash [@ VP3VideoDecoder_DecodeFrameCompleteCallback ]
''(please do not comment in bug reports; you can vote instead)''

Flash Builder 4.5.1 - Air ApplicationUpdaterUI Auto Update Fails

I just reinstalled my FlashBuilder 4.5.1 and built a new HelloWorld App
in order to test the SDK 2.6 with the Air ApplicationUpdaterUI.
I get no errors but it won't update using the 2.6 namespace in both the -app.mxml and update.xml on server.
A trace in the StatusUpdateEvent never shows up in debug mode.
The only window that pops up is the one asking to Check for Update?
Pulling my hair out - must be something obvious I'm doing wrong here - can a new set of eyes spot something?
Main xml file:
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                       xmlns:s="library://ns.adobe.com/flex/spark"
                       xmlns:mx="library://ns.adobe.com/flex/mx"
                       creationComplete = "checkForUpdate();" title="Test Air Updater">
    <fx:Declarations>
        
    </fx:Declarations>
    <fx:Script>
        <![CDATA[
            import air.net.URLMonitor;
            import air.update.ApplicationUpdaterUI;
            import air.update.events.StatusUpdateErrorEvent;
            import air.update.events.StatusUpdateEvent;
            import air.update.events.UpdateEvent;
            import flash.events.ErrorEvent;
            import mx.controls.Alert;
            import mx.events.CloseEvent;
            import mx.events.FlexEvent;
            private const APP_VERSION_FILE:String     = "http://www.public-knowledge.com/Quest/Timesheets/new_app_version.xml";
            private var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI();
            private function checkForUpdate():void {
                // Add events
                appUpdater.addEventListener(UpdateEvent.INITIALIZED, onInitialized);
                appUpdater.addEventListener(StatusUpdateErrorEvent.UPDATE_ERROR, onUpdateStatusError);
                appUpdater.addEventListener(StatusUpdateEvent.UPDATE_STATUS, updateStatusHandler);
                appUpdater.addEventListener(ErrorEvent.ERROR, onError); // If something goes wrong, run onError
                appUpdater.isCheckForUpdateVisible = true;
                appUpdater.isUnexpectedErrorVisible = true;
                appUpdater.isDownloadUpdateVisible= true;
                appUpdater.isDownloadProgressVisible=true;
                appUpdater.isInstallUpdateVisible = true;
                appUpdater.updateURL = APP_VERSION_FILE; // Server-side XML file describing update
                trace(APP_VERSION_FILE);
                appUpdater.initialize();
            private function onError(event:ErrorEvent):void {
                Alert.show('ERROR: ' + event.toString());
            private function onUpdateStatusError(event:StatusUpdateErrorEvent):void {
                Alert.show('Error Checking For Update: ' + event.toString());
            private function onInitialized(event:UpdateEvent):void {
                trace('Checking For Updates ...');
                appUpdater.checkNow();
            private function updateStatusHandler(event:UpdateEvent):void {
                //var descriptor:XML = NativeApplication.nativeApplication.applicationDescriptor;
                //var ns:Namespace   = descriptor.namespaceDeclarations()[0];
                //var verNum:String = descriptor.ns::versionNumber;
                trace('Update Event Reached ...');
        ]]>
    </fx:Script>
    <s:TitleWindow x="63" y="35" width="250" height="200" title="Hello">
        <s:Label x="24" y="80" text="Hello World"/>
    </s:TitleWindow>
</s:WindowedApplication>
-App.MXML File: (first part)
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<application xmlns="http://ns.adobe.com/air/application/2.6">

    
    <id>ca.questgeomatics.testairapp</id>
    
    <filename>TestAirUpdater</filename>
    
    <name>TestAirUpdater</name>
    
    <versionNumber>1.0.0</versionNumber>
    
    <versionLabel>v 1.0.0</versionLabel>
Updater XML file (new_app_version.xml):
<?xml version="1.0" encoding="utf-8"?>
<update xmlns="http://ns.adobe.com/air/framework/update/description/2.6">
<versionNumber>1.0.1</versionNumber>
<versionLabel>v 1.01</versionLabel>
<url>http://www.public-knowledge.com/Quest/Timesheets/TestAirUpdater.air</url>
<description><![CDATA[
* First official release that implemements Auto Updating feature
]]></description>
</update>
Bolded appl descriptor versions
Message was edited by: DonMitchinson

Status Update - don't know if this is a bug, design flaw, install problem or my misunderstanding.
I got it to work by first changing my Flex library to 4.5.0 - still didn't work with current
app and update mxml files using "2.6" for their namespace versions. But I did at least
get the popup error number 16815 - indicating an error in the update version namespace.
By leaving my application namespace version at "2.6" and changing the update version to "2.5" ... bingo!
I got my new update installed autiomatically.
Is this how it's supposed to work - or are my runtimes mixed up?
Will this work the same using the Flex 4.5.1 SDK? I'll find out shortly
Hope this helps others.

Why can't Flash Player auto-update?

Even in 1998, applications had the capability to auto-update. Why do I have to download a new install file for almost every Flash Player update? It even has the option to allow auto-updates yet here I am downloading another install file for the 37th time! If flash wasn't so embedded in all of the internet, I would abandon it and uninstall it altogether. I hope that someone comes along with a better solution so I don't have to use FP anymore. Get with the times, Adobe!

Flash Player HAS auto update available
The updates are not simply "patches" anymore. That sort of thing went the way of FAT16, several years ago.
You shouldn't have to update every day. If you are, something is wrong.

How to Auto Update an air app created in flash cs5

i have an application that needs to check auto update everytime it starts. but i have only found how to do it in fleash builder. sin ce im working in flash professional cs5 I DONT KNOW WHAT TO DO
any heads up?

The same techniques work in Flash/ActionScript. See http://help.adobe.com/en_US/air/build/WS5b3ccc516d4fbf351e63e3d118666ade46-7ff2.html. Although some of the examples are written in MXML, the relevant code is all ActionScript.

Adobe is not maintaining Flash Player auto-update

Flash Player auto-update is broken. The URL that is checked by the auto-update agent has not been maintained properly by Adobe:
https://fpdownload.macromedia.com/pub/flashplayer/update/current/sau/11/xml/version.xml
<version>
     <ActiveX major="11" minor="4" buildMajor="402" buildMinor="287"/>
     <Plugin major="11" minor="4" buildMajor="402" buildMinor="287"/>
     <MacPlugin major="11" minor="4" buildMajor="402" buildMinor="287"/>
     <SAUConfig checkFrequency="1"/>
</version>
This information is obviously out-of-date, as the current full-release version is Adobe Flash Player version 11.5.502.110.
http://www.adobe.com/software/flash/about/
As a result, client machines relying on the auto-update process are not being patched. The client machines themselves appear to be checking properly - they have internet access and fpsaud appears to be working properly.
There's really no point to having the auto-update facility if you're not going to maintain it. You might as well just pull it out of the product.

This is as designed. The silent auto update mechanism is not updated until 30 days after a major release. However, the older style UI notifications are sent out within 7 days (and a system restart). Hopefully the FAQ below explains how this works.
How does the automatic update feature work in Flash Player?
If you are responsible for updating clients within an enterprise network, we do have an option available that allows you to run your own update server and immediately push out builds silently and automatically.
http://blogs.adobe.com/spohl/2012/04/24/it-admin-deploying-flash-player-via-background-upd ater/

How to Disable Auto Updates on Flash Player 10 using mms.cfg

Hi Friends,
I am a newbee into this.I am trying to install a customized Adobe Flash Player 10.2.153.1 in which auto updates are disabled. I went through the Adobe guidelines and found that it is possible to do the same using a MMS.CFG file. Can anyone tell me how exactly this would look like. I will be extremely thankful if someone can attach a sample of the same.
One more question...
When we disable auto updates using mms.cfg file, will this be updated in the Global Settings Manager ?
Tries from my end till now:
I tried to create a mms.cfg by editing a txt file and adding "AutoUpdateDisable=0 " and then saving teh same as mms.cfg using UTF-8 encoding. this didnt make any difference in the Global Settings manager.
Please help me...
Regards,
Dilip

http://kb2.adobe.com/cps/167/16701594.html
But it seems that you have done everything correctly; doesn't it work?
dilzmail wrote:
One more question...When we disable auto updates using mms.cfg file, will this be updated in the Global Settings Manager ?
No, I don't think so; these settings are stored in a different place.
Some users have reported that AutoUpdateDisable via mms.cfg does no longer work in Flash Player 10.3. Please check if this failure already occurs in Flash Player 10.2.

Flash Player Auto-update problems

Hi,
In our environment we have Win 7 64bit Pro PCs, IE10 and users are NOT administrators. We install Flask Player 11.8.x using the MSI silent switches, with the autoupdate service disabled, the scheduled task for auto-update deleted and the MMS.CFG file configured to AutoUpdateDisable=1.
My current problem is that some users have now been prompted to upgrade their Flash player. This occurs during logon with task manager showing "FlashUtil32_11_8_800_168_ActiveX.exe /update activex" as an active process.
Does anyone have any ideas as to what may be causing the autoupdate? IS it possibly casued by Internet Explorer initiating the ocx? Any ideas welcome.
Many thanks in advance,
Andy

I should have also mentioned that if a user clicks [Install]
and follows the instructions, after being taken to the Flash
download page and trying to install, our own Flash detection code
no longer works. This means our users are prevented from launching
our app.

Flash Player auto-update fails to perform major updates

I'm managing Flash Player on a large number of Intel Mac computers. I have enabled the auto-update feature. Auto-update seems to work for minor updates (for example current version and update version are both 16.x.x). However the auto-update consistently fails to perform major version updates (for example from 16.x to 17.x).
mms.cfg file location:
/Library/Application Support/Macromedia/mms.cfg
contents:
AutoUpdateDisable=0
SilentAutoUpdateEnable=1

Hi,
Flash Player 17 was what is referred to as a 'loud' release and is distributed via the adobe.com site and not via silent auto-update. This blog post An outline of Flash Runtime installation options, specifically the 'Installation Options' section) provides more information. If you license Flash Player for distribution, the blog post, and the Flash Player Administrator's Guide offer various options for organizations to update Flash Player without the possible delay of the 'loud' releases. I'm happy to answer questions on the update options you may have after reviewing the blog post and the Administrator's guide.
Maria

Auto Update of 64 Bit Flash 11 on Vista Turns Zombie

Similar Messages

Maybe you are looking for