Jump to content

InexNV

Members
  • Posts

    9
  • Joined

  • Last visited

About InexNV

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Belgium
  1. Win 8.1 starts up faster then Win 7 also I don't use win 7 anymore
  2. Still not fixed for the final of version 8 They should build in a delay for checking updates and the problem will be solved I had the same problem with the first version of 6 but the have fixed it But they can't fixed it for version 7 and also not for the new one 8.0.301.0 SAD Back to Version 6.0.316.1
  3. Waw we have an update Still not fixed i see What a joke Why the hell can't they fix it They have fixed it for V6 but for V7 it's to difficult Let's go back to V6.0.316.1 Works perfect !!
  4. Glad i'm not the only one that have this After a month still not fixed https://forum.eset.com/topic/831-nod32-701040-not-updating-automatically/
  5. Installing the final didn't fix anything What's the point of testing out a beta if they can't fix it in the final anyway Going back to V6.0.316.1 Works perfect OS: Win 8.1 Enterprise x64 HDD: Samsung 840 SSD 250GB
  6. after an hour it updates fine. But next day when you start up the computer you see this error again NOD32 immediately checks for an update before DNS is resolved. NOD32 recognises it can't update so flags up a problem Same thing that happend with the first version of Version 6 (6.0.308.1) They have fix it for this version in version 6.0.314.2 and later versions of 6 So let them know this so they can fix it when the final version of 7 comes out Going back to V6.0.316.1 Works perfect
  7. the problem i had with V6.0.308.1 is back see hxxp://www.wilderssecurity.com/showthread.php?p=2206656#post2206656 I don't have any problems with V6.0.316.1 V7 updates fine when i do it manually But the next day when i start up the pc i see this error again Hope you can fix this for V7
×
×
  • Create New...