Avast WEBforum
Business Products => Avast Business => Cloud Management Console & Clients => Topic started by: REDACTED on March 05, 2017, 08:15:16 AM
-
Hello group,
We have over 100 businesses that we manage the IT for, and 400+ computers with Avast Business Installed. On 3/2/2017 many of these sites received the 17.2.2517 update and have been experiencing intermittent issues while logging into Active Directory. About 5% of the time a user logs in they receive an error that the profile could not be loaded from the server and the computer is using a Temp Profile. The normal cause of this type of error is a network related problem, or an issue with Active Directory, but I can assure neither are causing this issue.
The Windows errors we're seeing are: Events 1511, 1515, 1502 & 1508
This only started after these sites were updated to 17.2.2517, there are no other network issues, and these sites are totally independent of each other...all separate businesses with completely different software, servers and infrastructure. The only thing they all have in common is Avast Business 17.2.2517
Has anyone else experienced this issue? Is there a support number or process for me to contact support to help with this issue.
Thanks,
Jason
-
Some people (https://forum.avast.com/index.php?topic=198096.0) have reported that rebooting fixes this issue. I am getting this on my Server and will be scheduling a reboot to see if it resolves.
Can you verify you're getting the issue on PCs that have been rebooted since receiving the update?
-
I cannot constantly reproduce the issue, so I'm not sure if rebooting a single time fixes it. I feel that we've seen the issue after multiple reboots, but can't confirm because we did not know the cause of the Temp profile issue until now. I'll reboot some of the affected computers in the morning and report back.
Thanks!
-
Hi guys, it has been reported (by Mac) to the devs already. Cheers.
-
Hi we have this as well. This is a CRITICAL issue. We have Avast business installed on over 200 client computers, and many servers too, and they are dropping like flies. Some of them aren't getting any results by restarting.
Not sure how serious you guys are taking this, but this hasn't been fixed in 3-5 days already, and I can't imagine a worse issue than this short of Avast sending out the user's passwords out to hackers.
If this isn't sorted yesterday, you are going to lose a LOT of customers
-
I've had to completely remove Avast from our RDS session hosts to get around this issue. When trying to repair their temp profiles, for every user "C:\Users\Username\AppData\Roaming\AVAST Software\Avast\Cache" was completely locked by the client. Rebooting didn't make any difference.
-
We don't use roaming profiles, but I've had a couple computers experience the same issue with local profiles. I've had people reboot their computers, which didn't fix the issue when performed by them.
I ran a chkdsk /r prior to looking at the forum and after these completed, their desktop items were restored and the error went away. I'm not sure if the chkdsk fixed anything (it didn't report that it found, repaired, deleted anything) or if it just happened to like the reboot that specific time.
-
This also affecting some of our machines - potentially disabling the BEHAVIOR module in the new client and rebooting a couple of times will fix (did for one machine I tested on)
-
I must be really unlucky... systems on my network experience this local profile problem, Exclusions not working during scans, licenses not being applied properly, a slew of false positives (Malwarebytes installer? Really?), files getting deleted instead of being quarantined, inability to add systems to existing tasks in console, inability to even rename tasks in console.... the list goes on. Venting here, sorry, but I am not a satisfied customer at all.
-
We have about 200 systems at one client running avast, This update is causing the Profile sync issue that everyone is stating. It looks to be causing locking the user and admins out of the folder structure stored in the roaming folder of the user profile. Right now I have Multiple systems experiencing the issue.
-
See reply #3
-
Still waiting for a fix. Can we have some kind of feedback? This is a huge issue.
I would imagine that 90% of people experiencing it haven't even figured out it is avast yet, so you are only seeing a small proportion of the affected users
-
As a temporary Workaround for the Roaming-Profiles-Issue you can deactivate the Self-Defense Module....
Regards
-
It has crashed a bunch of different types of units around our district BSD and all.
-
Micro-update is being tested. ETA for go-public is 8 to 12 hours. We are in final testing phase. In urgency please contact our support they will provide you with the file and instructions.
Thank you all for your valuable reports and tips you have provided. Really appreciate it.
-
Micro-update is being tested. ETA for go-public is 8 to 12 hours. We are in final testing phase. In urgency please contact our support they will provide you with the file and instructions.
Thanks @misak
Can you confirm if micro-updates are still deployed if Automatic Program Updates have been disabled in the cloud console?
-
misak - what is the new version number we should be looking for?
-
Hello,
today we released a micro update for the self defense which should also fix the issue with roaming profiles.
Just give it some time to download or you can force it by a reboot or by executing AvastEmUpdate.exe. But when the update is applied a reboot is needed to take effect.
Thanks
Petr
-
I am currently showing Program Version 17.2.2517 (build 17.2.3419.0).
Is this the new build version that contains the fix?
-
I am currently showing Program Version 17.2.2517 (build 17.2.3419.0).
Is this the new build version that contains the fix?
It's not a new program update, just a micro update for current version.
Petr
-
If version number doesn't change, how do we know if reboot is needed? Will it pop-up a reboot window prompt on each computer?
I am currently showing Program Version 17.2.2517 (build 17.2.3419.0).
Is this the new build version that contains the fix?
It's not a new program update, just a micro update for current version.
Petr
-
Thank you! Yes, this is exactly why I was asking. I realize the Program Version will remain the same, but wouldn't the build number change?
If version number doesn't change, how do we know if reboot is needed? Will it pop-up a reboot window prompt on each computer?
I am currently showing Program Version 17.2.2517 (build 17.2.3419.0).
Is this the new build version that contains the fix?
It's not a new program update, just a micro update for current version.
Petr
-
After micro-update and PC restart my avast! Business version is: 17.2.2517 (build 17.2.3419.59)
Thanks for the update!
-
Awesome! Thanks for the follow up info.
-
@misak - is there another micro-update released recently? I had a client with a higher number than the .59
-
Now there is another micro-update that ends in .64. Any ideas on what this stuff is fixing?
-
Today is Monday. All faculty booting computers and getting a BSOD. New client 17.2.2517 has been installed on close to 2000
computers. for my school district. computers getting this all over the District. I have disconnected my 2 bench test computers running Windows 7. Boot into safe mode and removed Avast Business Client 17.2.2517.
Restarted computers 6 times, with no error's. Looks like big bug in version 17.2.2517. Please help how am I going to fix close to 2000 computers.
-
Same here mine are Dell's with the micro update .64
-
I performed a clean install of the latest version which is the .64 on 2 test computers. Restarted 6 times, no BSOD.
-
Today is Monday. All faculty booting computers and getting a BSOD. New client 17.2.2517 has been installed on close to 2000
computers. for my school district. computers getting this all over the District. I have disconnected my 2 bench test computers running Windows 7. Boot into safe mode and removed Avast Business Client 17.2.2517.
Restarted computers 6 times, with no error's. Looks like big bug in version 17.2.2517. Please help how am I going to fix close to 2000 computers.
Hi, see: https://forum.avast.com/index.php?topic=199156.msg1379196#msg1379196
-
I have run the micro update and restarted numerous times but I still have the issue.
Is something supposed to happen when you run the micro update? Nothing happens for me. If I monitor processes in task manager, it appears to run for a second or two then closes. Is this normal?
-
Monday morning I came into work and one of our main servers had gone down and multiple desktops were blue screening every few minutes. Since removing avast it seems to of stopped the problem but these computers are now unprotected.
-
Check you have rebooted then checked you have at least minimum 170320-1 virus definition update, and program build 17.2.3419.64 or later
This combination fixes a number of known issues with the initial version 17.2.2517 release