The Windows Firewall service (not the same as the Windows Firewall) sees/handles most, if not all, network traffic going through the PC, which is why the service itself (services.msc) cannot be disabled. I don't know the technical reason why, and perhaps this has changed with Windows 10, but it's not likely. utilize google and TechNet to research what any service is, and what it controls, prior to disabling. Don't make the mistake of simply assuming because a service has a descriptive name that it only controls what it's named as.what it does and does not control), one shouldn't be disabling it until thoroughly researching the aforementioned. The Windows Firewall service has deep hooks within Windows, and like anything, unless one knows the exact nature of a service (i.e. The service is critical to printers, and if one disables it, one will receive endpoint mapping errors when trying to add a printer (as well as print IIRC), among other networking and network device functions (essentially anything utilizing USB over IP). The Windows Firewall service must never be disabled, as the Windows Firewall is only a minute part of the Windows Firewall service. Any user who's claimed they've ran Windows Firewall enabled alongside a 3rd party firewall obviously wasn't paying attention, else they'd have realized traffic they explicitly blocked was in fact being accepted (inbound or outbound, doesn't matter).Running Windows Firewall alongside Comodo Firewall (free, CIS, or any other 3rd party firewall, it doesn't matter) will result in many granular Comodo rules being ignored, allowing traffic through which was explicitly blocked in Comodo. Simply for factual accuracy, as this is an old thread:
0 kommentar(er)
