Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location

Recent Profile Visitors

1,270 profile views
  1. I'm just using Nod 32 Antivirus and not the other versions, but I'm also seeing some strange behaviour after I was upgraded to version After rebooting to complete the update I got a notification from the Windows action center that said something aloung the lines of "neither Eset or Windows Defender is turned on", even though Eset was all green in the Windows Security Center and running in the taskmanager. I have not been able to recreate that though, it only appeared after upgrading to and rebooting to finish it. Now whenever I turn on my computer it would seem that W
  2. Hello again. After Archive module 1283 was installed the "QUICKBATCH" errors no longer appear in scan logs! So it would seem the problem has been corrected. I'd say we can mark this as solved 😊
  3. Ah I see, then it should be fine. Thank you for the update 😃 Would you like me to let you know if any more of these detections starts to appear in the future scan log for files?
  4. Thanks for the reply. Good to hear that these are being looked at.
  5. Hello again. Do we have an update in regards to these "QUICKBATCH" detections? It's worth noting that I have checked all the files in question on VirusTotal and they all came out green. I have always used HitmanPro to check them and the rest of the PC and it doesn't pick up anything either. Thanks in advance.
  6. I've PM'd you the download link for the various files. If they don't work let me know and I'll upload them elsewhere. Also it would seem that I missed 2 "QUICKBATCH" entries in the prior scan log: It turns out there is also 2 entries for "QUICKBATCH" for the two Windows10.0-KB4480116x64.cab detections. Pretty sure that one is from yesterdays patch Tuesday update. Sorry for missing it in my first post.
  7. Hello everyone. Since updating Windows 10 to version 1809 and Eset Nod32 Antivirus to version I've noticed some interesting results in the log after performing a full system scan. I'm fully aware that all results that show up in yellow text is currently in use by the OS or other programs, and should be safe, but these particular entries I'm a little suspicious about due to Eset's description of them: The results I've marked translate from Danish to English as follows: "QUICKBATCH - error - unknown compression method." What's interesting is that prior to yesterday
  8. Ah I see. I will edit my original post then. And good to hear that my version of Nod32 AV is compatible. Sounds good! Thank you guys.
  9. Hello. I see that Windows Update is now offering the new Windows 10 October 2018 Update (Redstone 5) and I'm simply wondering if Eset Nod32 Antivirus is ready for and fully compatible with the new W10 version? Thanks in advance.
  10. Hey guys. Seems like something similar is happening on my end, though I'm using Eset Nod32 Antivirus. I ran a manual update in Eset and noticed that it took quite a few minutes for it to finish. Usually it only takes a few seconds. Being curious, after the update had finished, I clicked update again to see if it would act the same way this time. It kept hanging for a while and eventually came with an error in red text "Product was not updated. Transfer was interrupted" (translated from Danish). Screenshots attached: As you can see the first update went through, even though it took se
  11. Okay, so at least it isn't just on my end then. Forgive me, but what exactly do you mean by "your Eset HIPS protection status is not affected by these error messages."? Does this mean that I in theory can't trust the Green status for my HIPS because of errors and that it may in fact not be working as intended, even though the Eset UI shows everything as "on"? So far they have only appeared once, yes. I have powered down my computer many times, since installing Nod32 again, as I always turn off my computer when I'm not at home. But I'd really like to know if my Nod 32 and HIPS is a
  12. Hello again. I finally decided to upgrade to Windows 10 Spring Creators Update 1803 (build 17134.112). My W10 version is Windows 10 Home 64-bit edition. Before doing so I completely uninstalled Eset Nod32 Antivirus from the machine to avoid potential conflicts doing the W10 upgrade. Yesterday I did a clean reinstall of Eset Nod32 Antivirus using the Live-Installer from the official website. Now I've noticed 2 HIPS related errors in the Nod32 event log. Translation from Danish to English: "Communication with the driver failed. HIPS is inactive." and "The module wasn't r
  13. Hello. I finally decided to upgrade my Windows 10 machine to Spring Creators Update bringing my OS to version 1803 build 17134.112. Before doing the upgrade from W10 version 1709 I decided to uninstall my Eset Nod32 Antivirus version to avoid any potential conflicts and issues doing the Windows 10 upgrade. So far everything seems smooth (fingers crossed). I have now reinstalled Eset Nod32 Antivirus version using the official Live-Installer from the website and the installation was a succes. However, I have now noticed something new in the Task Manager. Under
  14. All of this doesn't sound very good. I think I'll just try an stay on version 1709 for a while longer. Thankfully my system was actually able to receive and install the May 8th cumulative update (KB4103727) and not install Creators Update 1803 aloung with it. Of course it keeps nagging me to update to 1803, but that's Windows 10 for you..
  15. Oh dear that doesn't sound so good. Any chance one of the people working at Eset could respond to this thread? Is Nod32 AV v 11.1.54. fully compatible with Windows 10 Spring Creators Update 1803? Aside from maybe this ui issue MrWrighty mentions.
  • Create New...