Introducing, The New Prevx Edge.

Just to double check - are you using v3.0.0.188?

(And, is Self Protection enabled?)

 

Wow, that was a quick response

Yes, I am using 188, but the self defence was not ticked, so I have ticked it to see if that will help?

Thanks Rollers

 

Let me know if it helps at all Also, what other security products are you using? Some combinations may cause problems with Edge, but, if all else fails, it should restart itself within a few minutes of bootup.

 

Hi, I am only using Esets ESS realtime and prevx edge. The icon showed up but was disabled. Seems ok at the moment, so hopefully that will solve it.

Regards Rollers

 

Is the self-defence option required to be on, to stop the disabled issue?

 

No, version 188 should fix it without self defense on at all, but there could be an incompatibility with ESET which may be more visible with self defense on.

 

Ok, will run and see if the problem replicates. It would be interesting to know if anyone else is running the two together and whether they have run into any problems?
Thanks Rollers

 

I am running Now 188 with self defense on and Nod32 AV 3.0 with No conflics,However I do have Prevx.Exe in the exclusion of nod32.

 

One thing I have found is that even with 188 I had to go into the registry to remove as much of Threatfire as I could in order to stop having problems with Edge.
Even though I had uninstalled TF some part of it was running in the background and giving me a real headache.
I fixed it by restoring an image and then editing the registry.
Hope this help someone.
Edge is running properly now.
Hugger

 

You could have tried this removal tool for ThreatFire:
http://www.pctools.com/forum/showpost.php?p=191047&postcount=11

 

Hi thanks for your response. When you say you have excluded prevx.exe in Nod32 is that the one under advanced set up, exclusions? or do I need to exclude it anywhere else as well? Thanks Rollers

 

Hi there!

Prevx Edge (cleaning/blocking enabled) blocks the updated
version of Rootkit Unhooker (V 3.8.341.552) from installing.

When installed, RKU-executable gets a unique random filename, could it be
that this triggered heuristics?

The log shows it classified as "worm"

Andreas

 

Yes, I'd imagine something to do with the covert process installation, low level system access and random filename is triggering heuristics I'll get it sorted momentarily - thanks for the report!

 

I'm unable to track down exactly which file you have - I installed a v3.8.341.552 copy and it was not detected. Could you send me the scan excerpt from Edge referencing the file (Tools and Settings > Save Scan Results) or send me the file itself? Thanks for your help!

 

Okay, here it comes...

There are some other detections inside, which are at least partially FPs...

Just take a look for yourself

Thanks in advance!

Andreas

Edit: Prevx EDGE alerts when running the installer... not the installed rku itself

 

More fun sitting and suffering.
Hugger

 

We have corrected the false positives and are investigating some of the questionable ones now. Thank you for your help

 

On a side note: there's an updated version of RkU - 3.8.342.554 - at http://www.rootkit.com/vault/DiabloNova/RkU3.8.342.554.rar

 

Just to let everyone know, the double Edge icon in the system tray seems to be fixed with version 188. I'm really happy with Edge and hope that the support from Prevx continues. We all know how support for Prevx 2 seemed to be abandoned. But, I'm guessing it was due to resources being devoted to developing Edge and CSI. Keep up the great support..........thx

 

Great to hear And, as a word of reassurance, I'm not going anywhere

 

Hi guys!

Thanks for the lightning fast fixing, scans of rku installer come up clean now!
(and I have also updated to the most recent version now as EraserHW suggested)

Yours

Andreas

 

True, good help for cheap pay is always hard to find.

 

Yes in the advanced set up for exclusion.The first trial I had version 180 I can not remember exactly what happened but NOD terminated it from running.Besides the fact why let a security product scan files of another security product.IMHO its always a good idea to exclude each other.

 

I seen that today two icons with version 188 then one vanished have not seen it there after.

 

Edge seems to be running fine now with build 188 & Nod v2.7.

Now trying Winpatrol.....