Jump to content

ESET v4 Fixes


shought

Recommended Posts

  • Administrator

OK. I got the update properly. Updated to 4222. It was 1731 KB.

Link to comment
Share on other sites


  • Replies 2k
  • Views 215k
  • Created
  • Last Reply

I just received it as well(automatic update), I guess the impact of such a small big update(yeah, it's one of the smaller 'big updates' that have been released ;)) wasn't that big.

Link to comment
Share on other sites


  • Administrator

Sure it wasn't. :hehe:

Link to comment
Share on other sites


Hi all,

I have NOD32 2.7 why 2.7? because it is a very good version and very light.

I have the Nod32 fix: NOD32 Fix 2.3.2 by B-effect.

Now is my question my nod32 dont want to update my version is 4219 he says every time when i do a update: Nod32 is up-to-date.

I try this many many times 30 or 40 times.

Ps: Sorry for my bad english

Link to comment
Share on other sites


  1. Uninstall nod32 fix
  2. Uninstall nod32 2.7
  3. Download and run eset removal tool
    http://www.nod32.nl/download/tool/nod32removal.exe
  4. Download/install ccleaner and do a registry clean-up:
    http://www.ccleaner.com/download/builds/downloading-slim
  5. Download Eset AntiVirus v3* or v4*
    EsetAV v3* (32bit) here: http://download.eset.com/download/win/v3eav/eav_nt32_enu.msi
    EsetAV v3* (64bit) here: http://download.eset.com/download/win/eav/eav_nt64_enu.msi
    EsetAV v4* (32bit) here: http://download.eset.com/download/win/eav/eav_nt32_enu.msi
    EsetAV v4* (64bit) here: http://download.eset.com/download/win/v3ess/ess_nt64_enu.msi
    Use this website for username/password:
    *SNIP*
    or
    *SNIP*
  6. Install nod32 antivirus version 3* or 4*. In the setup: check 'set update paramaters later'
  7. Download nodlogin here: http://www.nsanedown.com/?request=140184
    Disable ESET before downloading/installing. Nodlogin is tool that inserts new username/passwords when they expire..
  8. If you installed nodlogin, you first have to exlude this folder "C:/programfiles/ulisessoft" in the nod32 options.
  9. After you excluded the folder > enable nod32 > go to update tab and press 'update virus signature database' (or something like that) :lol:

Link to comment
Share on other sites


  1. Uninstall nod32 fix
  2. Uninstall nod32 2.7
  3. Download and run eset removal tool
    http://www.nod32.nl/download/tool/nod32removal.exe
  4. Download/install ccleaner and do a registry clean-up:
    http://www.ccleaner.com/download/builds/downloading-slim
  5. Download Eset AntiVirus v3* or v4*
    EsetAV v3* (32bit) here: http://download.eset.com/download/win/v3eav/eav_nt32_enu.msi
    EsetAV v3* (64bit) here: http://download.eset.com/download/win/eav/eav_nt64_enu.msi
    EsetAV v4* (32bit) here: http://download.eset.com/download/win/eav/eav_nt32_enu.msi
    EsetAV v4* (64bit) here: http://download.eset.com/download/win/v3ess/ess_nt64_enu.msi
    Use this website for username/password:
    *SNIP*
    or
    *SNIP*
  6. Install nod32 antivirus version 3* or 4*. In the setup: check 'set update paramaters later'
  7. Download nodlogin here: http://www.nsanedown.com/?request=140184
    Disable ESET before downloading/installing. Nodlogin is tool that inserts new username/passwords when they expire..
  8. If you installed nodlogin, you first have to exlude this folder "C:/programfiles/ulisessoft" in the nod32 options.
  9. After you excluded the folder > enable nod32 > go to update tab and press 'update virus signature database' (or something like that) :lol:

here is the Uninstaller for v3 and v4

run it in Safe Mode

http://download.eset.com/special/ESETUninstaller.exe

Link to comment
Share on other sites


Bizarre™

@luuk112:

You don't have to schedule NodLogin. You just have to add it in the exclusion list (just in case)

You can just run it once, and forget about it until the expiration draws near :)

