当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

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