Introducing, The New Prevx Edge.

Same here. I don't think it's AGV as you suggested because I don't have any security on the PC where this is happening except Edge.

I got so fed up with reinstalling v180 and constantly restarting to kick protection into life (unsuccessfully)that I reverted my system with ISR to before the upgrade. No probs with v172 at all.

 

Threat identified in File

C:\Documents and Settings\*****\SpywareTerminatorSetup.exe

If i dont remember wrong, SpywareTerminator identified Prevx
CSI 2 be malicious.

Prevx Edge is now telling me that SpywareTerminator is malicious.

Just so u know !

TCSP

 

Just to clarify I also wasn't experiencing this problem with version 172 as it has only started to occur after manually updating Prevx Edge by downloading the latest version from the website and executing it (which updated the installed client from v172 to v180).

This problem is very frustrating and as a temporary solution I have disabled the AVG resident shield which appears to be working but as Clive has commented the problem is also replicated on a system where AVG is not installed meaning that it may be a more fundamental problem then a simple compatibility issue.

 

Check again, it's now fixed

 

Hello,
We are working on this issue and should have it solved shortly. Sorry for the inconvenience, and this is not directly an AVG problem (as it is seen from other security software as well).

We don't have a patch just yet, but we will soon. Thanks again for your patience!

 

Thanks for the update. I am glad that it is not a compatibility problem with AVG.

My advice to Prevx would be not to rush the update out at the expense of potentially introducing other problems as I have a sneaking suspicion that v180 was rushed out without sufficient testing to fix the compatibility and self protection issues and unknowingly introduced this problem. (Saying that I could be totally wrong).

Once again thanks for the timely support and I eagerly await this fix.

Cheers
Ben

 

It actually appears as though these problems have existed for longer but were obscured by the self protection issue. We're implementing a new piece of code now which will correct them, however, we are definitely going to be going through an extra round of testing against multi/many AV configurations (which aid in reproducing these issues) to double check that everything is working properly

Thanks again for your patience while we sort these out!

 

Still running perfect here

 

Some (useless) thoughts about colours...

If a security application shows an alert message with a green and a red button, which one would you click? I would prefer the green one. Green stands for safety, red for danger.

Fortunately Prevx Edge shows only "one" button. I like this idea to "hide" the not recommended actions.

But anyway... Imagine: In the threatening, dangerous "red enviroment" of an infection-alert there would be a peaceful, confident GREEN button (block/cleanup), leading the way back to safety...

Got the idea? I think pressing a green button is more logical and feels more comfortable, while a red button could feel like doing a dangerous action. (?!?) Maybe - but I'm not sure about it.

...and I know that there are MUCH more important things.

BTW: At the top of the small window during the initial scan is a Prevx logo, but on the top of the main screen of Prevx Edge is just "plain" text - no logo. Is that wanted?

 

Not useless thoughts at all

You should see how much discussion went into to deciding the colors.... and honestly, it can go either way. Technically speaking, the entire dialog should be green as the threat would have already intercepted at that stage. I will, however, bring it up with our graphic designer as I agree with your points, but he probably doesn't want to hear it again as we will just go in circles

Also, regarding the Prevx logo on the pages - that is intentional but probably not the most consistent of designs. I'll see what we can do about getting everything the same Thank you for your suggestions!

 

i disagree,

the colour red, brings it to my attention.

green, certainly would not.

 

Noooooooooooooooooooooooooo, not this conversation again

*puts fingers in ears and sings to himself*

 

And herein lies the discussion We also have Cleanup Now red always even though it eventually gets you to a clean system. I don't think there is a straightforward answer to this. We "could" always make it brown, a combination of green + red, but I don't think PrevxWebDesigner would be too happy with that

 

Oh I'm not so sure - brown is very "in" at the moment

 

again, your wrong.

anything that 'requires attention' by the user, is always red.

this is how it is, and how it always will be.

even with the full list of security products that are available today, they are all the same, anything that needs attention, is red.

...........redddddddddddd i tell ya!!!!

 

Red = alert!

 

Why not red and the closer you get to the button with the mouse it turns to green

 

um, no! Brown is the color of poo! No brown.

Don't change a thing

 

I agree I think we'll just leave it and hope that it's clear enough I do think that red is generally the normal color for a warning prompt, even if the warning has already been taken care of behind the scenes.

 

I understand. Going in circles is no way to get forward at all. And I have no problems with your inconsistent design if it is intentional. I just was wondering. Thank you for your reply!

BTW: Prevx Edge runs on 3 PCs without any issues. It is "Beautyful" and SOOO light - unbelieveable. The whole Prevx Edge installs quicker than my other security product can update its signiture database.

 

ROFLMAO

 

The GUI looks great as it is very attractive and easy on the eyes.Whats at most important now is under the Hood so to speak.

 

Wow....look what I missed the past couple days.

I can confirm the start up problem with SAS Pro on with realtime enabled also. If I disable it the boot problem goes away. I rarely use the realtime protection in SAS so its no biggie. Something to keep PH busy and out of trouble.

 

I think the GUI is A-OK also. Wouldn't change a thing.

 

Nice idea!