Link to comment
Share on other sites


@luuk112:

You don't have to schedule NodLogin. You just have to add it in the exclusion list (just in case)

You can just run it once, and forget about it until the expiration draws near :lol:

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

Using Nodlogin 9.9c sense the beginning of this version and ESS 4.0.437 and never had to add it in exclusion list - but that is me...

WinXP Pro SP3 (32 bits).

Cheers

Jofre

Link to comment
Share on other sites


Just a small reminder, Nodlogin can be use on Nod32 v2.7 without any problem.

Link to comment
Share on other sites


NodEnabler 3.2 is Finally out! Thanks to the The Damned Crew - Saying Daaaamn since 1973

Download:

Site: http://www.ziddu.com

Sharecode: /download/5552326/NodEnabler3.2.zip.html

Test it and share your comment!

Link to comment
Share on other sites


Tried Nodenabler 3.2 and I get this whenever I try to click apply in settings manager or run the program :

Line -1:

Error: Variable must be of type "Object".

Got Xp pro sp2 and ess 4.0.437

Link to comment
Share on other sites


NEW !!!

NODENABLER 3.2... :) ... :P ... :console: BY Matt1553, NodSter & Damian666

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

Changelog :

+Numerous tweaks under-the-hood to make the program more robust, reusable, and faster.

+Some minor bug fixes.

+Did lots of small things to improve usability and configurability.

+Numerous new options added to the settings manager.

+Removed everything from the installer that could better be placed in the settings manager.

+Removed some installer options that weren't really needed.

+New output options for automatic execution - Hidden/Silent, Standard (New: Tray icon only shows messages when license changes or something goes wrong), and Verbose.

+The Vista scheduled task can now have its repetition interval modified by the settings manager.

+NodEnabler now finally works properly with proxy servers (thanks to a new AutoIt release).

+The licenses used by NodEnabler are now much more random and diverse, hopefully meaning they will get black-listed less often.

+You can now completely change where and how NodEnabler searches for a license (more info at http://www.autoitscript.com/autoit3/docs/f...ringRegExp.htm).

+NodEnabler now checks when the current license is due to expire (ESET v3 and up only) and updates it before your ESET software starts complaining (Still doesn't anticipate black-listing by ESET though - not possible).

+Lots of small things that have already been forgotten about.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Download »»»»»»»»»»»»»»»»»»»»»»»»»»»»»» Mediafire.com

..................................Sharecode »»»»»»»»»»»»»»»»»»»»»»»» /file/m2bhin423tg/NodEnabler 3.2.zip

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cheers

Jofre

READ ME TEXT INCLUDED.

Link to comment
Share on other sites


Box-mara fix has been working flawlessly for weeks until today - just got a "general compiler error" as it was trying to update. Anyone encounter this before? Thanks much.

Link to comment
Share on other sites


  • Administrator

Yes. I am facing the same problem. Makers please reply.

Link to comment
Share on other sites


This is not problem with the fix . Eset definitions caused this. I also have this error. I did not try, but complete uninstall, and then fresh install should solve the problem. You can Google about this problem. Some says that they did not touch anything and Eset updated automatically itself.

Cheers ;)

Link to comment
Share on other sites


This is not problem with the fix . Eset definitions caused this. I also have this error. I did not try, but complete uninstall, and then fresh install should solve the problem. You can Google about this problem. Some says that they did not touch anything and Eset updated automatically itself.

Cheers ;)

I Googled the issue but couldn't really figure out the cause as I followed the diagnostics on the Wilder's Security forum for the problem but everything on my system seemed to line up. The problem was still there so I :

1-Disabled self defense and rebooted

2-Unfixed and uninstalled ESET. Deleted the registry entries and the ESET folders under Documents and Settings for all users and my user name and rebooted.

3-Installed ESET again, disabled self defense and rebooted

4-Ran the fix and rebooted

5-Changed the red icon to green by updating to the initial database of 05-14-09 (4075)

6-It should update to the curremt database as I recall in a day or so - we'll see.

