Avast WEBforum
Business Products => Archive (Legacy) => Avast Business => Avast Endpoint Protection => Topic started by: REDACTED on November 19, 2014, 10:38:54 PM
-
We've been able to duplicate this on two machines.
Windows 8.1 Pro
After installing Optional update KB3000850, the machines hang up - they cannot run network scripts, nor run many programs on the system. Some work, but much doesn't.
You can't even restart or shutdown - it just hangs forever.
We noticed that on both systems, the Avast system tray icon never appeared. So we thought to remove Avast.
If you get into MSCONFIG and force the system into safe mode - remove Avast using the Clear program - the system starts working perfectly.
Something about that KB messes up Avast. Please make sure you avoid that KB for now until the Avast team has a chance to check it out.
-
Same issue here! We are using version 8.0.1603 (Endpoint protection plus) and after updating Windows yesterday we have several issues:
- PC unable to restart
- Internet Explorer does not start anymore
- Not able to debug in Visual Studio (issue with starting builds)
Please look at this ASAP!
EDIT
I've just uninstalled KB3000850 via the Control Panel (safe mode not even required) and after a reboot the system is back to normal. This seems like the preferred way since it does not require you to remove Avast (leaving your system unprotected).
-
We are having the exact same issues as well. Lots of machines took that update. It has not been very fun trying to go around and uninstall that update. Hopefully this is resolved quickly.
-
It is going on with all version of Avast.
https://forum.avast.com/index.php?topic=160717.0
-
Yup, just came here to mention this... But already found that it is going to be addressed tomorrow morning.
https://forum.avast.com/index.php?topic=160717.msg1153446#msg1153446
We have been able to simulate the problem in our lab and I think we fixed this issue. This Windows updates calls new memory related functions which are not fully compatible with avast. We'll prepare EmUpdate with the patched driver tomorrow morning (it means, all & new avast installations should be patched immediately, that's how it works).
Edit: And no need to remove avast as someone suggested, just remove the MS patch KB3000850 temporarily until avast can get patched.
-
Do I have to update soa server if the avast patch is ready?
-
Do I have to update soa server if the avast patch is ready?
No sign of the patch yet... I got the impression that this would be a streaming update and/or something the mirror should pickup automatically... Assuming your SOA server is healthy...
-
Looks like yet again the business product is lagging behind, hopefully someone from Avast can comment on when the patch will be available for the other versions of their software.
-
Is there a way to use SOA to remotely uninstall the Avast client?
-
So this hasn't been updated for the business product? I have been following the other thread and seems like there is a patch for the personal side but I have not seen an update yet for the business side unless I have missed it?
-
So this hasn't been updated for the business product? I have been following the other thread and seems like there is a patch for the personal side but I have not seen an update yet for the business side unless I have missed it?
I haven't seen anything either. :(
-
I am waiting for a fix for the business client too.
It sure would be nice if the Avast Team would respond and give an update!!
-
As am I. Avast team, can you confirm that the Business products will be getting the same fix coming soon?
-
+1 This is affecting us horribly too. Had to remove the update for most people... Please get to updating the business client, avast!
-
As am I. Avast team, can you confirm that the Business products will be getting the same fix coming soon?
(http://www.20kgroup.com/wp-content/uploads/2013/02/JiminyCricket.jpg)
-
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
-
-> https://forum.avast.com/index.php?topic=160717.msg1155451#msg1155451
-
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
-
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.
-
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).
-
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?
-
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 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).
-
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.
-
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.
-
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.
-
Hi, I'm trying to figure this out, it seems I have the wrong version of the file : 8.0.1603.399.
Why isn't being update to .401 ?
I'm having all sorts of issues.
-
I am having the same problem where Avast Endpoint is not updating the .sys to .401. Recently, I have been revamping out with SCCM and have been testing with a vanilla windows 8.1 x64 image (from iso and no windows updates applied). I am finding that after I got SCCM to finally deploy Avast's exe to the device collection, I cannot even log on for the first time because the computer is stuck at Loading Personal settings (going on 4 hours now). Besides my annoyance with no MSI installers, not being able to include this "Emergency" update in a packaged installer is a joke. So now I am back to having to manually install Avast on each newly imaged computer just so i can run the emupdate and hopeully get .401. I don't see why this has to be so difficult.
-
@ jae1378
It would be a good idea if you could open a new topic here https://forum.avast.com/index.php?board=33.0 and making a reference to this thread ( topic ). You will have greater chances to an answer from someone who knows Avast Endpoint.