Guest AndreasCGN83 Posted May 15, 2007 Share Posted May 15, 2007 HI!Since Update number 2264 my nod32 doesnt update...fix2.2 is installed and until now it was no problemcan you help?ThxEdit: I looked up with Nod32view the server versions and on the trial server there is only Signature ver. 2264 - have someone more informations about that?the commercial server are all on ver. 2267 or newer Link to comment Share on other sites More sharing options...
pmpalma Posted May 15, 2007 Share Posted May 15, 2007 Got the same problem here Link to comment Share on other sites More sharing options...
1+1=FG Posted May 15, 2007 Share Posted May 15, 2007 Be patient :nono: Link to comment Share on other sites More sharing options...
nsane Posted May 15, 2007 Share Posted May 15, 2007 yeah, the last couple of updates have been kinda big (not just v2265), so they're just letting registered users get them before the eval users. they do this quite often actually :nono:defs are at v2268 now too btw...http://www.eset.com/support/updates.php Link to comment Share on other sites More sharing options...
pmpalma Posted May 16, 2007 Share Posted May 16, 2007 yeah, the last couple of updates have been kinda big (not just v2265), so they're just letting registered users get them before the eval users. they do this quite often actually :Pdefs are at v2268 now too btw...http://www.eset.com/support/updates.phpI've taught of that, but desistalled the fix and NOD32, rebooted, reinstalled NOD32 without the fix, and got updated to 2268, was previouslly stuck at 2264. Installed fix, couldn't upadte to 2269 any longer.Maybe I got lucky and was able to update to 2268? I mean, it is an eval :nono: Link to comment Share on other sites More sharing options...
Guest AndreasCGN83 Posted May 16, 2007 Share Posted May 16, 2007 so its normal? we just have to wait to get the update to 2269? this update seems to be "smaller"- will it be now ever that the eval. have to wait?greetings Link to comment Share on other sites More sharing options...
Guest b52b52 Posted May 16, 2007 Share Posted May 16, 2007 I'm still stuck at v2264 !!!On my other PC i updated the NOD32 Fix from v1.9 to v2.2 and then it worked one single time and updated to v2267 but now its Stuck there as well.NOD32View still says, the actual version is 2264 ?!Was anyone able to Update without any deinstallation or Update of the Fix? Link to comment Share on other sites More sharing options...
GrandPa Posted May 16, 2007 Share Posted May 16, 2007 This site offers latest info:- http://www.volny.cz/esetnod32/ Link to comment Share on other sites More sharing options...
pmpalma Posted May 16, 2007 Share Posted May 16, 2007 There's something that dosen't drive here...I'm currently at 2269 yet, when running Update Viwer, it seems that update server are currently at 2264Screenshot Link to comment Share on other sites More sharing options...
Guest gustavo.veloso Posted May 16, 2007 Share Posted May 16, 2007 I cant update too.Last version 2264; Link to comment Share on other sites More sharing options...
Lee Posted May 16, 2007 Share Posted May 16, 2007 I'm on 2267. Link to comment Share on other sites More sharing options...
lynnig Posted May 16, 2007 Share Posted May 16, 2007 Yes it seems that no updates since 2264 ---> 14th May on mine also :nono: Link to comment Share on other sites More sharing options...
Guest gustavo.veloso Posted May 16, 2007 Share Posted May 16, 2007 Reinstalling NOD32 trial and apply Fix 2.2 again solve the problem.ESET won? NSane loose? :unsure:nsane update the fix if its a trouble in them.thank for the job! Link to comment Share on other sites More sharing options...
pmpalma Posted May 17, 2007 Share Posted May 17, 2007 Gents, I've uninstalled both NOD32 and nSane fix. Rebooted, reinstalled NOD32 (without the fix) thus keeping it with the 30 days trial. Rebooted, and saw the signature file go to 2271.My guess is as good as yours... either something happened, or they (the fine gentlemen at Eset) finally caught up with this wonderfull piece that nSane once created.Meanwhile, I'm sure that this is a temporary issue that somehow will eventually get fix. Link to comment Share on other sites More sharing options...
Guest AndreasCGN83 Posted May 17, 2007 Share Posted May 17, 2007 Hi!I can report the same like pmpalma- uninstalled and then reinstalled without fix the update is no problem.so i think the fix doesnt work any longerbut really- thanks for the work @nsane! was a great job to fix NOD32!perhaps you will make a new fix.. i hope :-)thanx Link to comment Share on other sites More sharing options...
xicoescuro Posted May 17, 2007 Share Posted May 17, 2007 Hello....I must tell you my experience in this matter:I´ve uninstalled nod 32 fix and nod 32 too.....After reboot, Í've reinstalled nod32 and fix 2.2, anda after restart, with manual update, it worked... This was in 15 May... the day before yesterday, the first reported!Then I couldn't update (it was 2246) an after the reinstall I've got 2249, but since then, got no updates at all any longer.Regs Link to comment Share on other sites More sharing options...
vbnmu Posted May 17, 2007 Share Posted May 17, 2007 Once upon a time I was advised to use Nod32.It was a new dawn.It was to be a new start.And then came Nsane,He made that new world even beta.N NOWWWWWWWWWWWWWW.......it aint working!!!! Goddamnit!!!If no fix is found i might go back to symantec AV! not norton no no no! bt Symantec!Pretty please Nsane, fix Nod32 once again! Save my day! Link to comment Share on other sites More sharing options...
Han Solo Posted May 17, 2007 Share Posted May 17, 2007 Hmm, I was noticing this as well. I tried doing a manual update earlier...and it said 'none were available' even though the signatures were at v2274 on their support page. I just tried another manual update from within NOD32 and it did finally update. Just FYI. But, how come the automatic updates don't seem to work anymore? At least on mine the auto-update hasn't worked since I did an upgrade a week or so ago. Goofy. Link to comment Share on other sites More sharing options...
Guest b52b52 Posted May 17, 2007 Share Posted May 17, 2007 That the Fix isn't working anymore is a matter of fact we have to accept.I would be interested i a statemant of insane. Are you working on a new fix?Is it worth waiting?Thx anyway for the previous fix! Link to comment Share on other sites More sharing options...
xicoescuro Posted May 17, 2007 Share Posted May 17, 2007 It's not a problem with fix...I'read in other pages that it's a problem of all trial versions.But, i'm glad to tell you that my nod 32 has already updated automatically to version of signatures 2274 (20070517)I hope that's for good... :-)Regs Link to comment Share on other sites More sharing options...
Guest b52b52 Posted May 17, 2007 Share Posted May 17, 2007 Wow, that would be really good news ---- aaaand:I can confirm!!!!! Just tried to update manually and it needed 3 trys but Server u21.eset.com updated my Version to v2275.And there we go on and on and on.... Link to comment Share on other sites More sharing options...
vbnmu Posted May 17, 2007 Share Posted May 17, 2007 It's not a problem with fix...I'read in other pages that it's a problem of all trial versions.But, i'm glad to tell you that my nod 32 has already updated automatically to version of signatures 2274 (20070517)I hope that's for good... :-)RegsDo u have automatic Server selection? or u updating from a selected server?Y do u say its to do with the trial versions?And which fix do u have? Am wondering if it has anything to do with a specific fix!cheers Link to comment Share on other sites More sharing options...
Guest b52b52 Posted May 17, 2007 Share Posted May 17, 2007 Fix 2.2 with automatic Selection works!Every server is on v2275 in the meantime. Link to comment Share on other sites More sharing options...
xicoescuro Posted May 17, 2007 Share Posted May 17, 2007 It's not a problem with fix...I'read in other pages that it's a problem of all trial versions.But, i'm glad to tell you that my nod 32 has already updated automatically to version of signatures 2274 (20070517)I hope that's for good... :-)RegsDo u have automatic Server selection? or u updating from a selected server?Y do u say its to do with the trial versions?And which fix do u have? Am wondering if it has anything to do with a specific fix!cheersHello again...Yes, I have automatic server selection. I said that the problem is (was) in trial versions because I've read in other users forums that the problem was reported in no fixed softwares.My fix is 2.2 nsane.Regs Link to comment Share on other sites More sharing options...
vbnmu Posted May 17, 2007 Share Posted May 17, 2007 It's not a problem with fix...I'read in other pages that it's a problem of all trial versions.But, i'm glad to tell you that my nod 32 has already updated automatically to version of signatures 2274 (20070517)I hope that's for good... :-)RegsDo u have automatic Server selection? or u updating from a selected server?Y do u say its to do with the trial versions?And which fix do u have? Am wondering if it has anything to do with a specific fix!cheersHello again...Yes, I have automatic server selection. I said that the problem is (was) in trial versions because I've read in other users forums that the problem was reported in no fixed softwares.My fix is 2.2 nsane.RegsEarlier in the day i reverted to a previous version along with fix 2.1.On first update it worked fine. updating till 2273! and then got stuk!whn 2274 came out i tried manual updates in vain! n now its has updated till 2275 on auto update!wondering whether to go to the new version with fix 2.2!it does not seem to b a problem with the trial software, more like with the updates with trial software! might be Eset prioritised fully paid for AV!Has anyone tried the new Nod32? whats with the password for auto update??? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.