Long scan time

Hi,

I have NOD32 on my Sony desktop, my Macbook Pro and an HP laptop. The scan times are normal on the first two computers but on the HP is takes forever. I started a scan last night and got to 94% before I went to bed. When I got up it was at 99%. I took a screen shot of the log and saw that for entry after entry it was saying decompression could not complete... see the screen shot for the rest of what it is telling me.

I rebooted and did another smart scan and it’s doing the same thing. It gets to 94%in a decent time but then stays there for a very long time. I tried a custom scan of the whole computer, which should be what the smart scan is doing right? Anyway the custom scan does manage to scan and I do not get the decompression error message (I am doing the custom scan as an admin scan) and I am logged in as Admin for the smart scan.

Has anyone seen this issue before? Should I just re-install NOD? I do not recall in the past it taking so long to complete a smart scan.

Thanks
Logan

 

Apparently EAV is unable to decompress archives due to a permission problem with temporary folders. Try deleting and re-creating the temporary folders or set write permissions for the current user manually.

 

Marcos,

Thanks for the reply. It never used to do this and I have made no changes that I know of. Not sure how to delete the temp folders or even which ones. You are only seeing a small part of log, it seems to be doing this for almost everything it is scanning and not all of them are folders (unless I am missing something). Nor am I sure how to set write permissions or for what folders.

Again I logged onto the laptop as Admin.

Logan

 

ESET has a KB article that might help.

 

rockshox,

Hey thanks I will give that a try when I get home.

Logan

 

rockshox,

I also sent an email to Eset and got a reply back with 2 links and the first one seems to have fixed my problem (its this one here)

http://kb.eset.com/esetkb/index?page=content&id=SOLN2147

I did look at your link it even though it more directly relates to what I was seeing I did not try it as the problem is fixed.

Again thanks for the help!

Logan