I have been having an issue where my firewall takes an inordinate amount of time to start when i reboot my machine. I tried for a long time to track it down. If i disable the windowzones service, firewall starts up right away, but when WZ is enabled, it takes more than 2 minutes for the firewall to start. I am using Sunbelt Kerio firewall, version 4.2.2.
Since this beta was released, we have significantly changed the way WZ starts up. It now starts much earlier and "lighter weight". Hopefully this will address the problem when we refresh the beta.
Do you have a rule applied to the firewall at all? Or is it possible its being spawned from another process that does have a rule?
I did not set any specific rule relating to WZ. I gave WZ unrestricted permissions across the board, including not having set any restrictions in the application behavior section of Kerio.
