Hi

If you enter about:support in the address bar, what version number of Firefox do you have installed on your computer?

Hi If you enter about:support in the address bar, what version number of Firefox do you have installed on your computer?

Maybe i addressed my problem in the wrong way, but i really can't understand your answer: how am i supposed to type in what you said if i can't open the browser. Just to clarify i'm currently writing from Chrome. Firefox doesn't open at all

Also, thanks for your fast reply.

Please perform the following steps to give us a crash report ID that helps us find out more about the cause of the crash.

1. On the keyboard, press [Windows] The image "Windows key" does not exist. + [R]. This should bring up a Run window that contains a text field.
2. In that text field, type %APPDATA% and press Enter. An explorer window should open.
3. From that explorer window, double-click on the Mozilla folder, then double-click on Firefox and then on Crash reports. Double-click on submitted.
4. 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.
5. Open the most recent 5 files with a text editor and copy the IDs.
6. 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.

bp-1658062942 bp-1658057334 bp-1658054080 bp-1658057092 Those are the only ID's i've found, and every one of them was inside a generic file named InstallationTime followed by a string of numbers. I did not found any "submitted" folder. I may not be an expert, but these file look like a report of the time of installation of the four times i've tried. Also, sorry if some parts of this aren't understandable, but i'm not a native English speaker

What you posted are the date/time strings created when Firefox updates.

A crash report is a 32 character UUID string.

• bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Try to start Firefox in Troubleshoot Mode to see if that works.

• Windows: hold down the Shift key while starting Firefox
• Mac: hold down the Options key while starting Firefox

• https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode

You can try to bring up the Profile Manager and possibly create a new profile as a quick test to see if your current profile is causing the problem.

See "Creating a profile":

• https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

• https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile

You can check for issues caused by a corrupted or incomplete Visual C++ installation that is missing runtime components (Redistributable Packages) required by Firefox, especially VCRUNTIME140_1.dll.

See "Visual Studio 2015, 2017, 2019, and 2022":

• https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist
• https://aka.ms/vs/17/release/vc_redist.x64.exe
• https://aka.ms/vs/17/release/vc_redist.x86.exe

You may also have to install the Visual Studio 2013 Redistributable Package. You need to reboot the computer.

What you posted are the date/time strings created when Firefox updates. A crash report is a 32 character UUID string.

• bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

---

Try to start Firefox in Troubleshoot Mode to see if that works.

• Windows: hold down the Shift key while starting Firefox
• Mac: hold down the Options key while starting Firefox

• https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode

You can try to bring up the Profile Manager and possibly create a new profile as a quick test to see if your current profile is causing the problem.

See "Creating a profile":

• https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

• https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile

---

You can check for issues caused by a corrupted or incomplete Visual C++ installation that is missing runtime components (Redistributable Packages) required by Firefox, especially VCRUNTIME140_1.dll.

See "Visual Studio 2015, 2017, 2019, and 2022":

• https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist
• https://aka.ms/vs/17/release/vc_redist.x64.exe
• https://aka.ms/vs/17/release/vc_redist.x86.exe

You may also have to install the Visual Studio 2013 Redistributable Package. You need to reboot the computer.

Yeah, i thought it would have been something like that. I tried everything you said, but the profile manager just like the main application starts for a second and then crashes, the Redist was already up-to-date and safe mode just doesn't work. I even tried to kill any process in the backround using the task manager, but it simply shows up and then it closes. I do not have any other crash report. I also tried to install an older version like the 70.00 and then to update to the latest one directly, but even older versions don't open. I wanted Firefox because Chrome kills RAM and collects too much data, but at this point i'm just gonna remain on this bugged browser if there isn't a solution

You can try and install other variants of Firefox like Waterfox, Pale Moon, etc or even Firefox Nightly to see if it has the same problem, maybe your firefox updater is corrupted so it said like that

You can try and install other variants of Firefox like Waterfox, Pale Moon, etc or even Firefox Nightly to see if it has the same problem, maybe your firefox updater is corrupted so it said like that

Thank you mate. I'm just gonna use waterfox form now on. Absolutely in love with the design and functions. Have a nice day everybody and thanks for helping me with this problem! For those who have the same problem: you can wait until mozilla sees this and hopefully corrects the bug or use waterfox.