Firefox won't open and immediately ends all processes
Through extensive troubleshooting, I am unable to get firefox to open at all.
I've done a full uninstall, cleaned all user directories, program files / x86, program data, appdata roaming and local, etc. I used the Microsoft uninstaller and even Revo Uninstaller to remove everything related to Firefox, did a restart and reinstall of the latest one and it still won't launch.
Firefox was previously working until a reboot occurred and now it won't launch.
Firefox 32 bit seems to work when installed, and running Firefox as an admin previously worked but no it no longer does.
I looked at the following articles: - https://support.mozilla.org/en-US/kb/firefox-wont-start-find-solutions - https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles - https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles#w_start-the-profile-manager-when-firefox-is-closed
There's no malware on this machine (business EDR on it, even disabled it as a test and it still didn't open).
I was able to launch the profile manager but now I am unable to as the processes launch in task manager and then within 5 seconds they close.
Firefox is not running in the background for any user (I'm the only one logged in after a reboot as well)
I'm unable to open in troubleshoot mode either. Tried run as and admin cmd "C:\Program Files\Mozilla Firefox\firefox.exe" -safe-mode
Ran SFC / scannow / DISM restore health commands as well and both came back fine / no integrity violations
Выбранное решение
Mozilla devs already send it to them, so you don't have to.
Прочитайте этот ответ в контексте 👍 0Все ответы (9)
We're sorry to hear that your Firefox seems to be crashing when you open it. Please perform the following steps to give us a crash report ID that helps us find out more about the cause of the crash.
- On the keyboard, press [Windows]
+ [R]. This should bring up a Run box that contains a text field.
- In that text field, type %APPDATA% and press Enter. An explorer window should open.
- From that explorer window, double-click on the Mozilla folder, then double-click on Firefox and then on Crash reports. Double-click on submitted.
- Now, you should see a list of files that contain reports. Go to View > Arrange Icons by > Modified to get the most recent files at the top of the window.
- Open the most recent 5 files with a text editor and copy the IDs.
- Paste each ID with bp- into the reply window on the forums.
Thanks in advance!
You can find more information and troubleshooting steps in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
Sorry for the delay, Since I installed 32-bit to just function / work during the day I had to uninstall / reinstall 64-bit when I had time.
There is a crash reports folder but no data inside of the logs or events. I even simulated Firefox to crash several times, and it still doesn't go through.
I attached a screenshot of the directory showing nothing.
I have a quick video showing the process crash / fail to launch, but I am unable to upload it to this site.
Yes, SentinelOne is on this machine.
S1 hasn't received an update in over a month and FF 64-bit has been working fine ever since I made this post & there are 29 other employees who are allowed to use FF with S1 installed and no exclusions as well.
Did something change in 146.0.1? Even though that was released on the 18th of December, trying to think of anything else in this case.
Again, 32-bit has no issues.
I don't know why it's so selective. We have these crashes since 146.0, but we don't believe it was something on our side. Nevertheless, Sentinel is blacklisted since Firefox 147.0.
Im genuinely confused because before I opened this topic up, I disabled S1 and tested and it still failed which is why I ruled it out and even stated in the opening thread that I tried that.
I just tried it again, and it worked by disabling S1...
Can you elaborate on "Sentinel is blacklisted since Firefox 147.0."?
Do you have any information, logs, developer statements for me so I can go back to SentinelOne and push on them about this?
Выбранное решение
Mozilla devs already send it to them, so you don't have to.
Is there a beta build of 147 I can run to prevent this issue?
I don't want to disable S1 everytime I want to use FF (which is daily) nor put in a browser exclusion which seems excessive.
Для ответа на сообщения вы должны войти в свою учётную запись. Пожалуйста, задайте новый вопрос, если у вас ещё нет учётной записи.