hi hidere and msma11,
One of the unforseen issues with doing an upgrade to a newer build/version within the gui (program) is that all settings are carried over to the newest build or version number, whilst all the old files are tossed and new ones come in to replace them.
This means that the avast! firewall is not the same as the old one but has all the old settings set as if it was the old one, and this will happen if you update from within the gui. Old carried over settings are not going to work perfectly all the time in a newly redesigned firewall. Old settings will sometimes get blocked by newer/different firewall.
Example: OK to update within gui only if the version number is the same: 8.0.1482 to .1483 to .1488 to .1489 to .1497. Not OK to update from gui from 8.0.xxxx to 9.0.xxxx as too many new files, features, firewall redesign, etc., and certain specific settings unique to a particular user cannot be anticipated by avast! as these settings may not be the norm, but rather, is sometimes the exception.
FIX? Either remove all old settings within the new firewall or do a repair/clean install of avast! so you can set it just the way you want. avast! firewall will detect all your new connections and your xbox and ask what to do. Allow all connections as before and you should be good to go.
Best advice is don't update within the gui if moving up one build/version number (8.0 to 9.0); do a clean install instead.
FYI: Updating within a build/version number via gui works most of the time, but sometimes it doesn't, just so you know.
[EDIT:] Fixed typo.