Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Crash still happens in Troubleshoot Mode. See Crash ID below.

  • 1 antwurd
  • 0 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan italiangm

more options

Following instructions on crashes. Here's the Crash ID:

bp-4d41c3d8-62ef-44e0-a320-8241e0220908

The machine with the crash problem is Win 10 with Firefox 104.0.2 (64 bit) installed. The machine I'm submitting this request from is Win 7 with Firefox 104.0.1 (64 bit) installed.

Please advise what to do next. Thanks.

Following instructions on crashes. Here's the Crash ID: bp-4d41c3d8-62ef-44e0-a320-8241e0220908 The machine with the crash problem is Win 10 with Firefox 104.0.2 (64 bit) installed. The machine I'm submitting this request from is Win 7 with Firefox 104.0.1 (64 bit) installed. Please advise what to do next. Thanks.

Alle antwurden (1)

more options

I may have discovered what the problem was. Malwarebytes v4.5.14.210 detected and quarantined "PUP.Optional.Slimware" located at C:\PROGRAM FILES\MOZILLA FIREFOX\OMNI.JA. I restored OMNI.JA and launched Firefox in troubleshooting mode. Since it launched successfully, I turned troubleshooting mode off. Firefox seems to be working fine in normal mode, at least for now.

Also note: I configure Firefox to advise when updates are available instead of automatic updates. This gives me time to research if others are having problems with the update. Since I didn't see any issues, I updated to 104.0.2 and thought it had been successful. After restoring OMNI.JA however, I learned Firefox was still at 104.0.1.

I'm going to hold off updating to 104.0.2 again for a bit since the quarantine of OMNI.JA only occurred after the (apparently unsuccessful) update.