The latest Flash Player version is 11.4.402.278.
I downloaded the Flash Player msi (both ActiveX and plug-in) from the distribution page, and it installed the correct version. (11.4.402.278)
However, the Flash Player version written in this page is incorrect. We are updating the page.
Hi Sunil. Thank you for the reply. I'm not sure I understand what you mean by the version written in this page is incorrect? Are you referring to the version number that shows up in the list of Windows installed programs?
I'm running Windows 7 on my workstation. I just now downloaded both the ActiveX and Plugin version of the .MSI installers again. After I install them both and I go into Windows Control Panel - Programs and Features, it shows v11.4.402.267 is the installed version. This is the version number that I am referring to that is incorrect.
I did notice if I install the .EXE versions of the ActiveX and Plugin, it "does" show the correct version number of v11.4.402.278 in the list of installed programs in Windows. However, we only use the .MSI installer, which is what we are having a problem with.
EDIT: If you hear when these downloads get updated with a fixed version, can you please post that here? I will check the downloads frequently, but I'm guessing it will take some time before new files are put out there.
Thanks for bringing this to our attention. It looks like we forgot to update the version string in the .msi. As Sunil mentioned, the version string that Flash Player reports (11.4.402.278) is correct. We'll correct the problem with the msi the next time we release an update.
Edit: Just to be clear, the incorrect version string in the msi is the one reported in the add/remove programs control panel.
Hello Chris. Thank you for the update. I'll discuss it with our folks and see if they want to download this update or wait until the next one. Is there a place to find a "revision history" for Flash Player so we can review them to know the changes from one version to the next? We're primarily interested in security updates between versions and use that as a determination on how important it is for us to update our computers.
We have revision information in our readme's and I also maintain an "Announcement" forum for runtime updates that you can subscribe to here:
This release was simply a result of changes to our build process. There were no code changes made and no need for you to update your client systems.
You said "We have revision information in our readme's and I also maintain an "Announcement" forum for runtime updates that you can subscribe to here:". But the latest announcement on that page is from 4 weeks ago, the 8/21 announcement of Adobe AIR 3.4. Where is the announcement of Flash 11.4.402.278?
If I check the "Adobe Flash" version online at http://www.adobe.com/software/flash/about/ it does show me as having the current version, so it's just an MSI buglet. A simple registry fix will correct that for our version testing software.
For the plugin (I don't install the ActiveX player) on XP 32-bit,
Windows Registry Editor Version 5.00
Thanks Chris. As GeoAppsTucson mentioned, the revision info is a bit behind at the link you posted. So I have to ask where I might find the readme's you reference?
I have the same question, but it appears since this is a build difference only with no code changes, release notes would be redundant. Confusing though, especially when people ask whether or not this update should be installed. With nothing to reference, we didn't know what to tell them. I'm having no problems with the prior release so will hold off until a security update (with release notes) is issued and will advise the same with our forum members.
Hi SMSTechSR. It looks like you reported the same thing I did. Because we couldn't identify what was in this update, we've chosen to bypass installing it and not have to deal with the version bug.
The MSI could be fixed by using ORCA or similar if you need to distribute.
However I agree it may be best to bypass this version.
As far as I can see this issue has not been fixed (first reported 19th September) and is still causing confusion for organisations that try to distribute automatically.
I wonder why we have such a delay?
As mentioned before, this will be fixed in our next update. Look for this becoming available in the next week or so.