DinGo

What version number of NOD32 are you showing ram1220?

At first I thought the same Phoenix but now I've tried it a few times it makes sense to hide the option away. It was too easy before to disable protection.

I was just about to post the same but visited here and saw your post Phoenix I always found the pause protection useful if i was having problems with new software, it enabled me to rule out NOD32 from causing the problem.

Yes I got one at weekend Phoenix and did a clean install A good call in your previous post by the way.

I did a clean install of Redstone 2 last thursday and pleased to say NOD32 version 10.0.390.0 is ruinning fine, no problems at all. RS2 recived a cumulative update on Friday night which took it to this build:-

No Phoenix the new build i mentioned hasn't been released or leaked yet. It's probably just an internal build.

Looking at the Creators Update build feed. I tlooks like the version has gone up from 15063.0 to 15063.2, so there are probably small bugfixes still going on. https://buildfeed.net/build/85a0f7fb-31ef-48fe-b7b3-e68b3d4797ec/

Thanks Phoenix, I downloaded build 386 from an official ESET server this morning

Yes I just noticed that on MajorGeeks but can't find it on any of the official ESET servers yet. Update I downloaded the file fromMG which was linked to an ESET server but when checking the file out it was build 369.

Personally I'm having no problems whatsoever up to now. I ran the beta of NOD32 v10 when it first came out with no problems either, the final seems even faster and smoother.

I wouldn't have thought so as ESET ormally advise a clean install once the final release comes out. It could have changed though. It may work but I have found that the best practice is to do a clean install of the final release. Some changes between the last beta and final may cause some issues. I have every intention of doing that when the time comes. I'm not online all the time and I didn't want a surprise of non working protection system when I boot up. Eset will more then likely have a final release out by the expiration date or extend the expiration date as needed. I've entered my license key so should be ok anyway. I'll definitely do a clean install when the final is released though. TBH to me this hasn't been like a beta test, I've seen no major problems throughout it. The odd minor niggle but has always seemed like a finished product.

I wouldn't have thought so as ESET ormally advise a clean install once the final release comes out. It could have changed though.

You can always open the NOD32 Cosole and select Help and support. There is an option to Change License, if you click on that button you can insert the key that you are registered for version 9 or lower build. That is assuming that the key you use isn't already in use on another machine.

It's running fine with Windows 10 version 1607 here. As a Windows Insider I've been running 1607 for just over a week now so I would have noticed any compatibility problems by now.

Pleased to see this new release is working fine with Windows 10 insider build 14385 A good job ESET.

Thanks for the replies. I'd missed the fact that it was disabled by default.

After installing the first build of NOD32 AV version 10 beta I got a popup from the system tray telling me that the Virus Signature Database had succesfully been updated. (as always happened in previous versions) Since updating to build 10.0.169.0 and subsequently build 10.0.171.0 the popups have disappeared. I've checked the updates module and my virus definitions are still being updated on a regular basis. Is anyone else seeing this?

@TomasP: No answer? And no Information? In the following weeks, there should be a newer build available, containing all the recent bugfixes, being another step closer to the final release. As for when that happens, you have to wait and see, for the time being Tomas when the final release comes out I assume it will be fully compatible with the upcoming Windows 10 Anniversary Release?

That didn't work due to denied access when running the command: so here is the final solution to install the latest update thanks to xxJackxx: 1- While NOD32 is running, go to the start menu > ESET, then right click on ESET NOD32 Antivirus icon and choose run as admin. 2- This will re-launch the GUI in Admin Mode with full privileges 3- Now run the update again and you will immediately notice it is actually downloading the files then will proceed with the installation. 4- Reboot when prompted to do so to complete the installation Note: If you want to save the installer for future use, it is located in: C:\ProgramData\ESET\ESET NOD32 Antivirus\Installer and is named: NUPEFEF.msi this way you can install the latest version in the future right away Thank you Phoenix, good advice.

Thanks for the reply Marcos.

I've noticed with NOD32 version 10 beta there are frequent updates of modules. Nothing unusal there but the updates are far more frequent in the beta builds than you would see in final versions, which can be expected. Is there anywhere we can see what has changed in the modules, ie fixes applied etc. If not then could one of the ESET mods post the changes in a sticky thread on this forum.

While these requests are being discussed. I'd really like protection for my desktop icons

I've had NOD32 v10 beta installed for 24 hours now and it's running very well. The new GUI suits Windows 10 very nicely and it seems as lightweight on resources as varsion 9 No errors relating to it showing up in Event Viewer. I'm happy to use this as my regular AV until v10 final is released. I noticed that 3 of the modules were updated today. UPDATE Been using version 10 for a week now with no issues found

Just installed NOD32 beta 10 and so far I'm impressed. Looking around the interface and options I can't find a reference to gamer mode. Am i missing something or is this included as a default setting now. UPDATE Sorry, please ignore the above, I just found it

Thanks for the reply Phoenix. Yes I would normally do a clean install as routine, I just wondered if you'd tried installing over the top of version 9.