My PC with Windows 10 Pro x64 today after Avast upgrade crashed. Only safe boot with option turn off antimalware was a way to run the system and uninstall Avast. After Avast uninstall was Windows OK yet.
Exactly. Comodo is more important to the security of your System than Avast is. Avast protects people from downloading dodgy files & prevents infections. Comodo stops malicious programs from even accessing your system in the first place. Also, if you have a firewall & you are a light user just browsing or playing games. Windows 10 security shield will do just fine!
But, I like Avast because it screen’s websites for you for malicious activity. Even genuine sites can get hacked & malicious code put on it.
I have the same problem on two completely different machines. On the third I tried not to install the update yet.
W10 up to date, Comodo Firewall Free, Malwarebytes Free (which is always off), and the old version of Avast.
After updating, everything broke down, no apps can start, can’t be removed from Control Panel and so on.
I finally removed it by going in Safe Mode and using the utility, tried to fresh install with online and offline package, the same problem is here.
Removing Comodo Firewall doesn’t help either, and don’t want to, since the firewall itself is better and more advance than what W10 offers.
Installing fewer components - if the Behavior shield is the problem - is not a solution.
That could be an useful feature for protecting our PCs, so leaving it out doesn’t do any good.
We have been unable to induce this problem so far. Could someone please specify the exact version of Comodo FW and also the exact configuration? Also there are mixed messages so far in this thread. Somebody got the problem resolved by updating Comodo to v10, somebody just turned off HIPS, somebody has the problem even without Comodo FW. We tried all these scenarios with new Avast and could not reproduce.
My wife’s Dell with Windows 10, 64 bit is another victim of the update, and is now a brick.
Her update was done automatically, and before I knew there was an issue I manually ran the update on my own machine, but tried to cancel it after Googling. Avast now wants to reboot, and I fear that my laptop will also fall victim to this unfortunate upgrade.
Seeing as the issue surfaced on February 7th across many devices and configurations, I think it would have been wise to have paused automatic updates until the issue/s had been resolved.
Is anyone having trouble running Wordperfect after updating the AVAST free version? I know not many people run WP. I still use WP suite 7 from the 1990s because it prepares simple word documents.
Thank you.
My 64 bit Dell with Window 10 has no problems with this latest update.Maybe offering more information about her system will lead to a fix.On your system, it’s impossible to tell if you’ll have a problem or not since you attempted to halt the installation.see if the instructions here will help you once you’ve rebooted your system: http://goo.gl/VLXdeThey should also help you resolve your wife’s computer.
I had Comodo 8.2 and 8.4 on my systems, alongside with Malwarebytes Free (which doesn’t have any shields active), on W10 x64 up-to-date. After updating to this new version, both systems broke down and everything went wrong. Avast and Comodo had all shields active - including HIPS for the firewall.
But now I uninstalled both of them, after a few days of staying with Windows Defender and Comodo, then installed Comodo v.10 with all shields enabled and after that Avast - with Behavior shield also. Now it works. I don’t know if it’s something from their settings or the new version of Comodo, but at least on one system seems to be fine now. I’ll try the same on the other one.
[i]
Not related to Avast, but one problem with Comodo was that while having version 8.2/8.4, when checking for updates it wouldn’t find anything new, so it was “up-to-date”. Except it was not. If someone is having issues with it and now with Avast, it should be manually uninstalled and reinstalled from their website. [/i]