Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Firefox stopped working after updating to 43.0.1

  • 2 réponses
  • 1 a ce problème
  • 75 vues
  • Dernière réponse par Ian Hinton
  • Archivé

Ian Hinton
Ian Hinton

After updating to 43.0.1, Firefox no longer works. It won't even start up. The problem has appeared on two PCs: a laptop running Win 8.1 and a desktop running WinXP+SP3. Prior to this update this morning, things were running fine. As I frequently update, I was running 42.x before my update. To write this request for support, I'm using Google Chrome right now, as I can no longer start up Firefox. Any advice please?

After updating to 43.0.1, Firefox no longer works. It won't even start up. The problem has appeared on two PCs: a laptop running Win 8.1 and a desktop running WinXP+SP3. Prior to this update this morning, things were running fine. As I frequently update, I was running 42.x before my update. To write this request for support, I'm using Google Chrome right now, as I can no longer start up Firefox. Any advice please?

Toutes les réponses (2)

philipp
philipp
  • Moderator

hi, this is just a guess, but in case you have nvidia's network access manager or forceware network manager software installed, please go into your system control panel and uninstall it (or go there and have look if it is listed there, if you're unsure about this).

Ian Hinton
Ian Hinton Auteur de la question

Thanks for the reply. Neither of my PCs have the software you mention. Both PCs recovered Firefox functionality later in the day. My conclusion is that there was some kind of problem on Firefox's servers. That's the only explanation I can think of.