Well you are shooting yourself in the foot as you have the Outpost Web Control enabled, when it specifically should be disabled in compatibility mode.
- Outpost Exclusions - Whilst Outpost would have you exclude its folder from avast scans, I don't feel that is required, if outpost is running in its compatibility mode with no anti-spyware and no web control modules running.
Personally other than a single file exclusion I don't believe you need exclude the Outpost folder, I haven't in all of the time that I have been using avast and outpost together and that is many years.
This is the file and path that I have in the File System Shield, Expert Settings, Exclusions section, C:\Program Files\Agnitum\Outpost Firewall Pro\wl_hook.dll (easiest it to copy and paste this full path). This file is as its name implies a hooking tool that outpost uses to monitor activity also and is the only file where I ever had any issue with avast.
I would suggest that you do an uninstall, reboot and clean install of Outpost and when asked about avast acknowledge you have it installed (cheat and say you have exclusion set) and on the following installation settings uncheck the anti-spyware and web-control to maintain compatibility as Outpost stated.
See image and you will see no instance of those modules, you don't need them with avast installed.
The reason I say do a clean install, if you reinstall and do an update you won't get rid of the two modules.
