Duluc

It may end up being the RTM, but so far it's nothing oficial. Microsoft could end up releasing another Insider Preview for all we know. BTW, I'm also using it and it runs very well on my PC.

I have V10 already on my family's computers, no issues so far. Everything working smoothly.

Sorry for the double post.

Marcos, is the English V10 yet available?

I was actually asking about the English version.

Where's the link? I can't find it in Eset's page.

LOL, yeah. I really can't wait for the final release either.

They are all in the same level though wihch is 2 stars. Don't forget that ESET has a lot of other components that prevent infection in the first place such as PUP detections and HTTP scanning that blocks any malicious connections so the chances of being infected are much better than the competition. In all the 12+ years I've been using NOD32, I never got infected and got 0 false positives. I understand. I've been an Eset user for over 10 years and just yesterday I renew my family's license to 2 more years. No complains on our side. I just got surprised (pleased tbh) that Microsoft is finally upping its game. If Windows gets safer as a whole, we all benefit from it (less chance of propagation). And I'm a Windows guy.

What's really wrong with v10? I've running the Beta and find nothing really wrong with it.

I can't believe Microsoft got higher points than Eset. Microsoft just game 1 point short of the Advanced+ certification.

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. Yep. This beta has been remarkably stable. BTW, I'm about to renew my NOD32 family license to 2 more years.

Will the beta automatically update to the v10 final when it is finally released?

OK, it's true that you have to be careful about everything you download from every site. However, MajorGeeks has been the only software distributors I trust. BTW, this beta has been working fine so far on Windows 10.

This is, yet again, affecting me. NOD32 has become a real pain in the *** after Windows 10 came out. It's not long before a virus signature/component update breaks things in the OS. Later on an update fixes things just to happen in the future again. It's happened way too many times. I'm sorry, Eset, but this time for real I'm not renewing my subcription. Enough is enough.

I have to inform that with the latest modules update (right now) my Gmail account is finally syncing again. Thank you for the quick fix.

The Outlook account (Hotmail) I'm using with the Mail app works just fine. It's the Gmail account that's not syncing. Here are the details of NOD32. Virus signature database: 12910 (20160122) Rapid Response module: 7374 (20160122) Update module: 1060 (20150617) Antivirus and antispyware scanner module: 1474.1 (20160104) Advanced heuristics module: 1165 (20160104) Archive support module: 1243 (20151221) Cleaner module: 1114 (20151004) Anti-Stealth support module: 1093 (20151216) ESET SysInspector module: 1257 (20151113) Real-time file system protection module: 1010 (20150806) Translation support module: 1448 (20160112) HIPS support module: 1210 (20160111) Internet protection module: 1242 (20160114) Database module: 1072 (20150831) Configuration module (33): 1213.9 (20151211) LiveGrid communication module: 1020 (20150807) Specialized cleaner module: 1010 (20141118)

Was working fine yesterday too. Today I find this issue and I'm glad I'm not the only one. I had already deleted and re-entered my email account twice. Please Fix it.

Suffering from the same problem. NOD32 is becoming more of a problem on Windows 10. I'm considering going with Defender. The beauty of NOD32 used to be that you don't have to worry about anything and even forgetting it's even installed at all. Please fix this.

It did happen with v9.0.117 but now I'm on v8 and it's working perfectly. Can't repro it anymore. Sorry.

It seems to be an issue with v9, at least for me. V8 works fine.

Follow up: I installed NOD32 v8 with "Pre-release update" enabled. It installed fine, activated fine and everything works (HIPS and all). No problem with Store or any apps. So I'm staying with V8 until V9 gets this sorted out.

After waiting days to be able to install NOD32 on Windows 10 RTM, I'm facing a particular problem. NOD32 installed and activated just fine, no problem there. But after installing it, the Windows Store and Windows Apps have many issues. Store crashes instantly after interacting with it and many other apps have issues loading content. I concluded it's the NOD32 install that's causing, because after uninstalling NOD32 everything went back to normal and working fine. Can anyone else reproduce this? Is there a fix coming? I'm back to Defender until a fix is found. Thank you. I get this error on Event Viewer whenever it crashed. Faulting application name: WinStore.Mobile.exe, version: 2015.7.22.2, time stamp: 0x55b03689 Faulting module name: Windows.UI.Xaml.dll, version: 10.0.10240.16397, time stamp: 0x55af16e7 Exception code: 0xc000027b Fault offset: 0x0000000000483497 Faulting process id: 0x444 Faulting application start time: 0x01d0c8d8e66045b6 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsStore_2015.7.22.0_x64__8wekyb3d8bbwe\WinStore.Mobile.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: 5b9f5ebe-6f67-453f-9b73-71898d3fc609 Faulting package full name: Microsoft.WindowsStore_2015.7.22.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

Yep, I can reproduce it here too, every time.

Finally!

It's like we're being ignored right in their official support forums. No dates and the dates given are vague enough to be easily broken. "After July 20" Pfffffft