Jump to content

Web traffic hangs during update triggered startup scan


fardbark27
 Share

Recommended Posts

Recently I have found that when a virus sig update triggers a startup scan, it seems to block or at least severely slow my web traffic down to the point that browsers are unusable.   Usually I will find the browser tabs have stopped responding and immediately I can check the tray and confirm that I find NOD32 running a startup scan which in turn seems to have been triggered by a virus signature update. 

 

If I pause protection suddenly my network traffic returns unfettered. 

 

For now I have turned off HTTP protection and that seems to solve it, but of course I am not thrilled to have to do that. 

 

Could it be that NOD32 gets backlogged or hung a file scan for a few moments and when it does the network requests are queuing up because of that? 

 

At the moment the update-triggered scheduler entry for Startup Scan runs at lowest priority - I am wondering if that needs to be bumped up so that the process doesn't get hung up? 

 
Thanks in advance for any input/ideas. 
 

Details:  Lenovo X1 Carbon with Win 7 x64 w/ NOD32 v.8.0.304 aka latest update as of this writing...

 
Link to comment
Share on other sites

Hello,

 

1. Enable web access (http) protection again. It is very essential to have it enabled.

 

2. Go into the scheduler via the program GUI and uncheck the startup scan that is set to run after each successful VSD update.

 

But be sure to leave the startup scan enabled that is set to run at "user logon".

 

This way the startup scan won't run after each update, but will still run at each user logon. And you can always start a startup scan manually when ever you like by right clicking on the task in the scheduler and choose "run now".

 

Hopefully this will improve your situations so you don't experience that the system hangs due to the startup scan after each VSD update. 

Link to comment
Share on other sites

Yeah I guess that's a better workaround for my current situation and I'll prob do that so thanks.  

 

But I'm still hoping for a better answer - I have been a customer and vocal 'net promotor' of ESET and NOD32 for almost 15yrs and never had this problem before, its recent.   

Link to comment
Share on other sites

I see. I don't know why it started happening recently for you, but until you get a better answer, this work around is much better and safer than disabling the web access protection altogether. 

Link to comment
Share on other sites

At first you need to find out what is causing the issue. As for...

Could it be that NOD32 gets backlogged or hung a file scan for a few moments and when it does the network requests are queuing up because of that?

you could be right of course.

 

You can change the TreatSense1 settings of the startup scan in the settings:

post-3952-0-39937900-1424450513_thumb.png

 

The first tries could be to enable "Log all objects" to see whether it is caused by a specific file and to (temporarily of course - don't forget to ren-enable it) disable ESET LiveGrid there.

Both times you can try to start an startup scan manually and see if your issue still happens.

 

1 (that's the scanning engine of NOD32 and other ESET products)

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...