Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Firefox 19 incompatible with latest Windows update

  • 2 Antworten
  • 12 haben dieses Problem
  • 3 Aufrufe
  • Letzte Antwort von Catffs

more options

Running Firefox 19 and Vista/Windows 7.

My computer got one of those "critical Windows updates" and installed automatically. Afterwards it would not run Firefox. Firefox did not crash--it simply never started running in the first place. The most information I could get was that Firefox was now incompatible. Malwarebytes was able to connect to the internet, but not my browser. I did a system restore to before the update and it all works for now, but that's only a temporary fix.

Any ideas would be welcome.

Running Firefox 19 and Vista/Windows 7. My computer got one of those "critical Windows updates" and installed automatically. Afterwards it would not run Firefox. Firefox did not crash--it simply never started running in the first place. The most information I could get was that Firefox was now incompatible. Malwarebytes was able to connect to the internet, but not my browser. I did a system restore to before the update and it all works for now, but that's only a temporary fix. Any ideas would be welcome.

Ausgewählte Lösung

hello Catffs, please start firefox in safemode (by pressing the shift-key while it is launching) & go to firefox > options > advanced > general & disable hardware acceleration.

for some background on that issue you can also refer to bug #812683

Diese Antwort im Kontext lesen 👍 7

Alle Antworten (2)

more options

Ausgewählte Lösung

hello Catffs, please start firefox in safemode (by pressing the shift-key while it is launching) & go to firefox > options > advanced > general & disable hardware acceleration.

for some background on that issue you can also refer to bug #812683

more options

Thanks very much!!