MS KB3000850

[REDACTED]

How about finally update the business edition to a recent version (10)? I can not understand that the business edition is lagging behind at least two versions! Of course it is a bigger problem to fix this old stuff if such incompatibility issues occur with a modern OS.

Guys: this is urgent!

If this is not resolved quickly, I am forced to switch to another product in our company - whether I like it or not!

BR
Jobdan

[Asyn]

-> https://forum.avast.com/index.php?topic=160717.msg1155451#msg1155451

[REDACTED]

Thanks. I saw this already - because of this posting i wrote my comment above.

Another question for me that is unresolved: why is the mentioned posting in the Free/Pro section? Why is no information in the business section of this forum? WHEN will the fix be released? WHEN? Just to remember: the business edition is the one customers are paying for and this edition is rolled out to the whole company - no home users and private computers. Our guys have to work and i have to explain why we switched to avast as AV solution. Not funny.

BR
Jobdan

[REDACTED]

How about finally update the business edition to a recent version (10)? I can not understand that the business edition is lagging behind at least two versions!

Let me say;  I don't like the answer I'm about to give...  But as a long time personal user of Avast! Free edition who also moved a company to the business protection product my experiences have required me to come to terms with the following fact:

They see way more value in the millions of users acting as remote data collectors with the free edition and probably make more money selling millions of copies of the personal pro edition than they do selling thousands of copies of the business edition.  Most products that have a business edition are priced such that it is the flagship offering and the real bread winner of the lineup.  This is just not the case with the Avast! ecosystem...

It's a shame because this second class citizen stuff is going to drive a happy one time zealous proponent of Avast! over to something like Vipre, ESET, or *shudder* Webroot...  What is unfortunate is that the same thing that makes it great, also limits its success.

[drake127]

We just released an Emergency Update fix for the latest business edition (8.0.1603). The fixed version of aswSnx is 8.0.1603.401. To force apply the fix, it should be enough to either log out + log in or to execute avast! Emergency Update scheduled task from Task Scheduler).

[REDACTED]

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...

[REDACTED]

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.

[REDACTED]

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?

[drake127]

Do I just need to look at the aswSnx.sys properties and see if it is 8.0.1603.401?

Yes, that's enough.

[REDACTED]

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?

[REDACTED]

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?

[REDACTED]

Same for me.  I updated (SOA/Mirror) on test client and it is .399. 

[Theo@IC]

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.

[REDACTED]

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.

[drake127]

I'll check it and will let you know.