Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox crash at launch

  • 1 답장
  • 2 이 문제를 만남
  • 7 보기
  • 최종 답변자: Scribe

more options

Crash ID: bp-7dbe49dc-7f25-4f83-a62a-bd5312161229

Hello, since this morning I'm unable to launch FF. As soon as I try to execute the browser, I get the "Mozilla Crash Reporter" window, and safe mode is not working neither (pressing shift). I follow the suggestions I could find on Mozilla help, but none is working. I did a fresh install of FF, as that didn't work neither, I uninstall FF and remove any trace of Mozilla on AppData folders (after backing it up). I re-installed after that, and again, "Mozilla Crash Reporter". I have put the crash ID above, the latest one, which correlates with a clean instalation without data on AppData folder.

The system is a Dell E6530 running Windows 10 enterprise, with Firefox 50.1. I can't think of any software or hardware change that could have triggered this. Can anybody help me? I want my loved browser back :(

Crash ID: bp-7dbe49dc-7f25-4f83-a62a-bd5312161229 Hello, since this morning I'm unable to launch FF. As soon as I try to execute the browser, I get the "Mozilla Crash Reporter" window, and safe mode is not working neither (pressing shift). I follow the suggestions I could find on Mozilla help, but none is working. I did a fresh install of FF, as that didn't work neither, I uninstall FF and remove any trace of Mozilla on AppData folders (after backing it up). I re-installed after that, and again, "Mozilla Crash Reporter". I have put the crash ID above, the latest one, which correlates with a clean instalation without data on AppData folder. The system is a Dell E6530 running Windows 10 enterprise, with Firefox 50.1. I can't think of any software or hardware change that could have triggered this. Can anybody help me? I want my loved browser back :(

글쓴이 l1thiium 수정일시

선택된 해결법

Hi, this seems to be caused by a problem with Websense Endpoint, so if you have it on your system or within your organization, perhaps you could if possible try updating or disabling it.

If your question is resolved by this or another answer, please take a minute to let us know. Thank you!

문맥에 따라 이 답변을 읽어주세요 👍 1

모든 댓글 (1)

more options

선택된 해결법

Hi, this seems to be caused by a problem with Websense Endpoint, so if you have it on your system or within your organization, perhaps you could if possible try updating or disabling it.

If your question is resolved by this or another answer, please take a minute to let us know. Thank you!