@ Paranoid2000/Outpost Forum SuperMod
1. Outpost's Self-Protection will block any action with the potential to affect Outpost, including copying files into the Outpost program folder or relocating files (including disk defragmenters and registry/file cleanup utilities). There is currently no way to specify exceptions for trusted programs but Self-Protection can be disabled temporarily to allow a specific action. Users running other security software that controls file/registry access may prefer to configure this to cover Outpost's configuration instead.
Self Protection will also need to be disabled when installing Outpost plugins or overwriting their configuration (e.g. using Windows Explorer to replace Blockpost's blocklist.txt file rather than using its Import function).
2. On some systems, Anti-Leak may block access to certain "non standard" desktop items or entries in Windows Explorer. There have also been isolated reports of some applications starting with no window - in such cases, there are 3 possible workarounds:
- disabling Anti-Leak in Options/Application/Anti-Leak (this will obviously eliminate Outpost's ability to block leaktests and malware using similar techniques);
- creating a wl_hook_data.cfg file in the Outpost program folder listing the problem programs - these will be exempted from Anti-Leak. In addition, program checksums will no longer be checked by Outpost so programs included could be replaced or altered without triggering an alert - however this is safer than disabling Anti-Leak completely;
- renaming the wl_hook.dll file in the Outpost program folder (shutting down Outpost first) - this option will also disable Anti-Leak.
4. With Auto-rules enabled, rules created automatically (which will include several global rules, shown in blue) are re-created if deleted (when the configuration is reloaded) - if you wish to remove a particular rule without disabling auto-rules then just disable it.
5. Avast: Standard Shield may cause system freezes if set to High, set it to Normal instead.
6. Process Guard: Secure Message Handling may not work by default with Outpost 4.0 since window closure is done differently (enabling SMH results in File/Exit and system tray Exit options doing nothing). If so, switching to custom SMH (enabling SMH then holding down the Insert key while selecting File/Exit or Exit, see Process Guard's helpfile for more details on custom SMH) should work.
7. Sandboxie: Outpost 4.0 includes new drivers, one of which is called sandbox.sys. This confuses the Sandboxie installer into believing its software is already present - if using Sandboxie, install it before Outpost to avoid this issue. This also means if uninstalling Sandboxie, Outpost will need to be uninstalled first.
Windows 9x/ME users please review the changes carefully - 3 of 4.0's key features (Anti-Leak, Self-Protection and Game Mode) only work with Windows 2000/XP onwards, even though they appear to be present on Win9x/ME installations. While the more advanced leaktests (e.g. Thermite, CopyCat) will not run on Win9x/ME, Outpost 4.0 has been reported as failing Wallbreaker (test 4) so is likely to provide poorer leaktest performance than 3.5 on these versions of Windows.
Further Information:
Please refer to Paranoid2000's outline: What's New; What's Fixed; Upgrading;