PrevxHelp
September 29th, 2009, 04:39 PM
Hello all,
This build is a minor upgrade over 206, fixing a few incompatibilities but overall the protection has not changed significantly. To retest the changes after upgrading, just close/reopen your browser. The download links are still:
32bit: http://info.prevx.com/download.asp?grab=edgebeta
64bit: http://info.prevx.com/download.asp?grab=edgebeta64
! IMPORTANT - PLEASE READ !
We found a bug in the upgrade process which could cause an older component to persist on the system and not be upgraded, which looks to be the reason for some of the issues persisting that we thought were fixed. If you could please try uninstalling and installing the newest v3.0.4.213 on top, this may fix some of the persistent issues.
The changelog between 206 and 213 is:
- Fixed an issue with the Opera cache causing downloads/some pages not to load
- Fixed an issue identify illegitimate HOSTs file entries
- Fixed an issue blocking the Refresh button in IE8/Win7
- Minor changes which should improve Firefox graphical behavior on-load
- Added identification of incompatible programs
- Fixed compatibility with NIS2010
- Fixed compatibility with Ikarus
Known Issues:
- Some incompatibilities with Fritz!Protect firewall
- Possible issues with some download managers (if you experience any, please send a scan log to report@prevxresearch.com - we're adding exceptions for them as much as possible as they are reproduced :))
- Possible (unreplicated) issue with Threatfire v4.6.0.19
- Possible issue cleaning the Trojan Simulator
- Opening a new window in Opera prevents Prevx from monitoring the window properly
Conceptual Incompatibilities:
- Defensewall is expected to block Opera support as it prevents browsers from reaching trusted components (Prevx) so we are not able to load some protection/monitoring into an Opera browser protected by Defensewall
- SAS and MBAM scanning is sometimes slowed when Prevx is active: This is an issue stemming back a while and is solved by stopping Prevx protection while scans are taking place. We're investigating whether it would be possible to identify the operations SAS/MBAM are making in the system to prevent us from intercepting their file reads to improve their scan times.
Next Steps:
- Add Safari Support
- Add Iron Support
- Add Maxthon Support
- Add a "Reset to Default" button
Please let me know what you find! We had relatively few reports of problems with build 206 and are hoping to continue fixing any stray issues that come up :)
This build is a minor upgrade over 206, fixing a few incompatibilities but overall the protection has not changed significantly. To retest the changes after upgrading, just close/reopen your browser. The download links are still:
32bit: http://info.prevx.com/download.asp?grab=edgebeta
64bit: http://info.prevx.com/download.asp?grab=edgebeta64
! IMPORTANT - PLEASE READ !
We found a bug in the upgrade process which could cause an older component to persist on the system and not be upgraded, which looks to be the reason for some of the issues persisting that we thought were fixed. If you could please try uninstalling and installing the newest v3.0.4.213 on top, this may fix some of the persistent issues.
The changelog between 206 and 213 is:
- Fixed an issue with the Opera cache causing downloads/some pages not to load
- Fixed an issue identify illegitimate HOSTs file entries
- Fixed an issue blocking the Refresh button in IE8/Win7
- Minor changes which should improve Firefox graphical behavior on-load
- Added identification of incompatible programs
- Fixed compatibility with NIS2010
- Fixed compatibility with Ikarus
Known Issues:
- Some incompatibilities with Fritz!Protect firewall
- Possible issues with some download managers (if you experience any, please send a scan log to report@prevxresearch.com - we're adding exceptions for them as much as possible as they are reproduced :))
- Possible (unreplicated) issue with Threatfire v4.6.0.19
- Possible issue cleaning the Trojan Simulator
- Opening a new window in Opera prevents Prevx from monitoring the window properly
Conceptual Incompatibilities:
- Defensewall is expected to block Opera support as it prevents browsers from reaching trusted components (Prevx) so we are not able to load some protection/monitoring into an Opera browser protected by Defensewall
- SAS and MBAM scanning is sometimes slowed when Prevx is active: This is an issue stemming back a while and is solved by stopping Prevx protection while scans are taking place. We're investigating whether it would be possible to identify the operations SAS/MBAM are making in the system to prevent us from intercepting their file reads to improve their scan times.
Next Steps:
- Add Safari Support
- Add Iron Support
- Add Maxthon Support
- Add a "Reset to Default" button
Please let me know what you find! We had relatively few reports of problems with build 206 and are hoping to continue fixing any stray issues that come up :)