搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Version 30 keeps saying Flash 13.0.0.214 needs updating

  • 2 回覆
  • 46 有這個問題
  • 8 次檢視
  • 最近回覆由 josephrot

more options

UPDATE to Myself / Others... This could be a known "bug" with FF Ver 30.0 ?

Version 30.0 keeps saying Flash 13.0.0.214 needs updating. Clearly, Flash 13.0.0.214 IS already THE latest Flash.

Just to be "safe", I have repeatedly de-installed Flash, then repeatedly re-installed Flash 13.0.0.214.

The Flash install (and re-install over and over) works, but FF 30.0 about:addons PlugIns insists to "red-list" Flash 13.0.0.214, and thus keeps advising to update it.

Restarts of both 30.0 Firefox, and even system re-sets (Windows 7 64bit) have no effect. Doing anything in FF 30.0 "safe mode" is typically useless in the past and useless here.

Useless waste of time to even see the PlugIns message.

UPDATE to Myself / Others... This could be a known "bug" with FF Ver 30.0 ? Version 30.0 keeps saying Flash 13.0.0.214 needs updating. Clearly, Flash 13.0.0.214 IS already THE latest Flash. Just to be "safe", I have repeatedly de-installed Flash, then repeatedly re-installed Flash 13.0.0.214. The Flash install (and re-install over and over) works, but FF 30.0 about:addons PlugIns insists to "red-list" Flash 13.0.0.214, and thus keeps advising to update it. Restarts of both 30.0 Firefox, and even system re-sets (Windows 7 64bit) have no effect. Doing anything in FF 30.0 "safe mode" is typically useless in the past and useless here. Useless waste of time to even see the PlugIns message.

由 josephrot 於 修改

所有回覆 (2)

more options

This is supposed to be fixed sometime soon.

Feel free to vote for the report to keep track of any progress, but please don't post comments unless you have technical information to add. See the Bugzilla etiquette page for details.

  • Bug 1011824 - Plugin check page displays Flash plugin as vulnerable even if the latest version is installed in Beta30b4, Aurora31.0a2 and Nightly32.0a1
more options

Thank you for the update. OK, so it is a known bug, which actually makes me breathe easier than if we found out that this was "operation normal" behavior.

So we shall stand-by and see what the next Beta or two bring about.

Joe / Knoxville, TN / USA