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

Windows 10 Firewall created block incoming rules for firefox

  • 2 réponses
  • 8 ont ce problème
  • 1 vue
  • Dernière réponse par cor-el

more options

I was browsing the web with Firefox 56.0.2 when Windows popped up a security dialog asking me to allow incoming connections, I canceled the dialog and Windows Firewall created two block rules for incoming connections, one for all TCP connections to Firefox.exe and another for all UDP connections to Firefox.exe. The only addon I have installed is AdBlock Plus.

Any idea why this suddenly happened after months of normal use?

I was browsing the web with Firefox 56.0.2 when Windows popped up a security dialog asking me to allow incoming connections, I canceled the dialog and Windows Firewall created two block rules for incoming connections, one for all TCP connections to Firefox.exe and another for all UDP connections to Firefox.exe. The only addon I have installed is AdBlock Plus. Any idea why this suddenly happened after months of normal use?

Solution choisie

Please consider turning on send info to Mozilla before posting a question. This helps us help you.

If you check your Update History it is possible you received a update to Windows Defender. Or it just realized that your Firefox is now a different version since running the current version.

Microsoft wants it to be your A/V & Firewall. It does none of it very well. Since found the rules, delete them and create a rule to allow or wait for it to again popup and this time make the appropriate choice to allow for both TCP/UDP.

I strongly suggest getting a proper Firewall that monitors TCP/UDP to Firefox and blocks ones that are in their rules that are actually malicious. I run Norton Security and am blocking thousands of malicious requests daily to both ports. It is also advisable to run a anti-malware program at the same time. I run Malwarebytes and it blocks stuff that Norton does not catch.

Note : Firefox 57 Quantum release date Nov 14th https://www.mozilla.org/en-US/firefox/quantum/ Note : Legacy Extensions will be disabled and or removed.

Please let us know if this solved your issue or if need further assistance.

Lire cette réponse dans son contexte 👍 1

Toutes les réponses (2)

more options

Solution choisie

Please consider turning on send info to Mozilla before posting a question. This helps us help you.

If you check your Update History it is possible you received a update to Windows Defender. Or it just realized that your Firefox is now a different version since running the current version.

Microsoft wants it to be your A/V & Firewall. It does none of it very well. Since found the rules, delete them and create a rule to allow or wait for it to again popup and this time make the appropriate choice to allow for both TCP/UDP.

I strongly suggest getting a proper Firewall that monitors TCP/UDP to Firefox and blocks ones that are in their rules that are actually malicious. I run Norton Security and am blocking thousands of malicious requests daily to both ports. It is also advisable to run a anti-malware program at the same time. I run Malwarebytes and it blocks stuff that Norton does not catch.

Note : Firefox 57 Quantum release date Nov 14th https://www.mozilla.org/en-US/firefox/quantum/ Note : Legacy Extensions will be disabled and or removed.

Please let us know if this solved your issue or if need further assistance.

more options