analysis of application protocols will not function?

Discussion in 'ESET NOD32 Antivirus' started by zonemaster60, Aug 6, 2009.

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

    zonemaster60 Registered Member

    Joined:
    Aug 6, 2009
    Posts:
    17
    Location:
    Hornell, NY - USA
    Just rebooted my system after installing a video driver update and the updated Klite codec pack and got this error. My sons computer has this same exact problem. Apparently he has checked and asked around the forums here and it seems know one actually knows what the problem is or a solution for it. I have included a screen shot of the NOD32 main window. I don't know what happened actually, I just rebooted my computer and poof the error. I am running Windows Vista 32-bit Ultimate. If you need any more info for troubleshooting purposes, I would be glad to post them.
     

    Attached Files:

    Last edited: Aug 6, 2009
  2. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    Hello zonemaster60,

    Try reinstalling the ESET software. There are some instances we have seen where an update or new software installation causes the ESET software to malfunction.
     
  3. zonemaster60

    zonemaster60 Registered Member

    Joined:
    Aug 6, 2009
    Posts:
    17
    Location:
    Hornell, NY - USA
    I'll give it a shot. I'll post back with my results. Actually reinstalling made things worse than before. Some programs even failed to start before that worked fine. After second reboot was back to same old problems as before. I am trying system restore to an earlier point in time such as yesterday when this wasn't a problem. You guys or devs really need to look into this problem as I WONT be restating my subscription after 09/2010 when my subscription expires. Uninstalling and looking for another anti-virus alternative, IMHO not worth the trouble. Hmm, i wish i could get my money back now for the year left I have on my subscription. I'm sorry but this isn't worth my time if no one will help and only a few people have this problem. It's easier for me just to find another better alternative that i don't have to worry about causing these problems.
     
    Last edited: Aug 6, 2009
  4. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    I got sick of Norton antivirus letting things slip past real-time protection, only for me to run a manual scan with the same virus definitions, no update and it finds the virus that way. I saw a review on pc magazine online or cnet I don’t remember, but it was from about 2007 or 2008 and it listed kaspersky as first place followed by Symantec, eset and bit defender, though I do not remember the exact order of how they ranked, I just know eset was in the top 5.now I decided to mess around with eset NOD32, I tried version 3 and version 4, I think they added to many things I have no control to remove like the graphs and such, so my preference is version 3.

    Therefore, I played around with version 3 for a few weeks. I noticed that it auto adds programs that connect to the internet for you in the HTTP POP3 group including email clients, this is a function of the epfwtdir.sys file, which is placed under the hidden view of non-plug and play drivers in your device manager. If for some reason that driver fails because of itself or a problem with another driver, then this auto adding of programs and email clients will not work, also going to a web page and clicking on a link attached to a virus will not be detected.

    How to fix the problem?

    I noticed like clock work, after 4 reboots after installing NOD32 3.0 the driver starts to fail and I get this message in the EVENT log of NOD32 “Personal firewall: An error occurred while starting proxy server. Checking of application protocols (POP3, HTTP) will not work. “

    This is not the same error people get when they reboot and their eset icon is RED and they get a message displayed in their main program window that reads “Personal firewall: An error occurred while starting services. Analysis of application protocols (POP3, HTTP) will not function. “

    That is something different I will get into soon, but if you see this error by itself or accompanied by the other error above the same parts of the program will not function as stated above.


    I have only tried to install this on AMD platform pc’s, I doubt there is an incompatibility with AMD systems specifically, but I have installed NOD32 3.0 on 5 systems so far, and they all do the exact same thing, either default or custom install option selected does not change this while setting up the program. Nothing is changed, reboot 1, 2 ,3 times is still ok and change nothing, reboot again and the problem starts. I have not tried NOD32 on any Intel systems yet.

    I tried to google this problem and see a lot of people had the problem but it was never resolved and people left hanging for an answer, I am happy to say the problem has been solved by me.

    At first I thought the problem was the epfwtdir.sys file was failing, and I thought it was a little strange that this driver was missing the version info tab and the other 2 was fine. So my first way to fix it was to download NOD32 version 4, save the drivers folder, and use the version 4 epfwtdir.sys file. That made the ( “Personal firewall: An error occurred while starting proxy server. Checking of application protocols (POP3, HTTP) will not work. “ ) Error go away and not return, so I was sure that the files of version 3.0 was screwed up and never fixed and again I thought it was weird it (epfwtdir.sys ) was digitally signed but was missing it’s version info tab ( they should fix this )

    epfwtdir.sys is directly responsible for the 2 errors I mentioned though, but for different reasons, which I will get to.

    Therefore, that was my first fix, the error went away, and Internet checking functionality was restored using the version 4.0 driver.

    Then I noticed the real reason the driver was starting to fail, it was the startup type used by another eset driver easdrv.sys which is also in your hidden non-plug and play drivers section in device manager.

    They have it set for “ system start “ and this is clearly not agreeing with other things, I set it to “ automatic “ or “ demand “ start and with the version 3.0 of epfwtdir.sys the problem and error messages went away again and never came back, this is reiterated if you start in safe mode and you see and exclamation point by the driver easdrv.sys when it is set to system start but you change it to auto or demand and reboot and then reboot again into safe mode and the exclamation point telling you there is something wrong with the driver is no longer there, and it’s all fine now.

    So basically the fix for this error “Personal firewall: An error occurred while starting proxy server. Checking of application protocols (POP3, HTTP) will not work. “ At least on version 3.0 is to mess with the startup type of the other drivers used by eset till they all function properly together.

    But for this error “Personal firewall: An error occurred while starting services. Analysis of application protocols (POP3, HTTP) will not function. “

    That means your epfwtdir.sys driver has not started at all more than likely, I don’t know how to fix this, never got that error in 4.0 as I use 3.0, if you get this error though, I would check to see if there is a problem with that specific driver and if it started or not, and also try changing the startup type for that driver from system to automatic, if you set epfwtdir.sys to demand start it will definitely fail to start, so your only option for that is system or automatic start for that particular problem..


    That’s it ! fixed !

    They need to change the startup type in the install INF to stop this from happening.

    I like eset as a company and I LOVE NOD32, but it’s “ quirky “ some things they say work clearly do not, for no reason, it’s just “ quirky “ but so am I, so I like it.

    For instance, they say it supposed to play a sound when a virus is found, that never worked and I even looked in windows sounds for an eset category and found nothing. Also the submit feature im pretty sure does not work, I tried to submit a couple files from within the program either from right click context menu or from within the main program window and neither time did it ask me for internet access when it was not set yet in my firewall program and I even disconnected from the net and tried to submit and I never got an error message or anything that it tried to submit the file but had no internet connectivity……… just some quirks need to be worked out that’s all, then NOD32 both versions will be 100%

    ************* My bad on the submit feature.It works perfectly, I did not have threatsense enabled, I enabled threatsense and the submit feature worked as it should ******************


    I also want to add that it is pretty impressive that NOD32 is able to do internet filtering without an NDIS service bound to the network adapter and it works very well when you get a couple things ironed out.

    Also not that any of my virus signature updates have failed, but if they ever do, unlike norton or any other antivirus progam, I know exaclty how to fix them in NOD32 should it ever happen that the database gets corrupt and how to reset things and get a clean update, very easy to fix that if it should ever happen.

    overall since i know how to fix alot of things and get this program working right, I really like it, and praise it.
     
    Last edited: Aug 10, 2009
  5. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    Forgot to mention this happens to me on Windows XP SP2 and SP3 systems.The operating systems came directly from microsoft and NOD32 came directly from the download page version 3.0.684.0.I'm not sure if people have these issues with the retail CD of NOD32 or if it's just the download version.Is the cd version also missing file information for epfwtdir.sys ?

    Tried NOD32 3.0 on windows 7 and could not reproduce the problem, allthough the easdrv again like windows xp, had an exclamation point in safe mode until i changed the startup type from system to auto start.

    Then i tried version 4.0 NOD32 directly downloaded from eset on windows 7 to try and reproduce the problem zonemaster60 is having.seems it uses differen't drivers on windows 7, not sure about XP.I only saw ehdrv and epfwwfpr in the hidden non-plug and play drivers, and like easdrv did in windows XP, the ehdrv in windows 7 has an exclamation point in safe mode saying there is something wrong with the driver till you change the startup type from system to auto start. But unlike the XP senario where this fixes an issue, in windows 7 setting ehdrv to auto start makes epfwwfpr fail and then you get the errors we talked about before, also in the log it says could not communicate with epfwtdir.sys which was not installed by NOD32 version 4 in windows 7.Anyway since it's my own system to experiment on, i installed version 4 of epfwtdir.sys and version 4 NOD32 started using this file and did not bother to start service for epfwwfpr.sys and the firewall pop3 html error went away and the program seemed to have no problems functioning correctly.
     
  6. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    NOD32 3.0 has 3 folders for 3 drivers:
    eamon
    easdrv
    epfwtdir

    the same drivers get installed weather the operating system is windows 2000, XP or vista / windows 7.

    NOD32 4.0 has 4 folders for 4 drivers:
    eamon
    ehdrv
    epfwtdir
    epfwwfpr

    on windows 2000 and windows XP only eamon, ehdrv and epfwtdir get installed and those 3 folders will show up under the drivers folder in your NOD32 install folder.

    on windows vista / windows 7 eamon, ehdrv and epfwwfpr get installed only.

    if your using 3.0 in any of these versions even though windows 7 says it's not compatible because it does not integrate with their security center, it still functions properly and is easy to fix if you get this error “Personal firewall: An error occurred while starting proxy server. Checking of application protocols (POP3, HTTP) will not work “ or this error “Personal firewall: An error occurred while starting services. Analysis of application protocols (POP3, HTTP) will not function “

    “ An error occurred while starting services “ should give the clue that a service did not start, this service is epfwtdir in windows 2000 / XP and epfwwfpr in windows vista / windows 7, which can be found in device manager under “ view “ hidden devices under non-plug and play drivers.

    This error “Personal firewall: An error occurred while starting services. Analysis of application protocols (POP3, HTTP) will not function “ will give you a red icon and a message in your event log of NOD32 and also a message in your main program window.

    This error “Personal firewall: An error occurred while starting proxy server. Checking of application protocols (POP3, HTTP) will not work “ you will still have a green icon and no message in your main program window, but an error in your NOD32 event log and auto adding of email clients and other programs that connect to the internet will not function when you see this error and virus checking of links won’t function either.


    The problem is easily fixed with NOD32 3.0 on all versions of windows and NOD32 version 4.0 is easy to fix these problems under windows 2000 / XP, however in windows vista / windows 7 with the new driver introduced it is not easy to fix.

    Does everyone get it now ? I explained how to fix both versions in windows 2000 / XP and NOD32 3.0 in windows vista / windows 7, but cannot fix version 4.0 in windows vista / windows 7 because of the new driver introduced.
    Downloading a fresh copy as they suggest in the knowledge base is not the problem, unless the fresh copy means downloading a new build of that particular version your using.

    The moral of the story is if your having problems with 4.0 in vista / windows 7 there is no fix outside of reinstalling.if you have this problem, just go back to 3.0 for now.


    delaying startup items is NOT the problem, but the driver load order might be causing an issue because a problem driver is initializing before the others and causing a conflict.

    when you have a software driver set to boot or system it goes by load order if a load order group is set for it.

    when you have a software driver set to automatic start or demand start, then the load order groups are bypassed and the driver starts after all the drivers set for load order groups have started.

    I have a problem with version 3.0 only on windows xp SP2 and SP3. on windows 2000 and windows vista / windows 7 same config the problem does not happen.

    all the XP machines have either a VIA or Nvidia chipset with nvidia cards for video, but i have never seen or heard of hardware configs or hardware drivers causing a conflict with software drivers, so i will never know why it's doing it, however i know the work around, so it doesn't bother me at this point.Just wish it would be fixed so i wouldn't have to manually every time.

    also i used to be a pc tech for companies. if i went around reinstalling every time there was a problem instead of finding out why it happens at the root of the problem, i would have got fired a long time ago.reinstalling does not fix the issue of the cause, it only masks it.If the problem occured to you, then it's not a question of if it will happen again on the same machine, but a question of when it will happen again.... so you going to keep reinstalling as a temporary fix ? you should not have to.
     
    Last edited: Aug 12, 2009
Thread Status:
Not open for further replies.