InexNV 0 Posted August 26, 2013 Share Posted August 26, 2013 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 Link to comment Share on other sites More sharing options...
Administrators Marcos 4,922 Posted August 26, 2013 Administrators Share Posted August 26, 2013 If you connect to the Internet via wi-fi or DSL, it may take more time until an Internet connection is established. Does v7 update automatically after an hour when the program attempts to update next time? Link to comment Share on other sites More sharing options...
Arakasi 549 Posted August 27, 2013 Share Posted August 27, 2013 Does clear update cache help ? Also does this only happen on startup - automatic update ? Or as Marcos asked, every single hour ? If you can catch an exact time of when the update starts. You can check event viewer and see possible if there is something going on at the same time. Link to comment Share on other sites More sharing options...
SweX 871 Posted August 27, 2013 Share Posted August 27, 2013 And you haven't changed anything in the Scheduler? Found in the GUI -> Tools -> Scheduler Link to comment Share on other sites More sharing options...
InexNV 0 Posted September 9, 2013 Author Share Posted September 9, 2013 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 Link to comment Share on other sites More sharing options...
Nerius 0 Posted September 20, 2013 Share Posted September 20, 2013 I have this problem too. Everytime computer is booted up. Annoying. Never had this problem in ESS v4, where it waited for the connection to be established. Link to comment Share on other sites More sharing options...
DinGo 22 Posted September 22, 2013 Share Posted September 22, 2013 I get the same problem in V6.0.316.1 but only if I wake the computer from sleep mode. I have no problem after a boot up. Link to comment Share on other sites More sharing options...
Arakasi 549 Posted September 26, 2013 Share Posted September 26, 2013 It makes me wonder if Delayed start would work or if it would be a security risk... *referring to services Of course due to strong permissions and security the normal user cannot change the service to delayed start. Which would put it 2min starting after the last service started successfully. I know through registry you can change that 2min to shorter, but that window of opportunity would be bad. Will be neat to see how they handle this issue. Link to comment Share on other sites More sharing options...
Petu 0 Posted September 29, 2013 Share Posted September 29, 2013 (edited) I have not the exact same problem but: As i remember ESS updates his Signatures after every reboot or coldstart IF there are new Signatures. The Taskplaner shows that the Task has been running, but it did not update the Signatures. There is no Error in the Logfiles. I double checked if there are available updates @ hxxp://www.virusradar.com/en/update/info/. However, the manual update works and the regular updates every 60 Minutes works too. But if i use my computer every day for lets say 45minutes, ESS will never update automatically. I'm not on a dial up connection, I have Internets via Cable. ESS Version: 7.0.207.5 Again: As i remember this worked automatically on bootup in V6. EDIT: I use Windows 8 64bit. My wife uses Windows 7 64bit with the same Version of ESS and i forgot to mention: Her updates are working without any flaws. Edited September 29, 2013 by Petu Link to comment Share on other sites More sharing options...
InexNV 0 Posted October 20, 2013 Author Share Posted October 20, 2013 (edited) 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 Edited October 26, 2013 by InexNV Link to comment Share on other sites More sharing options...
InexNV 0 Posted June 27, 2014 Author Share Posted June 27, 2014 (edited) 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 !! Edited June 27, 2014 by InexNV Link to comment Share on other sites More sharing options...
SweX 871 Posted June 27, 2014 Share Posted June 27, 2014 (edited) AFAIK, There are not a lot of users reporting about this problem, in the forum anyway. But if ESET can't reproduce an issue/problem in-house then it's a good idea to work with them by sending in logs. Just a suggestion if you haven't done that already of course. Edited July 1, 2014 by SweX Link to comment Share on other sites More sharing options...
ESET Insiders TJP 143 Posted July 8, 2014 ESET Insiders Share Posted July 8, 2014 I have the same update issue when I first sign in; I'd estimate the error occurs 50% of the time with Windows 8.1 Pro (x64) and ESS 7.0.317.4 To be honest, I just presumed it was a Windows 8.1 issue as ESS updates fine at start-up with Windows 7 installed. Link to comment Share on other sites More sharing options...
InexNV 0 Posted October 11, 2014 Author Share Posted October 11, 2014 (edited) 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 Edited October 11, 2014 by InexNV Link to comment Share on other sites More sharing options...
InexNV 0 Posted October 11, 2014 Author Share Posted October 11, 2014 I have the same update issue when I first sign in; I'd estimate the error occurs 50% of the time with Windows 8.1 Pro (x64) and ESS 7.0.317.4 To be honest, I just presumed it was a Windows 8.1 issue as ESS updates fine at start-up with Windows 7 installed. Win 8.1 starts up faster then Win 7 also I don't use win 7 anymore Link to comment Share on other sites More sharing options...
Recommended Posts