Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Firefox 19 incompatible with latest Windows update

  • 2 përgjigje
  • 12 e kanë hasur këtë problem
  • 1 parje
  • Përgjigjja më e re nga 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.

Zgjidhje e zgjedhur

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

Lexojeni këtë përgjigje brenda kontekstit 👍 7

Krejt Përgjigjet (2)

more options

Zgjidhja e Zgjedhur

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!!