There shouldn't be any conflict, I certainly haven't seen any and I have been using Outpost and avast for over seven years.
There should be no need to disable the avast behaviour shield, I have had that on since it was introduced and no conflict with Outpost's Host protection.
Aside from this isn't the latest Outpost firewall, 7.x is, but in the free version it is now a suite, but it recognises avast is installed during installation. It asks you to confirm you have avast installed, answer yes and it doesn't install the AV, web control or anti-spyware modules to retain compatibility.
- 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.
