NOD 32 5.0.93.0 & 5.0.94.0:PC freezes when USB HD is connected

Marcos -

"I'm sorry to hear that even though we have a fix ready and will be included in the next build along with some further improvements and fixes... "

If you've already got a fix, why not release it now and add the other bells and whistles on a subsequent build?

 

ESET I trusted you in the past, but damaging my External Hard Disk Drive is a very serious problem. I never thought that an Antivirus could do that.

 

Hi!

Here is the solving of USB drive probleme:

Mail from NOD32 / Hungary

The problem is known.
Please unzip to your hard disk that you create a folder on the file link Snipped: link from private correspondence removed. Restart the computer in Safe Mode (press F8 to select this repeatedly to reach directly to your computer turned on when the memory and hard drives will be checked). In the Safe Mode startup please copy and paste To decompress, you create the directory ekrnAmon.dll file C: \ Program Files \ ESET \ ESET Smart Security \ folder and restart the computer.
This problem is to improve the program next version will be fixed soon.

 

Those who are experiencing the issue and don't want to temporarily downgrade to v. 4.2 can contact their local support for a hotfix.

 

I even have the issue within Windows 7. I use a USB memstick every day. When I installed ESET v5 my Windows 7 stopped working normally after about 15 minutes. I have to hard reset my pc and I kept trying a lot but in the end I rolled back to v4.

Hope a fix is out soon!!!!

 

Same problem - Plugging in USB HDD freezes Dell PR380 running Windows XP Pro SP3, all updates. Have tried the normal stuff mentioned by others. No problems using these 4 usb drives on other PCs running Win XP home SP3, Win7 SP1, Ubuntu 10.04, or when plugged into a SimpleTech NAS.
However, I'm running NOD32 v4.2.67.1. I believe problem started after last upgrade from earlier 4.2 version in September.
Suggestions appreciated.
cfk41

 

I have followed this a long time and have a ticket in regarding the issue on a Dell system running XP Home SP3. It occurs to me that maybe this is a Dell issue when combined with XP SP3 (either Home or Pro). The fix they have in the works may help with version 5.x. I have no problems with 4.2.71.2 and USB external drives being connected and disconnected while the system is up.

 

I got the version 5.0.95.0 from the support in germany.

All is ok, if I deactivate the protection before I plug the USB-HD. If I leave the protection active, the PC freeze under XP SP3. This is an error.

I think, this was the same in V 4.

 

and, how is 5.0.95? any better?

care to share?

 

This problem seems to be a combination of WindowsXP Pro and ESET NOD32. Deactivating ESET for removable media did not fix my problem. Dell workstation still freezes up on plugging in a USB hard drive (NTSF & FAT 32).
Can read flash drives OK.
USB wireless adapter works OK
Now what implicates WinXP and ESET is that I can boot to a Linux CD and see all of the USB drives that are connected and nothing freezes up. If this were a Dell problem it should be a problem regardless of the OS.

The nail in ESET's coffin is that uninstalling NOD32 v4.2.67.1 made my usb drives work again! I'll be asking for a 3-PC, 2 year refund and switching to AVG free.

 

Well, I've never had a problem with USB and ver 4.x of Eset NOD32. I did not see this USB issue until I installed 5.0 and that is why I rolled back to 4.2.71.2. Is it an issue with the combination of Dell systems and Windows XP SP3? It might be hard to find any other brand using XP SP3 since so many older computers that are still in use are Dell branded. It's probably just XP SP3, but then we have a poster here saying the problem happened with Windows 7. That's really odd and I wonder what brand of computer was involved?

 

99% of the cases is Windows XP, not limited to dell. If you are experiencing this on W7, you are probably experiencing another issue though.

 

That's the most likely scenario, I have to admit. I suppose it could be related to BIOS versions, but there are so many different versions of any BIOS plus different BIOS providers, that it would be hard to find something common there, either. So, it pretty much boils down to XP SP3, notwithstanding that post from an individual running Win 7.

 