I may have to do the same for my desktop and netbook. Although I haven't seen the problem yet, I also don't think they have updated properly.

Link to comment
Share on other sites


im not facing that problem but these one:

nonfunctional.th.jpg

even if i click under "Configure" and mark "Enable real time file system protection" then "Ok" i still have that red icon. Because the mark wont stay...

Please any idea? Never had these problem anyway.

Thanks a lot in advance

Link to comment
Share on other sites


Tried Nodenabler 3.2 and I get this whenever I try to click apply in settings manager or run the program :

Line -1:

Error: Variable must be of type "Object".

Got Xp pro sp2 and ess 4.0.437

I got the same error with Winxp SP3 and ESET NOD32 Antivirus v3.0.684.

(Nodenabler v3.0 and v3.1 have no problem).

Link to comment
Share on other sites


This is not problem with the fix . Eset definitions caused this. I also have this error. I did not try, but complete uninstall, and then fresh install should solve the problem. You can Google about this problem. Some says that they did not touch anything and Eset updated automatically itself.

Cheers :)

I Googled the issue but couldn't really figure out the cause as I followed the diagnostics on the Wilder's Security forum for the problem but everything on my system seemed to line up. The problem was still there so I :

1-Disabled self defense and rebooted

2-Unfixed and uninstalled ESET. Deleted the registry entries and the ESET folders under Documents and Settings for all users and my user name and rebooted.

3-Installed ESET again, disabled self defense and rebooted

4-Ran the fix and rebooted

5-Changed the red icon to green by updating to the initial database of 05-14-09 (4075)

6-It should update to the curremt database as I recall in a day or so - we'll see.

I may have to do the same for my desktop and netbook. Although I haven't seen the problem yet, I also don't think they have updated properly.

You need to do first update manually. Just keep pressing to update until you get it.

Cheers ;)

Link to comment
Share on other sites


Tried Nodenabler 3.2 and I get this whenever I try to click apply in settings manager or run the program :

Line -1:

Error: Variable must be of type "Object".

Got Xp pro sp2 and ess 4.0.437

I got the same error with Winxp SP3 and ESET NOD32 Antivirus v3.0.684.

(Nodenabler v3.0 and v3.1 have no problem).

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

Have you done a clean installation ? - Because I am using NodEnabler 3.2 and it`s OK. Tested all settings and none

issue found »»» WinXP SP3(32bits) and ESS 4.0.437.

Did you Reboot PC after NodEnabler has been installed ? - 32 or 64 bits OS ? Language ?

Cheers

jofre

Link to comment
Share on other sites


Just spotted the new box, mara- fix v1.2 (x32 & x64)

Thank you kindly for your continuing work box and mara-, much appreciated! ;)

So far, all implantations of fix 1.1 are working flawlessly, so I won't go fiddling with anything until I actually have to :) (as per mara-'s post #301)

Keep up the good work!

Cheers!

Link to comment
Share on other sites


Tried Nodenabler 3.2 and I get this whenever I try to click apply in settings manager or run the program :

Line -1:

Error: Variable must be of type "Object".

Got Xp pro sp2 and ess 4.0.437

I got the same error with Winxp SP3 and ESET NOD32 Antivirus v3.0.684.

(Nodenabler v3.0 and v3.1 have no problem).

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

Have you done a clean installation ? - Because I am using NodEnabler 3.2 and it`s OK. Tested all settings and none

issue found »»» WinXP SP3(32bits) and ESS 4.0.437.

Did you Reboot PC after NodEnabler has been installed ? - 32 or 64 bits OS ?

Cheers

jofre

It's a clean install of NOD32 Antivirus v3.0.684 and Nodenabler 3.2 on Winxp sp3 x86 OS (vmware).

and yes, did reboot pc after install nodenabler.

btw, it's a clean winxp sp3 on vmware without any other applications installed.

UPDATE:

I just try it again and still got the same error. Then I put in Microsoft .NET Framework v2.0, and it's working.

So, Nodenabler v3.2 needs Microsoft .NET Framework to run while older version (3.1 and 3.2 do not).

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...