搜尋 Mozilla 技術支援網站

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

了解更多

Firefox crashes

  • 2 回覆
  • 3 有這個問題
  • 1 次檢視
  • 最近回覆由 erindshaw

more options

Getting Crash ID: bp-700fea1a-48eb-49c5-b4cf-4b61f2160608 when trying to install Firefox 45.2.0 ESR. Deploying thru SCCM but also crashes when installing locally from the .exe. Original install did include a .cfg, .ini, .js and .cmd file. Have used the files to install previous ESR versions with no problems. Uninstalling and reinstalling from just the .exe doesn't fix the problem. Installing previous versions and consumer version doesn't work to fix it either. Still crashing every time it's launched. Crashes in safe mode as well.

Getting Crash ID: bp-700fea1a-48eb-49c5-b4cf-4b61f2160608 when trying to install Firefox 45.2.0 ESR. Deploying thru SCCM but also crashes when installing locally from the .exe. Original install did include a .cfg, .ini, .js and .cmd file. Have used the files to install previous ESR versions with no problems. Uninstalling and reinstalling from just the .exe doesn't fix the problem. Installing previous versions and consumer version doesn't work to fix it either. Still crashing every time it's launched. Crashes in safe mode as well.

被選擇的解決方法

I'm not 100% certain, but the modules list includes a Websense Endpoint DLL (qipcap.dll), so it could be a new incompatibility with that program. Usually the ESR release is well supported by Websense so this is a little mysterious.

A workaround Firefox users sometimes employ is to create a fake qipcap.dll file that will block Firefox from using the incompatible qipcap.dll file. Please see this post for more information on this option, which I have not tried myself: https://support.mozilla.org/questions/1111324#answer-847872

從原來的回覆中察看解決方案 👍 1

所有回覆 (2)

more options

選擇的解決方法

I'm not 100% certain, but the modules list includes a Websense Endpoint DLL (qipcap.dll), so it could be a new incompatibility with that program. Usually the ESR release is well supported by Websense so this is a little mysterious.

A workaround Firefox users sometimes employ is to create a fake qipcap.dll file that will block Firefox from using the incompatible qipcap.dll file. Please see this post for more information on this option, which I have not tried myself: https://support.mozilla.org/questions/1111324#answer-847872

more options

You rock, J! Thank you so much for the quick reply and solution. I would have never figured THAT out and since I use my director's PC as a test subject for new packages (meaning I blew his FF up too), a quick fix was wonderful!