simplicissimus 2 Posted July 27, 2016 Share Posted July 27, 2016 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. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,408 Posted July 27, 2016 Administrators Share Posted July 27, 2016 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 comment Share on other sites More sharing options...
simplicissimus 2 Posted July 27, 2016 Author Share Posted July 27, 2016 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 epfwwfprSERVICE_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 : 0x0C:\Windows\system32>sc qc epfwwfpr[sC] QueryServiceConfig ERFOLGSERVICE_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 comment Share on other sites More sharing options...
itman 1,790 Posted July 28, 2016 Share Posted July 28, 2016 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 comment Share on other sites More sharing options...
simplicissimus 2 Posted July 31, 2016 Author Share Posted July 31, 2016 Hello itman, thank you for your answer and links. BTW - do you actually use a proxy server? No, I do not use a proxy server. Link to comment Share on other sites More sharing options...
Recommended Posts