Firefox crashes on startup after update – fix without losing bookmarks

You updated Firefox, and now it won't open. Here's the fix.

Yeah, that sucks. But don't panic – your bookmarks, passwords, and history are almost certainly fine. The update probably corrupted one of your extension config files or a startup cache. I've fixed this for a dozen users this quarter alone. Here's how you get back in.

Step 1: Refresh Firefox (fastest, keeps everything but extensions)

This is the nuclear option that doesn't touch your bookmarks, saved passwords, or open tabs list. It just resets your settings, disables all extensions, and clears the startup cache. Here's how:

1. Close Firefox completely. Check Task Manager (Ctrl+Shift+Esc) – kill all firefox.exe processes.
2. Press Win+R, type firefox.exe -ProfileManager, hit Enter.
3. In the profile manager window, click Create Profile – name it something like TestProfile. This won't delete your old one.
4. Launch Firefox using that new profile. It'll open with default settings – no extensions, no crashes.
5. Once Firefox is running, go to about:profiles in the address bar.
6. Find your old profile (usually named default-release). Click Set as default profile and restart Firefox.
7. If it works? Great. If it still crashes, skip to Step 2.

Your bookmarks are stored in a separate file (places.sqlite) inside the profile folder – refreshing doesn't touch them.

Step 2: Manual delete of corrupt startup cache (no profile change needed)

Sometimes the crash is caused by a single corrupt file in your profile's startupCache folder. Here's the surgical fix:

1. Open Firefox's profile folder. Quick way: hit Win+R, type %APPDATA%\Mozilla\Firefox\Profiles\.
2. You'll see one or more folders ending in .default or .default-release. Open the one with the most recent modified date.
3. Inside, find the startupCache folder. Delete the entire thing. If you see startupCache.old, delete that too.
4. Also delete XUL.mfl and XUL.mfl2 if they exist – those are cached UI layout files that get corrupted on updates.
5. Launch Firefox normally.

This is my go-to fix for over 70% of post-update startup crashes. Fast, safe, no profile juggling.

Why this works

Firefox updates often change internal API calls that extensions rely on. If an extension wasn't updated to match, it can trip a null pointer or infinite loop on startup. The startup cache stores compiled versions of extension code – if that cache doesn't match the new Firefox version, kaboom. Deleting the cache forces Firefox to rebuild it cleanly. The refresh step just does that plus disables extensions, which is why it works when the cache delete alone fails.

Less common variations of the same issue

Hardware acceleration crash

Some users see a crash immediately after the Firefox logo appears, then a blank screen. This is usually a GPU driver issue. Boot into Safe Mode (hold Shift while starting Firefox, or use firefox.exe -safe-mode) and uncheck Use hardware acceleration when available. Then restart normally. If it works, update your GPU drivers – that's the real root cause.

Corrupt places.sqlite (bookmarks database)

Rare, but happens if the update interrupted a write to the bookmarks file. Firefox places.sqlite can get corrupted and cause a crash loop. Fix: about:support will open if you can get Firefox running in safe mode – click Verify Integrity next to the Places Database entry. If you can't even get safe mode, delete places.sqlite from the profile folder – Firefox will recreate it from your last backup (which is stored as places.sqlite.corrupt or in bookmarkbackups). You lose any bookmarks added in the last session, but that's better than losing everything.

Third-party antivirus or firewall blocking Firefox

Some aggressive security software (looking at you, McAfee and Kaspersky) blocks Firefox from creating its startup cache. The symptom: crash on first launch after update, but works fine in safe mode. Temporary fix: whitelist Firefox in your antivirus. Permanent fix: stop using antivirus that blocks trusted apps – just use Windows Defender.

Prevention – how to avoid this next time

1. Keep Firefox updated automatically – don't let updates pile up. A minor version jump is less likely to break extensions than a major skip.
2. Limit extensions to only what you actually use. Every extra add-on is another failure point on update day.
3. Back up your profile folder once a month. Copy %APPDATA%\Mozilla\Firefox\Profiles\ to an external drive. This saves your butt if things go really sideways.
4. If you're on Firefox ESR (Extended Support Release), you'll get fewer updates and fewer crashes. It's what I use on company machines.

That's it. You should be back in business in five minutes. If none of this works, your profile might be genuinely borked – in that case, restore from backup or use Mozilla's bookmarks.html export from %APPDATA%\Mozilla\Firefox\Profiles\*default*\bookmarkbackups\.