For SOA users - The update “141125-1” appears to include the 8.0.1603.401 version of aswSnx.sys, which if your mirror service is working correctly, you should already have… The clients will need to update at their regular intervals however, unless you click the “update engine and virus definitions” button at the client directly…
On to testing the update vs Microsoft patches…
So far so good. We are having success with the Avast update. We have some with the MS KB update on them still and after a reboot Avast has updated and the problems are gone. We have re-applied the MS update to some that we have removed it from and they are working good as well.
I currently have avast! Endpoint Protection Suite 8.0.163 Virus Definitions Version: 141125-1. How do I know if the patch has been updated? Do I just need to look at the aswSnx.sys properties and see if it is 8.0.1603.401?
Yes, that’s enough.
I Deployed Avast to another workstation and for some reason the aswSnx.sys does not update. Still stuck on 8.0.1603.399. Is there a trick to force the update? Update engine is at 141208-1. How do you force the update? Can I just copy the aswSnx.sys that is 8.0.1603.401 and transfer it over?
I’m the same boat on a few machines. They’re up to date on definitions, but the .SYS file remains the old 399 version and does not upgrade to 401. A spot check of several other machines showed they upgraded to 401.
Is there a way to force those few machines to 401 version? Can we copy the 401 SYS file over from another machine?
Same for me. I updated (SOA/Mirror) on test client and it is .399.
I installed Avast on a new Windows 8.1 machine (first one in our company) and ran into this issue. I took some time before I discovered it was the combination of Avast and KB3000850. Uninstalling KB3000850 restored the machine to normal behaviour.
On other machines the aswSnx.sys driver has been updated to the .401 version, but this doesn’t happen for a new install. On my Windows 8.1 system it is still version .399.
I can confirm that if you copy the aswsnx.sys from a client that got the 401 update, and overwrite it on a client that doesn’t want to upgrade, it works. You just need to copy in Safe Mode.
I’ll check it and will let you know.
We are seeing the same thing. The aswSnx.sys file is no longer auto updating. As the KB3000850 update is being applied to machines we are seeing the same problem as before. So we are manually updating the machines by going into safe mode.
Hi again, I am happy to inform you that we just released an updated version of the fix (the driver remains the same and so are versions). The original version of the fix has been causing some issues and was suspended for last few days.
Hi Drake.
Does that mean that the updated aswSnx driver version will again be 8.0.1603.401?
Thank you
Yes, the updated driver is exactly the same (8.0.1603.401).
Is this still distributed only via EmUpdate or it is also a part of the normal VPS update packages i.e. would an updated mirror server contain this version of the driver?
AFAIK via EmUpdate only.
Hi Drake,
Any plans to release it as a normal VPS / Program update?
EmUpdates are not solution for isolated / offline networks.
Cheers
It doesn’t seem so.
One problem with this appears to be with new computer setup… We need to be able to generate a new avast_managed.exe package that can install on a fully patched, new workstation as it is being setup…
I’m nervous about this as well. I’m about to setup my first new PC since the problem. The Windows 8.1 Pro system will have that KB installed prior to joining our domain, so when Avast installs, hopefully that emupdate runs immediately so the system doesn’t hang up.
Edit: A fresh install does not seem to update itself. It installs - runs the memory scan - then runs the standard VPS update. After that - nothing. The affected DLL file doesn’t change. If I force the emupdate to run, then the DLL was updated and I could restart.