Avast WEBforum
Business Products => Archive (Legacy) => Avast Business => Avast Endpoint Protection => Topic started by: Jereck on December 14, 2015, 07:20:29 PM
-
I have upgraded all my client computers (Windows 7) to version 8.0.1606 and I have now and error in Windows' Action Center on these computers.
I tried to reboot a 2nd time, but that did not help.
Any clues ?
-
I've got this too, plus it has turned the consoles on my SBS2011 installations into a sea of red. The clients are reporting no antivirus installed...BUT it does look to be working.....
-
Same here.
On every W7, W8 PC I tried.
New installation from exe file is OK (after uninstallation and avastclear), but when you upgrade from old version in program menu -> error in security center.
Really need solution for this one, 350 PCs waiting for update. :(
No responses from my reseller for this problem.
-
Ditto, having same issue for those that have updated.
-
I just want to add something to hopefully help troubleshoot. If you do a UPGRADE you get the security center alert. If you do a fresh install you do not. At least in my experience.
-Allan
-
I posted about this too. Also, on my workstation, after the update, the password to access the UI no longer works.
-
I posted about this too. Also, on my workstation, after the update, the password to access the UI no longer works.
No such problem here.
-
I have absolutely the same problem as Jereck on all Win7pro PCs and Notebooks too. Windows Security center doesn't recognize neither the avast eps Antivirus program nor the protection for mal- and spyware. The only solution found was to deactivate the corresponding functions in Windows security center.
-
The problem with v 8.0.1606 becomes significant now! As member of a TeamViewer Group, the Win7prof clients will be reported as unsafe! I think avast must issue a patch immediately or at least a guide to solve the problem.
-
At least for me (I have 5 clients with win7prof only) I was able to solve the problem with the security center.
1. uninstall Avast eps
2. restart computer
3. download from Avast website the newest setup_av_eps.exe and install!
4. enter your licence-file
5. check security center of Windows and activate Virus- and Mal/Spyware monitoring (avast will report that it does the jobs) :)
-
Same problem here.
I've tried reinstalling invidual clients and the console but it still shows as a problem in the Windows Action Center.
Any other ideas?
EDIT: Clearing Avast with avastclear.exe and reinstalling did work. I'd rather not have to do this on all our machines though.
-
Same here. Any solutions?
-
Same issue here. So far the only solution we found is an uninstall and reinstall of Avast to get rid of the error.
1) Uninstall Avast client
2) Reboot computer
3) Deploy Avast from the server console (which is update to the latest version)
4) Reboot
-
I also had the warning in system center that my system did not have anti-virus protection
after upgrading Avast endpoint protection.
I looked at Microsoft's knowledge base, and they claimed this was a known issue with Windows 7 and
Windows 2008 - not specifically with Avast, but in general.. you may want to go take a look at this:
https://support.microsoft.com/en-us/kb/2482947
( System health report doesn't detect antivirus programs in Windows 7 )
There is a US hotfix - I'm not sure about other countries, but after reading the description and obtaining
the hotfix, I applied and rebooted and it resolved the problem without uninstalling and re-installing Avast...
in my case, my avast installation was the result of an update from within the program, and not a fresh
install.
Windows action center no longer reports that my system is not secured.
-
for me the hotfix didn't resolve the problem.
-
Having the same issue on all Win 7 PCs. This release ALSO causes a BSOD on all Win 8.1 PCs : https://forum.avast.com/index.php?topic=180767.0
-
The suggested hotfix is from 2011. I don't think that is related to this problem.
-
Same issue here. So far the only solution we found is an uninstall and reinstall of Avast to get rid of the error.
1) Uninstall Avast client
2) Reboot computer
3) Deploy Avast from the server console (which is update to the latest version)
4) Reboot
Many thanks. Same here also.
Just to add, the official uninstaller is here (uninstalling through add / remove programs was not sufficient in our case): https://www.avast.com/uninstall-utility.
-
Solved for me, thanks!
-
We are seeing this issue with Win 7 and 8.1 units. However, I am also posting in another group (Windows 8.1 Blue Screens), because ever since we upgraded to this newest version, we have had machine randomly BSOD with the Critical Structure Corruption message. So be prepared if you haven't started seeing this issue already. Most of problems are occurring on Win 8.1, but just had a call from a Win 7 user. Kind of wondering if anyone from Avast is even listening or paying any attention to these post.
-
ok
uninstall, reboot, safe mode, avastclear, redeploy.
I can do this on one pc but we have hundreds of PC, I can not believe you can't find another solution :( :(
-
Is there still no solution for this problem?
Avast We are waiting. The work around is not a solution for a company wide deployment.
First we have to wait for 3 months, for a windows 10 client, and now again waiting to long for an update.
Frustrated!
-
So...
In windows 8.1 BSOD topic (https://forum.avast.com/index.php?topic=180767.75 (https://forum.avast.com/index.php?topic=180767.75)). I asked Che Johnson if this problem will be solved in the new 8.0.1607 version too and he gave me YES, BUT IT WASN'T.
I was trying to migrate from 8.0.1603 to 8.0.1607 because of this bug don't let me go for 8.0.1606 and here we go.
Our users are reporting no antivirus alerts from security center with Avast in green status all shields running and I must disable antivirus related alerts or cleanly reinstall AVAST.
I'm tired, from all this crap Avast brought on us for the last two years of using. This is just last nail to the coffin and I will not recommend extension after our licence runs out next year.
IT-KAV
-
Well, the problem is back again within 8.0.1609 (updated from 8.0.1608 using SOA console). I'm not relishing visiting each workstation to remove and re-install manually.
Anyone else finding the same?
Kind Regards, Stephen