Jump to content

"Windows-Update 3172605" and "Application protocols (HTTP, POP3, IMAP) are not checked"


Recommended Posts

Hello,

 

after the installation of the Windows-Update "KB 3172605" the following error is found in the log file of NOD32 AV.

 

 

Personal Firewall -> Beim Starten des Proxyservers ist ein Problem aufgetreten. Anwendungsprotokolle (HTTP, POP3, IMAP) werden nicht geprüft.

(While starting the proxy server an error occurs. Application protocols (HTTP, POP3, IMAP) are not checked.)

 

I am using:

  • Windows 7 Pro SP1 64bit
  • ESET NOD32 Antivirus 9.0.386.1

Although this mistake appears in the logs, NOD32 has a green icon and tells me that I am protected.

I'm a little bit confused about this.

 

Thank you very much and sorry for my broken English but English is not my native language.

 

post-1107-0-41219600-1469625606_thumb.png

Link to post
Share on other sites
  • Administrators

Does the problem persist after a computer restart? If so, please post the output of running the following commands with administrator rights when the protection status is red due to the above mentioned error:

sc query epfwwfpr

sc qc epfwwfpr

Link to post
Share on other sites

Hello Marcos,

 

thank you for your answer.

This error occurs directly after the reboot of the installation of Windows-Update "KB 3172605".

If I do not install "KB 3172605", there is no error. I suppose that the update is responsible for the error messages.

 

After several reboots (or after a successful update of the virus signatures) it seems that this error message is not coming back on one of my PCs.

On the other PC I get this error message after every reboot.

 

 

Here is the output of the commands (this output is identical on both PCs):

 

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Windows\system32>sc query epfwwfpr

SERVICE_NAME: epfwwfpr
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

C:\Windows\system32>sc qc epfwwfpr
[sC] QueryServiceConfig ERFOLG

SERVICE_NAME: epfwwfpr
        TYPE               : 1  KERNEL_DRIVER
        START_TYPE         : 2   AUTO_START
        ERROR_CONTROL      : 0   IGNORE
        BINARY_PATH_NAME   : \SystemRoot\system32\DRIVERS\epfwwfpr.sys
        LOAD_ORDER_GROUP   : PNP_TDI
        TAG                : 9
        DISPLAY_NAME       : epfwwfpr
        DEPENDENCIES       : Tcpip
        SERVICE_START_NAME :

C:\Windows\system32>

 


 

 

 

Link to post
Share on other sites

Appears KB 3172605 has triggered an old bug described in this thread:  https://forum.eset.com/topic/6344-getting-an-error-when-rebooting-computer-with-new-version-9/ . Eset even issued its own KB on the problem here: hxxp://support.eset.com/kb5676/ .

 

My take on this is KB 3172605 might be only impacting certain Win 7 versions w/Eset installed. I installed it and having no issues on Win 7 Home SP1, x64. 

 

BTW - do you actually use a proxy server?

Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...