Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

Learn More

A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.

I received an error message after trying to update Firefox and can no longer access Firefox. What do I do?

  • 4 válasz
  • 1 embernek van ilyen problémája
  • 7 megtekintés
  • Utolsó üzenet ettől: philipp

more options

I received a notice to update Firefox, so I did. During installation, I received an error message stating "The procedure entry point GetLogicalProcessorInformation could not be located in the dynamic link and can no longer get into firefox at all. What do I do? I even uninstalled it, restarted my computer, and tried reinstalling it, and it still won't work. I'm also receiving a message that firefox.exe has encountered a problem. Please let me know how to proceed. Thank you.

I received a notice to update Firefox, so I did. During installation, I received an error message stating "The procedure entry point GetLogicalProcessorInformation could not be located in the dynamic link and can no longer get into firefox at all. What do I do? I even uninstalled it, restarted my computer, and tried reinstalling it, and it still won't work. I'm also receiving a message that firefox.exe has encountered a problem. Please let me know how to proceed. Thank you.

Összes válasz (4)

more options

hi nb-cp, this is currently a bug in firefox 36 which is affecting a small subset of XP users (apparently where some corruption of system files is going on). could you specify if you are using servicepack 2 or 3?

more options

Service Pack 3

more options

ok thanks, at the moment a downgrade to firefox 35.0.1 is probably the only way to work around that until mozilla can come forward with a fix for this bug: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/35.0.1/win32/

more options

hi again, mozilla has just released an update to firefox 36.0.1 which should address the problem: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/36.0.1/win32/