As to no trouble with 4.2x, As I said in first post I only had trouble after updating to 4.2.67.10 back in September. I had no idea ESET could be the problem until I found a couple of postings on other forums that indicated it could be. Then I found this forum with a Google search, and started some checking before I ran out and bought add on usb card or new mb (geek expert son's recommendation). Linux being able to see all my usbs convinced me it was either WinXP or NOD32. Removing NOD32 solved the problem.
What I wonder, is what 4.2 versions are running and NOT causing a problem? 4.2.67.10 is a very late 4.2x so its possible that whatever is causing the problem carried over into version 5.
BTW, even if ESET solves this quickly I will not be going back - AVG free and Malware Bytes found 2 rootkits and 3 virus infections (between 4 machines) that ESET missed (lucky for me they were tracking bugs and not eat your PC bugs). However, the Win32/Olmarik.AJL trojan it let by last May was and took a lot of work to get rid of.
cfk41

 

Only on two machines under XP SP3 run the new version 5.0.95.0, but with deactivate the nod32. On a third machines (XP SP3) it does not run(freeze).

 

Maybe I'm missing something here, but what's the point of running it, if it's inactive?

And when is there going to be an official update? This is getting ridiculous.

 

Versopm 4.2.71.2 does not exhibit this USB issue for me with Win XP SP3. Version 5.0 did cause the problem. I rolled back not wanting to deal with the issue any other way. If a different AV works better for you, so be it.

 

You can contact Customer Care for a fix. The official update has not been released.

 

Well, the version with 5.0.95.0 locked up solid this morning when I tried to attach an eSATA drive.

It worked yesterday (I tried it once).

Not today though.

I'm rolling back. This is ridiculous.

 

While I was given a link for the bug-fixed build, I'm a bit reluctant to actually install it. (I've already rolled back to v4.2.71.2.)

There ought to be some type of compensation for those who have either purchased v5 or those who have extended their subscriptions in order to use it.

 

New fix that has worked (so far).

Had this same problem after upgrading to 5 recently (nightmare figuring it out since I had also just installed Truecrypt and was experimenting with it on the ext drive and moving it between computers). I found a new fix on Eset's site
http://kb.eset.com/esetkb/index?page=content&id=SOLN2854

The fix basically requires uninstalling Nod32 and deleting remaining files (I didn't have any remaining files after uninstalling using the Nod32 uninstaller), then downloading the .msi file(do not use the live installer .exe file). Installing fom the msi but NOT activating during the install (don't enter username/password). Then activate manually after completing the install.

Working so far (about 20 minutes, and it did work before and after a reboot). I did have my USB hard drive plugged in during the install just in case, but I'm not sure you need to do that.

Obviously I've only had it working a short time so I'll have to give it some more time to know for sure, but it looks good so far. If I have a problem I'll post back.

I really dread doing NOD32 upgrades. I had problems with 4 years ago and moved back to 3 for a while, and I must say NOD32 is soooo much slower at scanning emails (downloading form pop3 accounts into Outlook) in versions 4 and 5. The reason I went to NOD32 in the first place years ago was because it was fast. I was tired of security tools slowing me down.

 

I tried the solution posted in the above post and it appears to work in my case. I followed the instructions in the link to the letter and installed version 5.0.95.0 with one of my two usb-drives disconnected. When I tried to make an Acronis-image to this drive a week ago, my computer froze solid. After installing this new version, I just succeeded in making the image. Let's hope it says this way.

 

Re: New fix that has worked (so far).

Update: Been running for 3 days now with no problems. The New Fix seems to be working.

 

Re: New fix that has worked (so far).

Followed the instructions on the fix, but still having the freeze.
Anyone else having the same issue with the 5.0.95 fix??

 

Re: New fix that has worked (so far).

Yup. Still freezes for me.