ESET v4 Fixes

[Mo Husen]

Sorry if it has already been posted.

If anyone is interested, here is the latest MiNodlogin 3.3.0.1 :

mediafire.com

&

/?mmmhtahmmhl

or

/?sharekey=8c9424c0dbc8e66ad2db6fb9a8902bda

Not Tested by me.

[mara-]

@Sonar

I don't want to be rude, but why do I have to repeat my self. Fixes has nothing to do with your problem, that is just a coincidence. Check the link I provided in my previous post. Simple registry permission change which this fix do can't cause the problem you are having.

Cheers ;)

[chrisTM]

Hello.

mara appears to be correct.

Follow the link he has provided, and the instructions contained in that post. You also might try deleting any old references to ESET before reinstalling. The old data may be corrupted or create permission problems that may affect your ability to update the definitions.

I had experienced the same Compiler Error prior to following the instructions in that link.

My current definitions are now 4004.

Thanks, mara, and good luck to all with the updates.

chrisTM out.

[francisco]

Goog evening,

I've installed NOD32 V4 and then used the box-fix 4.30. However, I probably haven't followed the instructions correctly and now the program doesn't work.

I wanted to uninstall it and try again, but when I try to remove it, the following message appears and the process is interrupted.

"Could not open key:

HKEY_LOCAL_MACHINE\Software\ESET\ESET

Security\CurrentVersion\Info. Verify that you have

suficcient access to that key, or contact your support

personnel."

What should I do? I would be grateful for any help.

Thanks in advance

[harpua]

I think if you go into Eset's advanced setup and uncheck "enable self defense" and reboot to make the change effective and then try to uninstall, you will have success.

[Hoca]

@mara-

Fixes has nothing to do with your problem. Check this here.

Thanks for the pointer to wilderssecurity :)

Although I'm sure un-installing/re-installing ESS will fix things, it seemed note worthy that this has clearly happened to a number of users?

Maybe it was something in connection with receiving the last update that screwed the install of ESS 3.x?

I guess 3.0.350 is an older build of ESS 3.x, and it was maybe a bug in the earlier builds that created this issue?

Cheers

[Hoca]

@francisco

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

-: NsaneDown :-

-: Instructions :-

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

Advanced user or novice user, follow these steps carefully or you'll end up with a fucked up installation.

1. !!! UNINSTALL ANY FIX USED BEFORE !!!

2. !!! UNINSTALL ANY EARLIER VERSION OF ESET (RECOMMENDED BY ESET) !!!

3. Reboot your PC.

4. Install ESET NOD32 Antivirus/Smart Security 4.0.417 x32/x64.

5. DISABLE Self-defense.

Note: To DISABLE the Self-defense, open ESET, press keyboard <F5>, select <Antivirus and antispyware>, UNCHECK the <Enable Self-defense>, <OK>, and <OK>.

