We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

Firefox 5 will not start with Zone Alarm Ver 10.0.240.000

  • 1 个回答
  • 78 人有此问题
  • 10 次查看
  • 最后回复者为 Bad K

more options

Firefox updated yesterday and now it will no longer start, it looks like the probem may be with Zone Alarm Forcefield. Does anyone have any ideas how to get Firefox 5 to tun under Zone Alarm Extreme Security? Thanks

Firefox updated yesterday and now it will no longer start, it looks like the probem may be with Zone Alarm Forcefield. Does anyone have any ideas how to get Firefox 5 to tun under Zone Alarm Extreme Security? Thanks

由Btrask于修改

所有回复 (1)

more options

Hi,

I'm running Win7 x64 with ZoneAlarm Extreme Security 10.0.241.000

I had the same problem with Firefox 4. After turning off ForceField Toolbar, it started working fine.

Then I updated to Firefox 5 and it wouldn't start, instead it was showing an error message from ZA...

I searched mozilla support and followed the instructions here: http://kb.mozillazine.org/Browser_will_not_start_up on the topic"Firefox does not start after updating with ZoneAlarm ForceField enabled".

The correct instructions for this ZA version should be: "Internet -> Web Security -> Settings, and click Clear Virtual Data"

After that I could open Firefox again! Then I realized it was still version 4... I installed the update, and everything went smooth. Checked again if Forcefield toolbar was inactive (it was) and opened a few pages, closed Firefox and opened again. After a while it wouldn't open...

AGAIN the "Clear Virtual Data" did the trick...

This time I clicked on Settings (next to "Clear Virtual Data") -> Advanced Settings, and turned off "Enable Virtualization".

Until ZA get a fix for this, either we turn it off or clear virtual data every few moves...

Working fine.

Best regards