Nod32 v4.0.467 and Windows 7 error when saving pictures from IE8...

Discussion in 'ESET NOD32 Antivirus' started by GAN, Sep 25, 2009.

Thread Status:
Not open for further replies.
  1. MongooseOx

    MongooseOx Registered Member

    Joined:
    Oct 28, 2009
    Posts:
    1
    I am also getting this error in Windows 7 x64.. It seems quite random, can go a day without it happening at all, or it can happen every single time you try and save a file from IE, Word etc. Had to downgrade to 4.0.437. Hopefully it will be fixed soon.....
     
  2. vbuckjr

    vbuckjr Registered Member

    Joined:
    Jan 4, 2006
    Posts:
    10
    Location:
    Nashville, TN
    I am using RTM Windows 7 Professional 32 bit using Nod32 v4.0.467 I have the problem when downloading any file from the internet.

    "You don't have permission to modify files in this network location.
    Contact the administrator per permission to make these changes."

    When i get this error the file will be created, but is 0 bytes in size. If i click Ok on the dialogbox with the error and try again i will be prompted if i want to overwrite the 0 byte file and then it's downloading fine when i click yes.

    Until I stumbled over here I didn't know what it was.
     
  3. the1

    the1 Registered Member

    Joined:
    Oct 28, 2009
    Posts:
    15
  4. GAN

    GAN Registered Member

    Joined:
    Mar 3, 2007
    Posts:
    355
    Maybe it's time for some feedback from Eset.....
     
  5. the1

    the1 Registered Member

    Joined:
    Oct 28, 2009
    Posts:
    15
    That would be greatly appreciated by all.
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,456
    Unfortunately we could not replicate the issue yet and the logs provided didn't shed more light either. The issue is still being investigated.
     
  7. damike

    damike Registered Member

    Joined:
    Oct 29, 2009
    Posts:
    2
    I got Smart Security 4.0.467 64bit. Also have the same problems (IE, Photoshop, ...)

    But the strangest thing happens with Micrsoft Visio 2007 SP2: *Everytime* i try to safe a new sketch i get an error - sometimes he claims that the drive is corrupt. If i disable Eset - no problems at all
     
  8. tanstaafl

    tanstaafl Registered Member

    Joined:
    Apr 8, 2005
    Posts:
    207
    Why are you guys reporting Smart Security issues in the NOD32 AV forum??
     
  9. the1

    the1 Registered Member

    Joined:
    Oct 28, 2009
    Posts:
    15
    The issue was first reported by someone using NOD32. But others using Smart Security are getting the same errors. So it does not seem to be solely a NOD32 issue but an ESET issue.
     
  10. shadowsun

    shadowsun Registered Member

    Joined:
    Oct 29, 2009
    Posts:
    2
    Having this very same problem in Windows 7 Ultimate 64 bit and it needs fixing URGENT.

    Sent a ticket to ESET hopefully this will help the cause. Very, very annoying and it's wearing thin.
     
  11. jimwillsher

    jimwillsher Registered Member

    Joined:
    Mar 4, 2009
    Posts:
    667
    Don't fret. Just uninstall and revert to 4.0.437. What's the big deal?



    Jim
     
  12. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    Yeah, fret not lol....

    the developers know what changes they made from 4.0.437 to 4.0.467, this will be easy for them to figure out.
     
  13. the1

    the1 Registered Member

    Joined:
    Oct 28, 2009
    Posts:
    15
    Well I hope it is figured out quickly. :)
     
  14. shadowsun

    shadowsun Registered Member

    Joined:
    Oct 29, 2009
    Posts:
    2
    Not a big deal as such, but I've reinstalled Windows 7 twice now and I don't want to start uninstalling anti virus software and it leaving things behind.
     
  15. GAN

    GAN Registered Member

    Joined:
    Mar 3, 2007
    Posts:
    355
    Not a big deal for a home user, but for companies that might have 200 clients to rollback then it might actually be a big deal. Also if you are affected by a bug in 437 that is fixed in 467 it could be a big deal since you want a new version with the fix, but cannot use it yet because of a new bug.

    For me it's not a big problem since i only have one computer with Nod32.
     
  16. the1

    the1 Registered Member

    Joined:
    Oct 28, 2009
    Posts:
    15
    My program modules just updated. *crosses fingers*
     
  17. Funky3ddy

    Funky3ddy Registered Member

    Joined:
    Oct 30, 2009
    Posts:
    1
    Hey there.
    Today downloaded and installed NOD32 v4.0.468.0 (Trial) on my Windows 7 Ultimate v6.1.7600 Build 7600 x64-based PC
    And having the same problem with file creation. (..Firefox)

    I am Administrator on this PC so no problems should occur.

    Apparently Nod32 just locks files up before "X" program actually starts to write 'em.. (if scan-on-create protection is disabled, this error disappears)
    To be honest, I have no idea how to fix this.. maybe to add some sort of a rule like "Skip scan" if "File Size:0 bytes"


    Anyway, this is terrible guys. You should not worry about me, I am an old nod32 user and know that it is a great antivirus, but for new users this could be the last time when they try another Eset's program ;)

    Sorry for my bad english
     
    Last edited: Oct 30, 2009
  18. GAN

    GAN Registered Member

    Joined:
    Mar 3, 2007
    Posts:
    355
    I don't think there is anyway to fix this without disable some options that will compromise the security. This is a bug that has to be fixed by Eset.

    For some reason they are unable to reproduce the same problem so it's hard to tell when a fix will be available. Seems like a lot of people are affected by this problem. Read about the same issue in other forums as well.

    Since Eset obviously don't find this to be serious enough to remove the download links for the 467/468 release until fixed they should at least give the customers an option to download the previous public release (437). Also post a notice about this problem which is currently under investigation.
     
  19. Deviad

    Deviad Registered Member

    Joined:
    Oct 31, 2009
    Posts:
    4
    Hello,
    I have had this issue with ESET NOD 32 and Windows 7 since version 3.
    I have used the final release of Windows 7 for almost 2 months. I called ESET here in Italy and what I was told is that they didn't have a fix and the guy didn't even want to file a report.
    The final version of Windows 7 has been available to the developers for more than 2 months. My university offers MSDN accounts to the students so I have immediately downloaded Windows 7.
    Now, I ask myself why these guys didn't fix the problem in time for the release to the retail market. It's really awful.
    I went back to Avira which I decided to leave and with that I get Web guard and mail guard stopping to work suddenly; what they suggest is: reinstall.
    Once you reinstall after 3 - 4 days the problem is there again...
    Seriously, these guys had plenty of time to work on Windows 7 and they basically did nothing.
    I would start to mass mail them otherwise we can wait weeks before this is solved.
    For me it's a very boring issue expecially when I use Ensign (a market analysis software) as when I change the properties of a chart or I create a new one or simply add a study to a chart I get this damn error.
    The more I buy these programs the more I regret not using cracked versions. At least when you don't pay you don't have reasons to complain...
     
    Last edited: Oct 31, 2009
  20. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,456
    As I have already written, the issue is being investigated. Until it's reproduced in ESETs lab it cannot be fixed. How can you fix something that you don't know what it's caused by? Actually we found similar issues with earlier builds of Windows 7, but these seem to have eventually been fixed in Windows 7 RTM. However, this does not guarantee that Win7 RTM is bug free and that the problem is at ESET's part. Again, the issue is being looked at so the case has not been closed.
     
  21. Deviad

    Deviad Registered Member

    Joined:
    Oct 31, 2009
    Posts:
    4
    When I get such answers it looks to me like what happens here when you go to public offices... they keep blaming the other office and they don't solve your problem.

    Let's suppose this is a problem of Windows 7 which I doubt, other antivirus programs do not suffer this problem. So the average user will do 2 things:
    1) first complain about the issue;
    2) if the problem is not solved soon he will switch to another antivirus and say to his friends: "Hey do you know that NOD32 is crappy?". And those guys will tell them to other people not to buy or install NOD32. With the Internet this thing gets even wider on a world scale. Hence the antivirus programs that on Windows 7 launch do not suffer problems like this gain market share. Easy...
    Same happens when a game is launched. If it looks like a beta people just drop it, after 3 - 4 months it can be the best game in the world but people simply do not get the nerve to try it again because of the past bad experience.

    This Windows 7 launch was widely anticipated and publicized. Current Microsoft's CEO even suggested not to buy Vista anymore and wait for 7...
    I understand that there's the crisis, companies have to save money etc., but do you really wanna save that on maintenance of your software when there's the launch of a new OS?

    I see this even when I talk to customare care services... ever less prepared people answer your calls, business hours are reduced, etc.
    Imho this is not where the cuts should be applied since customers are your greatest resource as they are those paying your bills. But this is not just ESET.

    P.S.: if you wanna be sure to reproduce the issue, just download a demo of Ensign Windows, and you will start getting plenty of these errors. Once you uninstall NOD32 the problem gets solved. Tried with Avira, no problem... but as I said I do not like Avira for many other little issues that have not been solved over 2 years so I hope you will fix this issue on 7.
     
    Last edited: Oct 31, 2009
  22. Sumatra

    Sumatra Registered Member

    Joined:
    Oct 31, 2009
    Posts:
    2
    I'm having the same issue. I don't have a copy of v4.0.437 to downgrade to. Is there a place on the Eset site I can get it? I couldn't find anything. If I can't downgrade I'm going to switch to someone elses product as v4.0.468 is unusable.

    Thanks.
     
  23. PRJUS

    PRJUS Guest

    I fully understand that it's hard to fix something that you can't reproduce but the error isn't there in 4.0.437 which I have had to revert to as well so perhaps someone could sit down and analyze the changes made between the two builds and find some probable causes for these issues that look like timing issues as they won't show when the computer is busy running for instance Process Monitor.
     
  24. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    Didn't someone say they had this problem in windows 7 even with NOD 3.0 ?

    Does this happen in windows vista ? which is similar in many ways to windows 7.

    Also, the problem is obviously windows 7 and the way it interacts with NOD, or the other way around, but still it's something windows 7 is doing that NOD doesn't comprehend or agree with while it's running on that OS.

    true other antivirus may not behave this way on windows 7, but that doesn't mean that eset needs to patch a problem to make it work, it might boil down to a microsoft patch to fix it.it depends if there is a workaround on esets part, if not, then ....... wait for microsoft to patch it.

    Maybe it has something to do with advanced options in NOD, are all these people who have this problem running NOD out of the box ? or have you tweaked your settings ?

    maybe you should specify exactly which software and hardware is running on these problem machines, so they can have a better chance to see it happen in the eset labs.


    There are millions of people using NOD 4.0 with windows 7, but only a dozen people have this problem or else there would be tons of people here complaining.Might want to check your end as well to find the reason for the conflict.Have you guys tried a clean install of windows 7 with nothing on it but NOD32 and see if IE still does it while you try to download ? maybe it has to do with protected mode of IE as well, you can turn off protected mode by shutting off UAC.
     
    Last edited: Oct 31, 2009
  25. KCH

    KCH Registered Member

    Joined:
    Oct 31, 2009
    Posts:
    1
    I have the same problem.

    Win7 Pro 64-bit
    NOD32 v4.0.467.0

    IE8 Protected Mode Off does not solve the problem.

    Disabling Real Time Protection: Scan on Create solves problem, but rather not have to do that.

    How do I activate "Process Monitor Log" ??
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.