DinGo

Think I may give this a go after your comments Phoenix. Did you do a clean install or install over v9 ?

The last number is irrelevant as it identifies localization builds with no change in the program code. Thanks for clarifying that Marcos.

Announced here on Dec 9: https://forum.eset.com/topic/6889-eset-nod32-antivirus-version-90349-is-available/. I was thinking the OP was asking what the changes are between 9.0.349.0 and 9.0.349.14 are.

No problem getting on that site here. Running NOD32 version 9.0.349.0

I'm running NOD32 v9.0.318 and HIPS is working fine with Windows 10 Threshold 2 here. Try updating NOD32 to v9.

Slightly off topic Marcos. Windows 10 Threshold 2 (SR1) is due to be released sometime in November. Will HIPS be fully functional for this release?

Like most here I don't think there should be a free version of ESET NOD32. I've used NOD32 AV for at least 12 years now and I'm happy to buy a renewal licence when it's needed. Before I moved to NOD32 I tried a whole host of paid for and free AV software and not been entorely happy with them. The simple reason I've stayed with ESET products is they work well with good virus detection and do not hog system resources. My current licence expires in December and once again I'll be purchasing a 2 year renewal. for me it's a no brainer. As an aside, version 9 is working far better with Windows 10 than version 8 did. For me version 9 starts up as soon as I reach the desktop whereas version 8 used to hang for around 30 seconds. Anyway back on topic, my feeling is you get what you pay for and ESET AV is great value for money.

Thanks for the reply Marcos.

Several weeks ago ESET staed there would be a fix, possibly only partial to enable HIPS to run on Windows Insider builds of Windows 10. @ Marcos, is there any update on this?

Windows 10 build 10537 is a leaked build and it's inadvisable to use it. The latest official Windows Insider build is 10547.

The issue with "incompatible" Win10 builds (published to Fast ring) will be solved in final v9 release. That's good to hear Martin I'm reluctant to leave the Fast Ring yet as for me Windows 10 build 10532 is far faster and more stable than the RTM build 10240.

You can sign up with Microsoft as a Windows Insider and receive preview builds of Windows 10. This is not really advisable on your main PC though due to the possibility of the preview builds containing bugs.

The latest build of Windows 10 which is currently supported by ESET is 10240. If you have opted for insider preview builds (fast ring updates), HIPS will not work. In the future, we plan to make HIPS work with such builds with limited functionality. That's good news for Windows Insiders Marcos, thanks.

Still broken 22 August 2015 @11:30 am Pacific Daylight Time How do I check if HIPS is working or not? Double click the ESET tray icon and the console will open up. Select Setup on the left hand side then on the right of the screen you will see whether HIPS is enabled or disabled. If it is disabled then try enabling it, if you are running Windows 10 build 10525 then NOD32 won't let you enable HIPS.

This has been discussed and answered in 2 other topics at least. Build 10525 available on fast ring won't be supported unless Microsoft provides symbols to vendors. Marcos, are you saying that Microsoft don't send your devs new symbols when they release a new build? I would have thought it would have been an essential thing for them to do and also for them to realise that not everyone wants to use Defender.

Thanks Marcos. Build 10525 was only released to Windows Insiders yesterday, so it's early days yet but I assume alot of the code is likely to be part of Windows 10 SR1 which will allegedly be released in October.

HIPS is now broken again by build 10525 of Windows 10 (insider preview}. To make it worse I'm also getting a popup advising me to enable Windows Defender

I had the same problems as you when trying to set up Process Monitor for Boot Logging SMK. I tried to take Ownership of Driver directory to get around the problem but it was having none of it. Any ideas Marcos?

Running NOD32 version 8.0.319.0 in windows 10, I get a delay of up to 50 seconds after reaching the desktop before NOD32 appears in the tray. I realise this is probably a Win 10 issue but is anyone else experiencing the same?

I second that. uTorrent was fine around 4 years ago then it started loading its installers with all sorts of malware. An alternative apart from qBittorrent is Tixati which once you get used to the GUI works well and is free from any rubbish.

Just tried NOD32 Beta 9 x64 on Windows 10 x64 and got the same errors. Also activating NOD32 was impossible, I just ended up in a loop. No way to put the username and key in. Still, I guess that's just one of the joys of beta testing.

Having the same problem with Win 10 build 10166.

Yes IMO it isn't necessary to uninstall it too. So I read your post again think your problem is not that you see the blue messages, but that you don't see them anymore in v8. Are I'm right? So if this is the case then I don't know whether this is a problem, by design or you just can open all objects now. I can only say that I see in almost every case these messages. So to troubleshoot if this is really a problem: Have you tried to scan the boot sector. In many cases there is something that cannot be opend. Have you checked all your logging settings and you're ThreatSense settings? Do you know how to change the permission for a file? If so create a file or dir where you disallow the access for all users and especially for the user "SYSTEM". (If you are the owner of the file you can give yourself the permissions later again) This file should now be not possible to scan. Now try to scan the file and look whether you see this messages. If you want to see more messages (about files scanned etc.) you can activate the option to log all objects in the ThreatSense settings. For instructions read this kb article. The article describes a solution for another problem, but in step 6 there is the option I mean. Yes that's correct. My problem is that in V7 I saw the blue messages when I scanned as Administrator and not Administrator. In v8 I see blue messages if I scan as not Administrator but no blue messages if I do scan as Administrator. Could be that it's working correctly in v8 and locked files are being scanned when running as Administrator therefore no blue entries. When I run a manual scan I run an in depth custom scan on everything, every fixed drive including memory and boot sector.

I haven't got a problem with uninstalling as I've done it many times in the past. It's just not necessary to post a couple of screenshots with one showing a blank scan log and the other showing blue entries in the log. It isn't something that bothers me too much, I was purely interested in why it was happening as I hadn't noticed with any previous version of NOD32, I've been using it since version 3.

Thanks for the reply rugk and I've had a read of the links. However I'm not about to uninstall v8 and replace with v7 to do screenshots. The most I can say is that running as administrator on v7 I got a lot of blue entries in the scan log, in v8 I get none. It's not a big deal I just wondered what had changed to cause this.