Losing internet connectivity

As I pointed out to Thankful, here, I still run the task disabled but do run it when my PC has nothing better to do since it is recommended that this task be scheduled to be used at all times.

Adjusting protocol filtering, I have found, over time for a typical DSL connection user works for optimal connectivity, your results may vary.
Use what latter setting works best for your situation.

 

Since I disabled automatic scanning after updating the database this bug seems to have gone. It's a pity that Eset still only offers this workaround and has not fixed this bug.

 

Please do the following:
- disable automatic updates
- when a newer update is available, start capturing file operations using Procmon and leave it running until the startup scan completes

Besides the Procmon log, generate a complete memory dump during update when the connectivity is lost per the instructions here and convey it to ESET along with the pml log (pm me for further instructions when you have the stuff ready).

Is the connectivity restored automatically after the startup scan completes?

 

The problem is not the usual startup scan, this works fine. The problem is later, during work (maybe whenever a new database update is automatically downloaded and then the following scan is started). I disabled the automatic scan after database update and this works as a workaround. And no, the connectivity wasn't restored automatically after database update and scanning. The connectivity was only restored after rebooting the machine. And, this bug only appeared occasionally after database updates (every few weeks) so it may depend on which files are updated during the update process. The bug search may be complex because this bug isn't easy to reproduce. Another user reported that there may be a correlation with the self-defense of NOD32.

 

After several years of operation we've suddenly encountered this issue, non-reoccuring so far on 4 out of 160 clients with 3.0/4.0/4.2 mix installations but only 3.0 affected so far. I cannot help but think that the bodged update during new years that was fixed, has the actual fixed files caused this issue in some way?

I've found that when attempting to resolve the issue outside of restarting the pc the eset gui is active, but 3/4 are non-admins. Killing the egui.exe to run it as an admin results in a sudden and sustained spike of cpu utilization for several minutes until the gui finally appears, at which point its rather blank and none of the menus work. running it as the local user gives the same result.

I've adjusted policy with the 'FIX' suggested here to see how things go..

**EDIT**

Client info incase anyone is interested (2 laptops and 2 desktops)

R-AMPONSA
Information on operating system
Operating system: Microsoft Windows XP
Operating system version: 5.1.2600 Service Pack 3
Operating system type: 32-bit
Version of common control components: 5.82.2900
Processor: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz (2259 MHz)
System memory (RAM): 3540 MB

Information about executive parts
Virus signature database: 5760 (20110104)
Update module: 1031 (20091029)
Antivirus and antispyware scanner module: 1293 (20101110)
Advanced heuristics module: 1115 (20101116)
Archive support module: 1124 (20101214)
Cleaner module: 1050 (20101207)
Anti-Stealth support module: 1023 (20101125)

Information about installed product
Product version: 3.0.695.0
Product name: ESET NOD32 Antivirus
Product language: 1033


REPRO-1
Information on operating system
Operating system: Microsoft Windows XP
Operating system version: 5.1.2600 Service Pack 2
Operating system type: 32-bit
Version of common control components: 5.82.2900
Processor: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2327 MHz)
System memory (RAM): 3317 MB

Information about executive parts
Virus signature database: 5760 (20110104)
Update module: 1031 (20091029)
Antivirus and antispyware scanner module: 1293 (20101110)
Advanced heuristics module: 1115 (20101116)
Archive support module: 1124 (20101214)
Cleaner module: 1050 (20101207)
Anti-Stealth support module: 1023 (20101125)

Information about installed product
Product version: 3.0.695.0
Product name: ESET NOD32 Antivirus
Product language: 1033


LIBRARY
Information on operating system
Operating system: Microsoft Windows XP
Operating system version: 5.1.2600 Service Pack 3
Operating system type: 32-bit
Version of common control components: 5.82.2900
Processor: Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz (2194 MHz)
System memory (RAM): 1015 MB

Information about executive parts
Virus signature database: 5760 (20110104)
Update module: 1031 (20091029)
Antivirus and antispyware scanner module: 1293 (20101110)
Advanced heuristics module: 1115 (20101116)
Archive support module: 1124 (20101214)
Cleaner module: 1050 (20101207)
Anti-Stealth support module: 1023 (20101125)

Information about installed product
Product version: 3.0.695.0
Product name: ESET NOD32 Antivirus
Product language: 1033



S-FENTON
Information on operating system
Operating system: Microsoft Windows XP
Operating system version: 5.1.2600 Service Pack 3
Operating system type: 32-bit
Version of common control components: 5.82.2900
Processor: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (1662 MHz)
System memory (RAM): 2551 MB

Information about executive parts
Virus signature database: 5760 (20110104)
Update module: 1031 (20091029)
Antivirus and antispyware scanner module: 1293 (20101110)
Advanced heuristics module: 1115 (20101116)
Archive support module: 1124 (20101214)
Cleaner module: 1050 (20101207)
Anti-Stealth support module: 1023 (20101125)

Information about installed product
Product version: 3.0.695.0
Product name: ESET NOD32 Antivirus
Product language: 1033

 

Yes it a mystery why the startup scan doesn't have this problem only when the update occurs during web browsing. It effects all browsers. Firefox Internet Explorer Chrome haven't tried Opera.

 

I have very similar problem as described. Also, when this occurs, I cannot disable my ESET nor uninstall. A reboot is required. I have also noticied that my NOD32's last successful update date is x/x/1601. Very odd, seem like the application crapped out. Upon reboot, I confirmed that the definition was updated earlier(~3-4 hours ago) during the day(so it could not have been part of the def update).

We have about 150 clients and this randomly occurs. We didn't pinpoint it to ESET until recently.

I will give the suggestion(disable scanning after update) in this thread a try.

 

The scheduled start-up file check has been working for me of late under the latest build without issues on a stand-alone PC.

This may vary with your connection type, ISP and other variables.

As discussed previously in this thread one can enable the task and run it from the scheduler window when the workstation or PC has nothing better to do.