Avatar for Username

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

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

  • 1 відповідь
  • 0 мають цю проблему
  • 1 перегляд
  • Остання відповідь від 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.

Усі відповіді (1)

italiangm
italiangm Власник питання
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.