Eset Nod 32 Fix for 3.0? (CONTINUED)

[toti]

nod32 trial updates perfectly, but if you fix not update multiple :D

:dance2: well nodlogin

Best regards

[KotaXor]

denis v6 auto updated 3335

-----------------------------------------

I got 3 minutes ago, 3336 with NodLogin.

-----------------------------------------

Going to try to schedule using "kostaxor" explanation.

Sorry but I started this NodLogin yesterday and thought it wasn`t possible to schedule...but only believe when I have it done.

-------------------------------

Time to ;) now... :D

Why shifted to nodlogin. Sometime back ur were shouting at the top of ur voice tht its a eset server problem and not a fix problem eh? :dance2:

Please do not blame anyone, Jofre did a very good job in testing all the fixes by nsane members.

Just because most of evaluation servers is down, it's not his fault that Nod does not update.

When the servers is back up again....who know when....the trial fix will continue to work.

As it is, some members are still able to update using the trial fix.

Who knows, Nodlogin might failed again as it has many times before. Pray hard. :sadwalk:

[toti]

Please do not blame anyone, Jofre did a very good job in testing all the fixes by nsane members.

thanks :notworthy:

[PHiXiON666]

You can schedule nodlogin to run by itself, just follow the u/m instruction:

Install Nod32 v3.xx

1) Remove user name and password in NOD32 v 3.x during installation

2) Put "nodlogin setup.exe" in Eset folder and run it. (install hidden mode). You can delete the setup file after running it if you want.

3) Go in Eset UI 'Tools' and then Scheduler and then "Add"

4) Click 'Run external application'

5) Taskname "Nodlogin" and Run the task Event triggered.

6) Event to trigger task:"Successful update of the virus signature

database"

7) Run task as soon as possible

8) In "Run application" window, browse to nodlogin.exe

(Executable file

C:\Program Files\ESET\ESET NOD32 Antivirus\nodlogin.exe

In 'Work folder'

C:\Program Files\ESET\ESET NOD32 Antivirus )

OK

9) Go in Eset UI 'Tools' again and then Scheduler and then "Add"

10) Run external application

11) Taskname "Nodlogin" and Run the task Event triggered.

12) Event to trigger task:"Successful update of program components"

13) Run task as soon as possible

14) In "Run application" window, browse to nodlogin.exe

(Executable file

C:\Program Files\ESET\ESET NOD32 Antivirus\nodlogin.exe

Again in Work folder

C:\Program Files\ESET\ESET NOD32 Antivirus )

OK

that's it, your Nod32 should auto update every hour or during bootup.

It has been working for me since awhile without me needing to manual update.

Thanks kotaxor for this tutorial it works great! :notworthy:

[bismarck]

jofre thanks for the links. kotaxor thanks for the tutorial. box, marsu, ulisses, etc thanks as well. :notworthy:

btw jofre any news on generator 6.2? thanks!

[jofre]

8)

Just installed Nodlogin 9.6 ( clean inst.) and applied information ( Page 76 / Post 1515) given by member =Kostaxor=in order to get automatic updates.

Seems to work, but not sure yet. For the moment it shows 3338 =virus signature database.

Soon will give you news saying if it auto-updates or not .(ESS 3.0.669)

-------------------------------------------

cheers to everyone here ! :notworthy:

Jofre

[UnixSofter]

:lmao:

Just installed Nodlogin 9.6 ( clean inst.) and applied information ( Page 76 / Post 1515) given by member =Kostaxor=in order to get automatic updates.

Seems to work, but not sure yet. For the moment it shows 3338 =virus signature database.

Soon will give you news saying if it auto-updates or not .

-------------------------------------------

cheers to everyone here ! 8)

Jofre

I installed Nodlogin 9.6 and followed kotaxor's instructions, and it's working great! EAV is now updating automatic. :notworthy:

[KotaXor]

The instruction actually came from the founder of this forum. Nsane actually came up with a fix for Nod32 v3 many moons back for testing which incorporate nodlogin and scheduler.

But nodlogin was very unstable then and it did not fully worked.

[UnixSofter]

The instruction actually came from the founder of this forum. Nsane actually came up with a fix for Nod32 v3 many moons back for testing which incorporate nodlogin and scheduler.

But nodlogin was very unstable then and it did not fully worked.

Oh yeah, what happend to the nsane v3 fix? Did the development of the fix stop, when all the other fixes appeared? ;)

[shought]

The instruction actually came from the founder of this forum. Nsane actually came up with a fix for Nod32 v3 many moons back for testing which incorporate nodlogin and scheduler.

But nodlogin was very unstable then and it did not fully worked.

Oh yeah, what happend to the nsane v3 fix? Did the development of the fix stop, when all the other fixes appeared? ;)

nsane probably saw other fixes popping up, replacing his fix and thought it'd be better to quit developing it. And of course time has always been an issue :sneaky:

[KotaXor]

Nsane has his own personal problem, initial nodlogin did not work as expected.

It started with Nodlogin8.0, then 8.0a and 8.0b .....and so on \.....now 9.6.

The question was first asked, what happen if all trial servers were to be removed? All trial fixs will failed including nsane fix.

The theory and idea then was to use so called "genuine" user/password, as such nodlogin.

The first nsane fix with nodlogin came about late last year. I manged to get a copy for analyse and testing.

It was a .exe which automate the whole process.

I merely extracted the idea and theory behind it and list it into a step by step guide.

Anyone can make a batch or .exe file from the idea and automate the whole procedure. But this guide will show you what is actually happening.

Because the trial fix and patches was working so well and popular most of time. Not forgetting that nsanefix for Nod32 v2.xx was a trial fix too.

Nodlogin was 'cast' aside. Until Now!

Nsane sure has the foresight, knowing that trial servers might not last forever.

[Fuely]

Does "nodlogin.exe" need to be added to Exclusions ?

[talakitok]

Nsane sure has the foresight, knowing that trial servers might not last forever.

uhm?...so any alternatives?... if this would happen??.... ;)

[KotaXor]

Nsane sure has the foresight, knowing that trial servers might not last forever.

uhm?...so any alternatives?... if this would happen??.... ;)

Lets be realistic, nothing last forever. Be grateful with what you have now.

As long as there are 'crackers', there will be a solution. Matter of using 'reverse engineering'.

If the trial servers are back up, all trial fixes by members should continue to work.

[harpua]

Does "nodlogin.exe" need to be added to Exclusions ?

Yes.

[talakitok]

Nsane sure has the foresight, knowing that trial servers might not last forever.

uhm?...so any alternatives?... if this would happen??.... ;)

Lets be realistic, nothing last forever. Be grateful with what you have now.

As long as there are 'crackers', there will be a solution. Matter of using 'reverse engineering'.

If the trial servers are back up, all trial fixes by members should continue to work.

ok...uhm?..sir kotaxor the other day that u told me bout the update thing its not workin now..i am stocked up with v3331

[Noddy]

Does "nodlogin.exe" need to be added to Exclusions ?

I always add the 'ESET' installation directory to 'Exclusions.' This helps as we usually keep changing from one fix to another for V3. Therefore, all fixes within the 'ESET' folder are exempted by default.

[Luckie]

is NODlogin a virus? After installing it I have some stupid dlls in temp and system32 folder. The only chance to get them away is to boot a BartPE Disk and remove the files, boot in normal way and remove the registry entries. :sneaky: ;)

[harpua]

is NODlogin a virus? After installing it I have some stupid dlls in temp and system32 folder. The only chance to get them away is to boot a BartPE Disk and remove the files, boot in normal way and remove the registry entries. :sneaky: ;)

No, it is not a "virus" and most programs need to install some files to work. How do you know the dlls etc. are "stupid?"

Nodlogin.exe (or the setup program for it or both) is/are, however, detected as a "threat" by ESET as are many other AV fixes, which they usually name, rather appropriately I think, some varient of "WinHackAV." It is natural and expected that ESET would want to defend their program and discourage use of a fix in this manner. Fortunately, the work around is to simply add the file (and whatever other files you don't want NOD32 to ever scan) to the list of exclusions in NOD32.

[Luckie]

before installing NODlogin I had a clean system. After installing NODlogin I found some DLLs (combination of numbers and letters) inside the temp and system32 folder which are started by rundll32.exe and they will be restarted everytime you kill rundll32.exe. And those DLLs are also force to be loaded from some Windows services. This is a virus behavior for me.

[harpua]

before installing NODlogin I had a clean system. After installing NODlogin I found some DLLs (combination of numbers and letters) inside the temp and system32 folder which are started by rundll32.exe and they will be restarted everytime you kill rundll32.exe. And those DLLs are also force to be loaded from some Windows services. This is a virus behavior for me.

Unless something malicious is being done to your system, I wouldn't necessarily classify such behavior as a "virus" or even "malware."

What happens if you uninstall nodlogin? Do those offending dlls go away after uninstall and reboot?

[KotaXor]

Nsane sure has the foresight, knowing that trial servers might not last forever.

uhm?...so any alternatives?... if this would happen??.... ;)

Lets be realistic, nothing last forever. Be grateful with what you have now.

As long as there are 'crackers', there will be a solution. Matter of using 'reverse engineering'.

If the trial servers are back up, all trial fixes by members should continue to work.

ok...uhm?..sir kotaxor the other day that u told me bout the update thing its not workin now..i am stocked up with v3331

Use nodlogin instead of the trial servers if you want immediate update. The eval server is erratic most of the time. Either wait for the trial server to be fully up or use nodlogin, the choice is yours.

[Muhannad]

don't know here

apply the written steps, got nothing & stuck wiz 3329, so um and old f ;) ked signature i've

any further help please

tanks in advance

[harpua]

don't know here

apply the written steps, got nothing & stuck wiz 3329, so um and old f ;) ked signature i've

any further help please

tanks in advance

Hard to know what you are talking about since you provide no details at all regarding what fix you are trying to use but assuming you are talking about Nodlogin 9.6, I would suggest that you uninstall any other fixes you may have installed, uninstall ESET AV or SS, delete any remaining ESET directories and then do a clean re-install of ESET and then install Nodlogin again, add the nodlogin executable to Eset's exclusions, and after it's installed manually run nodlogin.exe and then try to update the ESET program. If it works, then add the Eset scheduler entries to run nodlogin.exe automatically after update as suggested in another post a couple of pages back.

[Aeracier]

last night i tried to update hundreds time the pc where i have a nod32 cracked with marsu 2.5

it has always failed, saying everything is up to date

Then i ve launched Nod viewer to check and test the servers

i ve noticed that many of them were not working properly. They are online but they don't give back the info.

after doing 3-4 checking of all trial update servers on the list, the trial server 34 and 38 were responding and giving me back the info of the last update (3338 last night). When i say that they were responding, it was only for few minutes

i ve then downloaded the update from Nodviewer to my pc. While it was downloading 14 MB files, i ve set my Nod32 update option to server 34, and try to update at the same time as nodviewer--->My cracked version has instantly been updated to 3338.

I have downloaded and discovered Nod viewer for the first time last night.

I don't know really how it works, and i didn't had time to learn more this tool.

But you can download from it all the updated files on a ESET_Upd folder that Nodviewer create. and i imagine that we can manually update nod32 from this source on your pc. I saw also some option wich seems to update automatically your nod32 after that nodviewer has dowloaded it.

But!!!, even with nodviewer, servers seems to not work properly

I m sure some people know this tool better than me, i am at work actually and i can't test it more. Maybe i ve just been lucky..maybe this solution works....but it is a kind of nodlogin alternative for those who don't use nodlogin, but a cracked version (while waiting that servers come back to normal)

I don't have those problems on my others pc who run legits version (but we already know this)