Avatar for Username

Search Support

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.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox crash at launch

  • 1 reply
  • 2 have this problem
  • 7 views
  • Last reply by Scribe

l1thiium
l1thiium
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 :(

Modified by l1thiium

Chosen solution

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!

Read this answer in context 👍 1

All Replies (1)

Scribe
Scribe
more options

Chosen Solution

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!