i installed 7.5.1 over 7.5 and all went okay. it checked compatibility to avast and then unchecked anti-spyware and web control and i’m done. i checked my setiings and they are disabled. ;D
I don’t want them just disabled I don’t want those elements installed, which is why I did a custom Expert install for the 7.5 install.
Disabled still does anti-spyware stuff in the background, it allows scheduled anti-spyware scans, it places an entry in the windows explorer context menu. To achieve all of these it updates the anti-spyware signatures, so essentially all it is doing it stopping the resident protection.
Which isn’t what I want and nor was it what I had the current installation set up for, so clearly it isn’t ‘just’ updating my existing installation or it would respect my current installation and settings.
I was also wondering and get to ask PR Manager. Here is what she says…which is not looking promising
I am the anonymous in the second post
Thanks
Ash
you’re the man. i reinstalled following your advice. lol 
You’re welcome, I have been having my own fun and games with outpost 7.5.1 on my win7 netbook.
Whilst this might be off topic for this particular outpost issue.
But I have just spent a few of hours battling with a BSOD and Outpost 7.5.1 installed on my win7 netbook.
I did a clean install because of what I mentioned above about update installs modules not in the original installation. The first reboot was fine, when I then entered my license and imported my previous configuration settings (which I had exported prior to uninstall). Since that was late last night I just shutdown my netbook and went to bed.
This morning I started it up and BSOD started my desktop and did some searching on the BSOD stop: 0x0000007E (0xC000005, …, …, …) and nothing of much use. Well knowing the last installation was the Outpost 7.5.1 Installation, tried to boot into safe mode to uninstall. Had to go through the win7 repair attempt, unable to repair anything, finally I was able to uninstall and reboot and no problem.
I went through the clean install and associated BSOD, win7 repair, safe mode, uninstall hassle twice more with the same result. Finally I installed it entered the key and didn’t bother importing the saved configuration settings from 7.5 and this booted into normal mode.
So for whatever reason, 7.5.1 didn’t like the 7.5 configuration settings to the point of it resulting in a BSOD. I have done a few reboots since and no further BSOD problems, fingers firmly crossed.
This is quite interesting. I’ve asked Agnitum support about installation process
and disabled modules. Here it goes:
I would like to know if the Anti-Spyware and Web Control modules are
disabled for compatibility reasons and don’t actually run, can I i
count such situation as if I had never check them to install during
the installation process?Agnitum’s answer:
Yes, you can. There is no difference in these situations.
This statement contradicts what You have wrote about…:-/
In all honestly I have found the outpost firewall forum most frustrating on the rare occasions that I resorted to it.
I can only recount my personal experience, from what was a clean install of 7.5.0, expert install where I didn’t install the web control or anti-spyware; I installed 7.5.1 over the top of 7.5.0 and it recognised that was installed and offered an update of the existing installation. Now even though I didn’t have the web control or anti-spyware modules installed and in the compatibility screen I unchecked the web control and anti-spyware options, they were installed (all be it disabled) and as I said I didn’t want them disabled I didn’t want them installed, period.
Why else would I go to that trouble in the expert install only for the update to ride roughshod over my previous decision. So I had to once again uninstall outpost, reboot and do
a clean expert install, crazy and bloody frustrating.
So you simply aren’t getting the full story in the answer you got, I have run in compatibility mode previously and it was only in 7.5 when they introduced some other functionality in the anti-spyware module that I realised that it is still running in other areas, there for context menu and on-demand scans as I said these would require that the anti-spyware modules signatures were updated. There is also the option to Submit suspicious files for analysis in the ImproveNet, now I’m wondering how this is achieved without the anti-spyware. Not to mention I unchecked the ImproveNet option during the install, yet here is another example of it not complying with my install options.
I have anti-spyware protection coming out of my wazoo I don’t need or want another. I have simple needs and that is for my firewall to be just that a bloody good firewall and let me take care of the rest or at the very least comply with my options on installation or update.
That is why I’m so pissed after many, many years of using outpost that they haven’t come up with a program update from the GUI that ‘only updates’ the components you have installed.
I would say that if you have avast behavior shield installed ,there’s also a very strong possibility of conflict with outpost.Id use one or the other.Personally i have far less problems ,since i reinstalled AVAST without the behavior shield.IMO there’s no need for it if you are using outpost and its hips features.
I have had no conflict with avast and outpost when in compatibility mode or on a custom install without the web control or anti-spyware installed and the avast behavior shield installed. I will go further ans say I haven’t had a single entry in the behavior shield log relating to any outpost component/file.
If you care to read my other posts I don’t exclude any outpost folder and only one outpost file C:\Program Files\Agnitum\Outpost Firewall Pro\wl_hook.dll (something I did way back in avast 4.8 that I carried forward) and that is in the file system shield, nothing in the behavior shield and no problems.
Not to mention it really is nothing to do with the outpost issue I recounted above or the same problem would exist with or without importing saved configurations.
Hi David…
Do you have “Monitor the system for unauthorized modifications” in behavior shield unticked?,while running outpost?.If not don’t you think there may be a possibility of conflict with outposts proactive protection there?.
No I don’t it is enabled as it is a default setting and I haven’t had and conflict since this was introduced in early avast6 testing. So I have had these settings on two systems XP Pro and win7 and no conflict with the behavior shield from when this was introduced early in avast6 beta trial and regular builds. My problem with outpost in the win7 system could hardly be down to any conflict as it never even got to boot.
I have the outpost system guard enabled and essentially cover unauthorised system modifications and don’t really see that as a problem either, if avast gets in first on an area and blocks a change to the system then outlook wouldn’t see it and vice versa, one would have to be first.
I don’t have the File & Folder lock enabled (default setting I believe) as I don’t have any folders I’m overly concerned with.
I am getting frequent BSODs after installing 7.5.1
should i revert to 7.5?
Hi ,
He said agnitum support not the forum ;D. I also confirm that agnitum people from “support@agnitum.com” told me that these features does not conflict with avast :o atleast web control don’t as I am using it and don’t find any conflicts.
Try uninstalling in safe mode and then a reinstall, worked for me.
+1 
I guess it depends in part on a users OS /setup etc.All im saying is that 2 web scanners could = slow internet /page loading etc.2 hips or behavior blockers is much more likely to cause bsods and erratic behavior of an OS.
reinstall in safe mode?
no more BSODs?
craigb means uninstalling in safe mode and reinstall in normal windows (not in safe mode)
i uninstalled 7.5.1 in normal windows and reinstalled 7.5.0 in normal windows too. seems working fine. if I want to reinstall 7.5.1, should i uninstall 7.5.0 in safe mode and reinstall 7.5.1 in normal windows?
I would try installing over top first and if that doesn’t work and you get BSOD’S then use safe mode to uninstall and reinstall 7.5.1 in normal mode.