leosuth

Just in case this helps 😉 I use Outlook 365 Same problem here - log: Time;Scanner;Object type;Object;Detection;Action;User;Information;Hash;First seen here 27/08/2020 12:23:37;IMAP filter;email message;from: "MRS. GRACE ALLEN"<gitlab@jbcloud.tokyo> with subject I'M A CANCER WOMAN HELP ME dated Wed, 26 Aug 2020 21:23:07 -0700 ;HTML/Fraud.EK trojan;contained infected files;DESKTOP-********\***********;Event occurred upon receiving an email by the application: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE (4EFC5B419545D8BEF94562B5B37F7CB826AFB8CE).;B6F39053914FA3C684E51EB99EA8A9792C786A34; NOD32 set to delete emails on detection, as suggested above - so I don't think that works (at least - see below - when download not to Inbox?) I have two accounts, one with Gmail, the other with Virgin. I went to the webpage for Gmail - that email does not exist there. But as a matter of course, I cleaned out everything from there since I don't really use Gmail. Also, I haven't got Gmail mapped in Outlook anyway - but I thought it worthwhile checking and having a clean out On Virgin front end, I found the email hiding in the Spam folder. I deleted this, then tried download again - still detecting. I finally found it hiding in the Deleted folder (Trash) - Doh! So I deleted it from there as well, and now it is no longer being detected. I also took the opportunity to do a clean-out there as well. Looks like Outlook365 downloads the contents of the Spam and Trash folders as well🤨, which was why it was being detected so the lesson is to check in ALL folders if this kind of thing happens and not to assume things. Anyway, thought I'd share with all, hope it helps some.

Just wanting to check that v9.0.402.0 is being fixed/replaced with respect to the disabled HIPS problem - and maybe any idea of release date, maybe? Apologies for pestering

Ah OK - had me well confused

When you say HIPS is broken, do you mean you are having problems with https: websites? hxxp://imgur.com/a/vF7ga I also have a problem with Firefox 48.0 and add-ons from Mozilla the download never finishes and throws an error comment every time. This all happened yesterday also. Update: If I disable Web & Mail > SSL/TLS > Enable SSL/TLS protocol filtering my browser works like it should. Can anybody explain to me why that is as I am not computer literate enough to work it out myself. I guess I worded that badly. I am referring to the problem of not being able to start HIPS - I believe the cause being something to do with problematic communication between Windows 10 (Windows Security Centre?) and NOD32

In the end, I had to bite the bullet and reinstall NOD32 as download from site - it's up and running now with HIPS enabled, all looking good except that (for now) running 9.0.386 (I think) with automatic updates disabled for the time being so I can manually update the database each day while not having the app itself updating (dodging HIPS problem I hope). Just until the HIPS problem is resolved, then back on auto-update it goes!

Does the problem persist after upgrading to v9.0.942 and restarting the computer once or twice make a difference? Should the problem persist, run "sc quert ehdrv" as an administrator and post the output. Well, as I reported in my other (related) post, I got an auto-update to 9.0.402 a couple of days ago, which also exhibited the same HIPS syndrome. v9.0.942 is another update in the last couple of days? App hasn't picked that up as available? I'll need to look at this evening, but does it specifically address the HIPS problem?

Night before last after NOD32 was updated to previous version (dunno what that was), HIPS got broken. After a lot of faffing around, including uninstalling and reinstalling, I managed to restart it by doing a Pre-release update - it worked fine all day yesterday. Last night, another update was done to v9.0.402.0 .............. HIPS IS AGAIN BROKEN!!! (and also Device control reported as non functional) This time trying a pre-release update doesn't appear to do anything useful - do I have to uninstall it once again? Apologies, but this is beginning to get beyond silly - do I give up with NOD32 (which I have used for years with no problems) and get something else, or do I just ignore the red warnings and carry on regardless? I'm on Windows 10 build 10586.545

Only a year later Got exact same problem with NOD32 v9.0.386.0 on Windows 10 build 10586.545