To get outbound control in a simple and user firendly manner for the Vista FW there is a free application (Vista FireWall COntrol). Because a few experienced FW users I know, used the default Vista FW (they say it is a decent and fast FW), I have learned to use the Vista FW (FW.MSC) in a dumb ass way. First installed Vista FW Control, started all of my application possibly needing internet access. Wrote down the programs and program paths asking for outbound. Then unistalled Vista FW Control. Next I went to FW.MSC First I changed allow to block for all outbound. Then I started to create allow entries one for the update service of Vista, the others on a per application basis gotten from VFWC. For future aps, I added a TEST TRUSTED RULE (which allows outbound for all programs and set to inactive). I use this when I install a trusted program, check what processes pop-up when I push an update buttom in task manager, and allow this program after setting the TEST TRUSTED RULE to inactive again). I noticed the startup seems to be shorter (Vista FW control always pop-up some 5 secs later). THIS IS MY QUESTION What are the benefits of using FW.MSC over Vista FireWall Control? The only one I have been told is that with FW.MSC the rules are valid right from boot up (that VFWC sets them when this program is loaded) Could somebody explain?