搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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