Avatar for Username

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

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

  • 1 risposta
  • 0 hanno questo problema
  • 1 visualizzazione
  • Ultima risposta di italiangm

italiangm
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.

Tutte le risposte (1)

italiangm
italiangm Utente che ha posto la domanda
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.