1

When Windows Firewall is activated, newly installed programs open incoming ports. Can this be prevented somehow?

Fragmentation Needed
  • 215
  • 1
    UAC prevents this by default. When you enter your administrator password or click "Yes" in the UAC prompt, you are effectively saying "Yes, program, you can make changes to my registry, firewall, settings and files". –  Aug 19 '13 at 20:32
  • 1
    Clarification: Can I prevent it in any case? So you have to add these firewall exceptions manually? – Fragmentation Needed Aug 21 '13 at 18:43
  • Did you ever get a solution to this? As far as I know, each program you install will have logic built into the installation/setup process to open the firewall ports programmatically using commands and such opening what's needed for the application to work. I suspect if you install elevated, then that elevated credential would have access to open the firewall up. An idea that may be worth testing would be to completely disable the Windows Firewall (I have a post or two explaining this simple process) before the install, run the install, re-enable the FW, and then check to confirm, etc. – Vomit IT - Chunky Mess Style Nov 24 '19 at 15:02
  • For example here.... as I wrote about here you can run netsh advfirewall set allprofiles state off, do your install, and then run netsh advfirewall set allprofiles state on after the install. – Vomit IT - Chunky Mess Style Nov 24 '19 at 15:09

0 Answers0