Thursday, April 14, 2011

Outpost 7.5 enters Public Beta #2 phase

Yesterday, on April 13, Outpost 7.5 - Performance Edition became available as Public Beta #2. Second Public Beta is based on first public beta feedback and internal work-outs.

As always, you’re welcome to check out Outpost 7.5 Public Beta #2 and share your impressions.

What’s new in Outpost 7.5 Public Beta #2? 
- New Auto-Learn and optional security alerts on trusted application activity
- Allow Once / Block Once options restored
Learn More

Check out the Public Beta #2 versions of Outpost Pro 7.5 today and provide your feedback.

7 comments:

titi said...

outpost 7.5 beta 2 is disappoint for me.
real time protection have old problems with some kinds of files.
also outpost realtime protection is very heavy for file analysing.
decrease my system speeds completely.!!!???
also anti leak in non auto learn mode allow most screenshots and keybord logins.

agnitum said...

Dear Titi, please keep in touch with our support team. Outpost 7.5 is still in beta, so please report all issues to go ahead with privacy and analyzing tools...
BTW, any deep analyzing tool cannot be light-weight for your PC.

Anonymous said...

with avast installed Outpost disables its Web control feature..Which is ridiculous, because when I install Outpost firewall(with Web Control) first and then avast, they both work just fine together. I failed to understand why does Outpost asks for choice to install Web Control after detecting avast when it know that it will be turned off.????

Anonymous said...

I think web control should not be disabled as it works fine with avast free and pro..

You should give us option to enable it

agnitum said...

Please contact our support team to solve that question - this is automatically solved compatibility issue.

Anonymous said...

agnitum support parts do't true report for outpost suppliers.
i give report last month about one problem in oss.but still that, exist in outpost ss.

agnitum said...

Please be patient - support team cannot fix the issue by themselves, they only report it to R&D department and monitor regularly whether the issue was resolved.