Sorry !!! one correction
Web Shield off permanently - internet works as usual - very fast I mean.
Hello Peter,
thanks for the report. If you are really running on the updated version of the driver (aswstm.sys, 265 - yes, in system32\drivers - you can tell easily it is the correct one by the fact, that there are many other driver (.sys) files there), I have no clue at the moment. I might guide you how to enable logging and we might try to find some hints in the logs, it all depends if you are willing to spend some time with it.
If not, I would suggest switching back to proxy-based WebShield, by the following change in the ini file:
websheld.ini
[General]
UseStreamFilter=0And restarting.
Everything should run as before, even though not exactly the same as the whole period you are using avast. WebShield was introduced in avast 4.5, and later modified in behavior in 4.8, which is roughly 10 years ago, so switching WebShield off would bring you more into the golden years before that.
In case you would like to help finding the problem, and also for anyone other with same/different symptoms with 9.0.265, here are the logging settings that would generate some logs for us:
StreamFilter.ini:
[Common]
FileLogLevel=0
RecordInput=1Restart the shield.
Then send us the log folder and nsf folder, both subfolders of the avast's programdata (C:\ProgramData\Avast Software\Avast\log, C:\ProgramData\Avast Software\Avast\nsf)
All edits in the INI files should be done with SelfDefense disabled, I recommend re-enabling it back and undoing the edits after your are finished with testing.
Even more logging can be obtained with DbgView, download from here:
http://live.sysinternals.com/Dbgview.exeRun as administrator, in the menu, select enable Kernel Capture, enable Verbose Kernel Output.
After the problem occurs (which should be easy), send us the output from the debugview window together with the logs.
BTW: if you see the following line, you are running the correct version:
AswStm.sys, ver. 9.0.2011, patch 3 - 'Lauri'We'll continue testing of course. It is a new code, so actually we were expecting some problems, but it is also being tested in our QA lab at least since August 2013, so it is not rushed and it behaves great in our tests. So far it seems that the API we are using (WFP) is behaving differently in Windows 7 (no SP).
Anyone with similar problems on Windows 8?
Thanks a lot for all your reports and patience. Lukas.