6. Reboot your PC (otherwise Self-defense won't be DISABLED)

7. Install ESET4 Box4EVER 4.30A (Launch the EXE and press [LOCK]

8. ENABLE Self-defense.

Note: To ENABLE the Self-defense, open ESET, press keyboard <F5>, select <Antivirus and antispyware>, CHECK the <Enable Self-defense>, <OK>, and <OK>.

9. Reboot your PC (otherwise Self-defense won't be ENABLED).

10. It might take up to two days before you receive your FIRST(only the first) update, if you chose to convert the Retail to the Trial ESET will show RED in the beginning, after you received your first update this will be solved, your trial should remain 31 days FOREVER though.

11. Make sure that you [uNLOCK] ESET before uninstalling it.

Note: This fix will cause the Virus signature database not to show in the ESET tray message box. You can check it in the ESET User Interface though.

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

-: Thanks/Credits :-

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

Thanks to box for making the fix!

If you did not UNLOCK before trying to un-install NOD32? run ESET4 Box4EVER v4.30A again and click UNLOCK (if you're not certain what you did, UNLOCK it again just to be sure! :) ).

Moral of the story?... ALWAYS read the instructions! :P

Cheers

[user123]

how do you uninstall boxmara fix or any other fix. do they create any window startup entries or start any services.

[Hoca]

@user123

"how do you uninstall boxmara fix or any other fix"

YOU READ THE INSTRUCTIONS!!!!!!!!!!!!!!!!!!

:) How many times does it have to be said?!

I can sometimes excuse folk from not wanting to individually read through over a thousand posts in this thread, but given the last post before the one you made was pointing out to read the instructions, don't you think that could be a pretty good place to start? :P

The box, mara fix v1.1 actually has all you need to know built in to the ReadMe First/Information link in the fix itself!

Other than that read the first page in this thread: http://www.nsaneforums.com/index.php?showtopic=16786

How easy do you want this to be? :s

[KotaXor]

Sorry if it has already been posted.

If anyone is interested, here is the latest MiNodlogin 3.3.0.1 :

mediafire.com

&

/?mmmhtahmmhl

or

/?sharekey=8c9424c0dbc8e66ad2db6fb9a8902bda

Not Tested by me.

Tested since.... :) and found to be working beautifully!

It work just as good as Nodlogin or even better!

It is stable too!

MiNodlogin should be on the fp! Don't know why it is not there though!

[francisco]

Good morning,

First of all, I thank you for your patience and fast response.

However, the problem still resides. The program won't uninstall and the same announce appears:

"Could not open key:

HKEY_LOCAL_MACHINE\Software\ESET\ESET

Security\CurrentVersion\Info. Verify that you have

suficcient access to that key, or contact your support

personnel."

The anti-virus' self-defense is undoubtelly unchecked and the fix is unlocked.

I should warn you, that when I installed the program I checked 'set update parameters later'. Should I have written 'eset' in the username and password? During the process of installation, he warned several times with something about keys, but I ignored it. Then, I used the fix and followed the instructions, but after I unchecked 'self-defense' and rebooted, the fix wouldn't lock. That is the problem, I still can't lock it. He says that I have to uncheck 'self-defense'. And I cannot uninstall the program either, even tough, 'self-defense' is unchecked and the fix is unlocked. For what is worth, later, I did set the update parameters. I used 'eset' as the username and password.

Thank you

[shought]

@fransisco

What OS are you running? If on Vista try running the fix by using right click 'run as admin'.

Don't worry about the update parameters, they're not the problem.

Tested since.... :frusty: and found to be working beautifully!

It work just as good as Nodlogin or even better!

It is stable too!

MiNodlogin should be on the fp! Don't know why it is not there though!

Why, is it really that much better than NodLogin or NodEnabler? I mean we already have two of that kind on the frontpage, lol.

[francisco]

I don't know if it helps, but on certain ocasions it also warns me that it cannot read my firewall configuration.

Another thing, previously I had Eset Smart Security V3, however, I forgot to unistall its fix. I only did it after I installed V4. Anyway, I did not unistall that fix, because I thought it wasn't working anymore. Sometimes it stopped working and I had to install it again, that's why I thought it was uninstalled already.

shought,

I am using vista and I did what you said and tried to lock the fix, with 'self-defense' unchecked, but it did not work.

[shought]

This is a total guess, but it might just work... If you manually delete most of ESET's registry entries and then try to uninstall it might just work, I don't know if you have any experience with the registry, if not then I would be willing to do it for you, using TeamViewer(have a look at their website to see what it is).

[harpua]

If you are still trying to uninstall the program, you might try to disable antivirus and antispyware protection by right clicking on the Eset system tray icon and selecting the appropriate menu item and then try uninstalling by running Eset's uninstaller found under Eset in the All Programs menu. If that doesn't work, boot into safe mode and try to run the uninstaller again.

I thought the instructions for the fix made a big deal about uninstalling any previous fixes before trying to install the new fix. Sounds like that step was forgotten. Very important to read and follow instructions.

[KotaXor]

Tested since.... :x and found to be working beautifully!

It work just as good as Nodlogin or even better!

It is stable too!

MiNodlogin should be on the fp! Don't know why it is not there though!

Why, is it really that much better than NodLogin or NodEnabler? I mean we already have two of that kind on the frontpage, lol.

It is....it is, just don't tell anyone....I removed Nodlogin and installed MiNodlogin instead. :P

I kept Nodlogin and NodEnabler just in case.....but so far..... :frusty:

Wondering also when Nodlogin is coming out of beta!

Many ppls are facing problem with NodEnabler v3.0 too!

[KotaXor]

Look like I spoke too soon! :frusty:

NodEnabler v3.1 should be coming in the next few days! :P

[francisco]

shought,

Can't you explain how to delete the registry entries manually?

By the way, harpua, I disabled the program temporarily and tried to unistall it, but it didn't work. Then I disabled it again, because it was already enabled, and booted the computer in safe mode, just like you said, but it still didn't work.

Thank you anyway

[harpua]

You're welcome. Sorry none of those ideas worked.

[Bizarre™]

@francisco:

Can you try installing on top of your current installation of NOD32?

[chrisTM]

Hello.

I was digging around in my computer services and came across the mara-box1.1 fix listed as automatic, but not running. I tried to remember how it was listed before, but don't remember. I tried to start it, but received the message shown in my attachment. Clicking on Properties showed a file path that I added to exclusion list. Is this because the fix technically only runs at boot time, or is this an error to worry about?

Thanks in advance.

chrisTM out.

A/V def. 4004

Hello.

mara appears to be correct.

Follow the link he has provided, and the instructions contained in that post. You also might try deleting any old references to ESET before reinstalling. The old data may be corrupted or create permission problems that may affect your ability to update the definitions.

I had experienced the same Compiler Error prior to following the instructions in that link.

My current definitions are now 4004.

Thanks, mara, and good luck to all with the updates.

chrisTM out.

[chrisTM]

Sorry, here it is.

Hello.

I was digging around in my computer services and came across the mara-box1.1 fix listed as automatic, but not running. I tried to remember how it was listed before, but don't remember. I tried to start it, but received the message shown in my attachment. Clicking on Properties showed a file path that I added to exclusion list. Is this because the fix technically only runs at boot time, or is this an error to worry about?

Thanks in advance.

chrisTM out.

A/V def. 4004

Hello.

mara appears to be correct.

Follow the link he has provided, and the instructions contained in that post. You also might try deleting any old references to ESET before reinstalling. The old data may be corrupted or create permission problems that may affect your ability to update the definitions.

I had experienced the same Compiler Error prior to following the instructions in that link.

My current definitions are now 4004.

Thanks, mara, and good luck to all with the updates.

chrisTM out.

[shought]

This is a leftover of the mara-fix, the box, mara-fix no longer uses this service. Maybe mara- can create something to remove this service.

[chrisTM]

Thanks.

In the meantime, I'll disable.

chrisTM out.

This is a leftover of the mara-fix, the box, mara-fix no longer uses this service. Maybe mara- can create something to remove this service.

[Hoca]

@shought

Your comment about UAC in Vista is an essential one that should be made very obvious to all Vista or Window7 users!

Bloody UAC!! AKA anti-medicine mechanism! :P Wouldn't it be worth having something on the first page to this effect?

The mara fix has an un-install built in. If you have it installed and run again it offers to remove the fix ;)

@ALL

If you're using Vista/W7 ALWAYS right-click and choose Run as Administrator when installing/un-installing fixes!!

@chrisTM

Did you try to remove the mara fix before applying a new fix?

Disable SD, run the box, mara fix v1.1 and UnFix, then run mara-fix x1.5 (x32 & x64) and see if it identifies it is still installed? If it does not not see it is already installed, you could always install it anyway, then immediately run it again to remove it from the system? Then finally run the box, mara fix v1.1 again and Fix It, then enable SD, hopefully that will smooth everything back as it should be :P

I think I'd be correct in saying if you've not removed the mara-fix x1.5 (x32 & x64), the ESET service will still be being delayed at boot up, so you won't be getting the full benefit of having changed to the box, mara fix, as SD will still be slightly comprimised ;)

Cheers