Discussion in 'ESET NOD32 Antivirus' started by Marcos, Nov 6, 2007.
I did not want the link for a version with user and password but yes for a version trial straight
Not sure if it's the new build.
Thanks for help
Sad to report, my Outlook express just glitched out again. It only happened once - first time opening after reboot. Tried to start OE, got the Windows clang, the OE window flashed but did not open. Clicked OE again and it started properly.
One other issue with V3.0.560, the first reboot after installing it on top of 3.0.551, the "Automatic real time file system protection startup" didn't work. I checked the setup tree and this option was not checked and I'm quite sure I didn't uncheck it. Got the windows security center warning at startup about no AV running... I checked the box and restarted and the AV protection was OK. Then I tried to open OE and got the clang. Starting to feel like a beta tester
My system is Win XP Pro SP2. Other security apps in sig.
I am happy to report that V3.0.560.0 has indeed corrected the problem for me. Have accessed OE at least 40 or fifty times over the past three hours without an occurrence of the Crash Upon Launch problem. I was one who posted in two threads that I too was experiencing the problem and to the point of wanting to revert back to v 2.7 because of it.
Am still experiencing some lag upon exit, however it lags for only about 2 seconds which is something I can easily overlook.
Trial version tested links download1, download2 and download3 servers version 551
What about right after a reboot? That now seems to be the only time I get the crash.
With zass are there any known clashes/conflicts with EAV, Nod etc? I mean known in the sense of posted on the various support centers or forums?
This is as you know, not a challenge question.
In Nod 32, I like to except other security software so it doesn't scan their peers and block/disable etc etc. IMHO. This is one of my policies for security software.
Hi Escalader. None with Nod32. Not sure about EAV. All premissions in pgm control are given. If it looks like my installtion is the only one with a problem, I may try a reinstall later.
I hope they sorted the gui in exluded addresses in advanced setup or theres not much point updating. Can someone post a screenshot of excluded addresses (with no addresses in the list) thanks
Can't agree with the idea that SW products or flu serum have to be corrected by mass exposure.
Here is something on quality control I just received from a professional organization seminar write up. I can't id it here. But if we substituted EAV for automobile, electricity, etc and SW bug for repair, no lights etc it would be an interesting "paper". Note that GE etc are in competitive business's and have increased revenue.
Take it easy
After installing v3, I was getting a 'code injection' warning from Sunbelt Personal Firewall (SPF) the first time I opened Outlook Express after a reboot. (Screenshot link). OE appeared to work properly once I closed the warning and I could re-open it without getting the warning. I updated to the latest release (3.0.560.0) and still got the same problem. I've now 'allowed' the ESET service in the HIPS section of SPF and had no further bother.
I hope this info' may give a clue to cause of the problem.
Just tried a reboot and went immediately to OE - no crash.
Yeh i just tried that to ..no crash.
Thanks poutine and Supersnake. Sounds like I need to try a clean reinstall.
never hurts to do a clean reinstall. Make sure you also get rid of the eset data in documents and settings
Good luck oldshep. let us know how it goes.
I realised, I read everyone have complaint about EAV release still trouble. You said .551 was perfect then .560 is not perfect.
When I get download ESS (BETA) was problem freeze a OE. I gave it up, return to NOD32 v2.7 was fine on us.
Everyone are right. because many million are different software or 3rd party software been installed. EAV or ESS might be very carefully and test a working with it. Many Forum users are alway right way been told to ESET Development Team should be fix a correct. Until Forum user feel very happy with it and most less or very few a complaint. Finaly to released version it.
If ESET Team ignore you, A million will not buy ESET will be loser against Forum user told been to ESET must be fix immediate... on next .561 or whatever.
Believe me, Eset will not ignore the forum members. All the problems will be solved. Please have a little patience.
And now I can't reproduce the error either
I haven't changed anything or re-installed. But after 5 reboots, I can't generate the error with OE. Oh well, I guess I should be grateful and just move on
I like your sense of humor - on second thoughts . . . . . . . . . . . . . . . . . . . . maybe, you were NOT joking