Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: REDACTED on February 07, 2017, 06:11:27 PM
-
This morning AVAST upgraded to a new version. It rebooted my computer after the upgrade. When my computer came back up, my applications (except for browser) don't run. I get lots of these errors: Application Error - The application was unable to start correctly (0xc00000e5). Click OK to close the application. I cannot uninstall AVAST - uninstall does not run (I can click on Uninstall and it asks me if it's OK to do the uninstall, then nothing happens.) I figured if I uninstalled I could reinstall and that might fix the problem.
Help!
Doug Roberts
-
Uninstall Utility >> https://www.avast.com/uninstall-utility
-
- Which Avast..? (Free/Pro/IS/Premier)
- OS..? (32/64 Bit..? - which SP/Build..?)
- Other security related software installed..?
-
Already rebooted a few times ?
Already tried a repair of avast ?
-
Uninstall Utility >> https://www.avast.com/uninstall-utility
Hi Pondus -
That AvastClear worked. I'm back in normal Windows mode and my apps run. Now I'm going to reinstall Avast.
I am using the free version, Windows 10, 64 bit.
Doug
-
Uninstall Utility >> https://www.avast.com/uninstall-utility
Hi Pondus -
That AvastClear worked. I'm back in normal Windows mode and my apps run. Now I'm going to reinstall Avast.
I am using the free version, Windows 10, 64 bit.
Doug
I reinstalled Avast and I've got the same problem back of my apps not running. Excel.exe does it. Things went wrong during the Avast Startup Scan.
Going now again to uninstall using AvastClear in safe mode.
My other piece of security software is Comodo Firewall. I thought that was necessary for complete security.
Doug
-
Hi -
I'm looking for a suggestion on what to do now that I have successfully uninstalled Avast a second time. I now have caused this problem of no apps running to occur two times, each time followed by uninstalling Avast in safe mode with AvastClear.
I've been using Avast with no problems for a very long time. Is it a problem that I run Comodo Firewall? (I've been running Comodo Firewall without issue for just as long as I've been running Avast.) I thought Comodo Firewall provided coverage that was not covered by Avast.
Currently I'm running with no security.
Thanks for any help. That AvastClear was a lifesaver when uninstall did not work in normal mode.
Doug
-
Remove Comodo completely.
There is no need for it as Windows already has firewall that does the job.
Next to that, Comodo isn't just a plain firewall anymore and can cause conflicts with other security software.
-
Does it work if you remove Comodo..?
-
Like I said in the other thread, I have the same problem on both my PCs and I am also running Comodo. So there might be a lead there. Might as well be coincidence though. Three is not exactly a big sample size.
-
Remove Comodo completely.
There is no need for it as Windows already has firewall that does the job.
Next to that, Comodo isn't just a plain firewall anymore and can cause conflicts with other security software.
I'm doing that removal now. How do I turn on the Windows Firewall?
Thanks for the quick reply.
Doug
-
Windows 10 should turn on the build in firewall automatically if there is no other firewall installed.
-
Same problem. Windows 10. All kinds of application errors. I use Comodo as well. In the past there was no conflict. Something in Avast changed, apparently, that has created a conflict.
-
Windows 10 should turn on the build in firewall automatically if there is no other firewall installed.
So I've got Windows Firewall turned on. It already was turned on. I'm also getting a message from Windows that Windows Defender is not turned on. Do I need that?
The installation of Avast is now complete and the startup scan is complete. Applications run without error.
Thank you. Please let me know about Windows Defender.
Much appreciated.
Doug
-
In Windows 10 Defender is automatically turned of when another av is installed.
-
In Windows 10 Defender is automatically turned of when another av is installed.
What is an "av"? If I'm using Avast, do I need Windows Defender?
Thank you Eddy.
Doug
-
In Windows 10 Defender is automatically turned of when another av is installed.
Question: Why did Firefox and PaleMoon browsers work when all other executables did not?
Thanks.
Doug
-
What is an "av"?
AV = Anti Virus
do I need Windows Defender?
It is integrated in the OS and can not be removed, only disabled / turned off
-
do I need Windows Defender?
It is integrated in the OS and can not be removed, only disabled / turned off
OK, thanks for the info on Windows Defender being integrated into the operating system. Do I need Windows Defender?
Separate question: Why did the browsers FireFox and Pale Moon keep working when all the other applications (.EXEs) would not work. If they had not then I would not have been able to contact you folks.
Thanks for the info.
Doug
-
Defender is just a basic av almost entirely relying on signature detections.
You sure don't need it if you have avast ;)
About the browsers, I have to guess as I can't see your system and what is going on etc.
My guess is that the other applications are using Windows files (or parts of it) that the browsers don't.
If they had not then I would not have been able to contact you folks.
Ofcourse you could have come here.
You are not the only one in the world with a computer and Internet access. (Neighbors, friends, family, library, schools etc) ;)
-
Remove Comodo completely.
There is no need for it as Windows already has firewall that does the job.
Next to that, Comodo isn't just a plain firewall anymore and can cause conflicts with other security software.
I'm doing that removal now. How do I turn on the Windows Firewall?
Thanks for the quick reply.
Doug
There is a 'Windows Firewall' panel on the 'Control Panel' where you can check status / turn on / off etc.
-
I have had exactly the same problem using Windows 10 x64 version (uptodate) on a DELL Latitude 3550. I am using Comodo firewall.
The problem is caused by the 'Behaviour Component'. With this switched on it seems to prevent any 32bit software from running.
You are right, you can't uninstall, can't run System Restore, or disable Avast.
My workround is as follows.
1. Start Windows in Safe Mode.
2. Set the 'Avast Antivirus' service to Manual.
3. Restart normally.
4. Go to Control Panel/Programs & Features
5. Select 'Avast Antivirus' and choose 'Change' then 'Modify'.
6. Unselect the 'Behaviour Shield' component.
7. Say 'NO' to restart now.
8. Closedown and restart in Safe Mode.
9. Set the 'Avast Antivirus' service to 'Automatic Start'. (Do NOT start it.)
10. Restart normally.
No requirement to uninstall Comodo (unless you want to).
-
Another one here with Windows 10 64B and Comodo Firewall with HIPS and Viruscope disabled.
The workaround by TFC works. Thanks :)
-
Damn, your workaround came too late for me. Uninstalling Comodo however did solve the problem too.
-
TFC's "workaround" is a really bad idea as the behavior shield helps protecting against a infection by ransomware.
-
Pardon me! And your suggestion is?
-
Same problem here. Windows 10 Home 64 bit. Yesterday Avast installed the update automatically. Before reboot Avast interface showed a blank white window. Upon reboot, I got lots of errors: Application Error - The application was unable to start correctly (0xc00000e5), referred to AvastUI.exe as well.
I use Comodo too. I have always used both Avast and Comodo in the past, never had a conflict.
I couldn't uninstall Avast. Clicking on the control panel link to display installed applications list had no effect.
I had to reboot Windows in Safe Mode, uninstalled Avast from there and rebooted in normal mode. Then I tried to reinstall Avast (form the offline setup), but I got the very same issue.
Here is what I've done to solve:
1) Rebooted Windows in safe mode
2) Executed "Avast Uninstall Utility" from desktop (really a life saver)
3) Rebooted in normal mode
4) Installed Avast from the on-line setup this time.
Never disabled Comodo in the meanwhile.
Something has been changed in Avast for sure. I hope better compatibility with Comodo will be restored in the future...
Now I have both Avast and Comodo up and running again.
Hope this helps, because yesterday I was afraid I could not solve this issue.
-
On Windows 10 there is no need to have any third party software firewall.
As I said before, Comodo is not just a firewall anymore and that is causing the conflict.
Remove Comodo and use the Windows firewall (or use a hardware firewall)
https://blog.kaspersky.com/multiple-antivirus-programs-bad-idea/2670/
-
Thank you for your advice.
-
Firewalls and anti-virus security software are two different creatures -- and generally it's a design flaw when they don't play nicely with each other simply because they are produced by different companies. Avast offers its own firewall -- presumably because it believes its design is better than the default built-in Windows firewall, and users may find it more attractive. The same is true of the Comodo firewall. If one uses Comodo as a firewall and doesn't enable its AV features, and uses Avast as an AV and doesn't enable its firewall features, it is not too much to ask that both companies work to assure their products are compatible with each other. Historically, moreover, Avast AV and Comodo firewall have been compatible, and when they have temporarily failed to be in the past, whichever update caused the problem was subsequently modified. I don't pretend this challenge is easy for companies to achieve, but it is a reasonable user expectation.
-
I had the same problem (and with other AV as well) and the following steps solved my issue. I'm also using Comodo Firewall and that sneaky piece of software forgot to tell me that the 8.4.X version is not the newest by far. That would be version 10.
1 - Uninstall Avast the regular way. If it's not possible due to application running blocking, skip to step 2.
2 - Boot into safe mode and run the official Uninstaller Utility: https://www.avast.com/hu-hu/uninstall-utility
3 - Reboot your PC and the system should work fine.
4 - Uninstall Comodo Firewall.
5 - After the reboot, install Avast using the latest online installer downloaded from avast.com.
6 - Restart your PC and install back Comodo Firewall using the latest version available from the website. Don't be confused by the same name of the .exe file. The old installer had the same name (but why?).
7 - With the new Comodo Firewall, the newest Avast should work just fine.
Edit: If for some reason you can't uninstall Avast the way I described above, run a system restore to go back to a system state when Avast wasn't updated. Then uninstall it with steps 1 and 2 before it updates.
-
glerikud.strawhat . . . That's very interesting. I had reinstalled Comodo earlier, but disabled Comodo's HIPS and Viruscope features as per guidance in earlier posts in this thread. I left all Avast components active, including Behavior Shield. That works. Your post, however, implies that with Comodo 10 (yes, mine updated as well from an earlier version when I downloaded and installed it again) is compatible with the updated Avast AV even with all functions active (that is, with HIPS and Viruscope active). But I wonder if you've checked your Comodo configuration to verify if that is correct? Do you have HIPS and Viruscope enabled? Please advise.
-
CFW v.10 does "not" work on a Win10 running avast.
Comodo does "not" allow the user the choice to install CFW v.8.2 anymore.
It's now the full blown CIS or nothing.
My suggestion is to use Windows Firewall with outbound protection turned "on" (if you want HIPS).
-
I have had exactly the same problem using Windows 10 x64 version (uptodate) on a DELL Latitude 3550. I am using Comodo firewall.
The problem is caused by the 'Behaviour Component'. With this switched on it seems to prevent any 32bit software from running.
You are right, you can't uninstall, can't run System Restore, or disable Avast.
My workround is as follows.
1. Start Windows in Safe Mode.
2. Set the 'Avast Antivirus' service to Manual.
3. Restart normally.
4. Go to Control Panel/Programs & Features
5. Select 'Avast Antivirus' and choose 'Change' then 'Modify'.
6. Unselect the 'Behaviour Shield' component.
7. Say 'NO' to restart now.
8. Closedown and restart in Safe Mode.
9. Set the 'Avast Antivirus' service to 'Automatic Start'. (Do NOT start it.)
10. Restart normally.
No requirement to uninstall Comodo (unless you want to).
your solution is really good, below is what i did
1. jump straight into safemode (win key + r, then msconfig, then boot, then, select safe boot, then apply,)
2. complete shutdown
3. reboot computer
4. then once logged into safemode access control panel and select avast then click change.
5. when avast opened clicked change then unselect behavior shield. then finalize the change and exit out of the program after the progress bar for the change went away.
6.then re-did step 1 doing (win key + r, then msconfig, then boot, then, unselect safe boot, then apply,)
7. rebooted computer after full shut down. and no issues
*note: i did not touch commodo firewall, auto sandbox, hips, or viruscope so i assume the issue is in avast and it has to do with behavior shield. also i tried toggling commodo and avast on and off in many combinations and this is the only one that let me keep both.
-
The problem is most likely caused by a conflict between the newly added Behavior Shield and Comodo. We have experienced conflicts with Comodo before in AVG too. We are now looking into the problem and hopefully can come up with a solution that will allow CFW and Avast Behavior Shield run simultaneously. Until then it is either to disable/uninstall CFW or turn off Behavior Shield I'm afraid :( As stated in the earlier posts, the conflict will most likely be in Comodo HIPS and not in the firewall part, so alternatively, you could try to turn off only Comodo HIPS.
-
I use comodo & I had to remove avast! This isn't the first time this has happened & if you are aware of conflicts with comodo. I think you should test before releasing. We the users ain't your testing platform.
The only way I could get back into the 4 systems updated & locked me out was rebooting twice when I windows loading icon showed up. Which instigated the repair. Selected advanced. Then startup & restarted & selected safe boot. I then uninstalled avast & rebooted to a perfectly working system!
Also, fix your verification system. 11 times I had to try before it accepting the letters!
-
Well, I had the same problem. HOWEVER, I am NOT running Comodo Firewall. I have not yet had a chance to try the workarounds suggested here, but will this evening. In any case, it doesn't seem to necessarily be an issue between Comodo and Avast, at least not just that. I am running Win10, 64-bit, with Windows Firewall. I'm hoping that Avast finds the general issue (not just one that involves Comodo) and puts out a fix soon...
-
Well the 4 systems that updated to this version all had same problem. Startup items just couldn't execute. remove programs in control panel wouldn't open & nothing would actually respond the way it should. It even blocked me from rebooting into safe mode from within windows. You know msconfig & select safe boot or just disable programs from start up. Didn't work, I applied, click ok. Select restart & my systems either crashed or just ignored the settings I just made.
But I would suggest booting up & hit restart when you see win 10 icon loading twice. The 3rd boot should go into recovery. Select advanced & you want to go into start up options. It will say to reboot & hit Number 4 for safe boot. It will reboot & will boot into safe mode. This was the only method that would let me uninstall avast!
I think Avast should at least test these new updates. Even open up a testing pool of users who are willing to test avast's major updates for free subscriptions or other benefits. I don't think this was fully tested considering the amount of problems & my 3 kids computers, my nan & granddads. My mothers, Uncles & my brother's computers all had to do what I said above to get them working again this morning. Been at it since 8am sorting them out! Now imagine their problem if they didn't have a technically minded person like me who is very experienced with pc's & alike. Furthermore, how would avast fix these problems when their systems not only do not boot up correctly. But software like avast doesn't even boot?
I think you owe people an apology because I can be sure that many people who are not technically minded or have anyone at hand to fix it will have lost their use of their laptop or computer & will probably end up paying someone to fix it who will just be as thick & format & re install their windows!
-
@Bolt1955 Sorry for that, I left those out of my previous post. I don't use the HIPS and VirusScope features of Comodo, so I disable them instantly after install.
-
I had the same problem. After avast latest update every application crashed!! When i uninstalled comodo firewall everything worked just fine!
-
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.
-
Remove Comodo completely.
There is no need for it as Windows already has firewall that does the job.
Next to that, Comodo isn't just a plain firewall anymore and can cause conflicts with other security software.
Why remove comodo when avast is to blame? I had avast and comodo running fine until avast released the new versionand forced me to upgrade!!
-
Remove Comodo completely.
There is no need for it as Windows already has firewall that does the job.
Next to that, Comodo isn't just a plain firewall anymore and can cause conflicts with other security software.
Why remove comodo when avast is to blame? I had avast and comodo running fine until avast released the new versionand forced me to upgrade!!
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.
Such a let down by Avast!
-
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.
...now I'm stuck with Windows Defender.
-
Hello,
I am not using the license for almost a year. I noticed now that they charged me by automatically renewal. Is there any way how to get my money back?
-
Hello,
I am not using the license for almost a year. I noticed now that they charged me by automatically renewal. Is there any way how to get my money back?
-> https://www.avast.com/faq.php?article=AVKB24#artTitle (Orders and Renewals)
-
Remove Comodo completely.
There is no need for it as Windows already has firewall that does the job.
Next to that, Comodo isn't just a plain firewall anymore and can cause conflicts with other security software.
Why remove comodo when avast is to blame? I had avast and comodo running fine until avast released the new versionand forced me to upgrade!!
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.
Such a let down by Avast!
Sounds like a reply from a Comodo fan. I let go of the dragon a long time ago. :)
-
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.
-
Hello,
I also encounter problems with this version of avast.
Application Error - The application was unable to start correctly (0xc00000e5), referred to AvastUI.exe as well.
Comodo firewall Version 8.4.0.516526 of September 2016
And this under WIndows 10 64 family and under Windows 10 64 Pro
With HIPS active or not in comodo.
And as it is impossible to use windows I go through a restore point.
Thanks translate google
A+
-
Hello,
I also encounter problems with this version of avast.
Application Error - The application was unable to start correctly (0xc00000e5), referred to AvastUI.exe as well.
Comodo firewall Version 8.4.0.516526 of September 2016
And this under WIndows 10 64 family and under Windows 10 64 Pro
With HIPS active or not in comodo.
And as it is impossible to use windows I go through a restore point.
Thanks translate google
A+
Have you tried updating to the latest version of Comodo ???
-
Version 8.4.0.516526 of September 2016 is the latest version of comodo firewall
http://cdn.download.comodo.com/cis/download/installs/updates/release/inis_4080/release_notes.html
Version 10 is an internet security version so with an antivirus
A+
-
Version 8.4.0.516526 of September 2016 is the latest version of comodo firewall
http://cdn.download.comodo.com/cis/download/installs/updates/release/inis_4080/release_notes.html (http://cdn.download.comodo.com/cis/download/installs/updates/release/inis_4080/release_notes.html)
Version 10 is an internet security version so with an antivirus
A+
You have the option to not install the Antivirus portion. Use a custom install.
-
For Comodo this means installing the firewall version
So the 8 as well as the 10 and with the same driver and without risk.
-
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.
-
No, it is not wise as you will not receive the updates that contain fixes that way.
-
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 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.
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/VLXde (http://goo.gl/VLXde)They should also help you resolve your wife's computer.
-
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/VLXde (http://goo.gl/VLXde)They should also help you resolve your wife's computer.[/font][/size]
Thanks Bob.
Thing is, I'm unable to boot her Dell into safe mode or open anything. It boots up but is dead in the water.
I'll sort it somehow, but getting to system restore is proving impossible at the moment, even on boot-up.
-
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/VLXde (http://goo.gl/VLXde)They should also help you resolve your wife's computer.
Thanks Bob.
Thing is, I'm unable to boot her Dell into safe mode or open anything. It boots up but is dead in the water.
I'll sort it somehow, but getting to system restore is proving impossible at the moment, even on boot-up.
Do you have an emergency boot disk ?
See if this helps you get to safemode: http://www.digitalcitizen.life/4-ways-boot-safe-mode-windows-10
-
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.
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.
- 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.
-
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.
Sure. Comodo version: 8.4.0.5165 - when I click update, says Up to date.
Firewall - safe mode.
Auto sandbox - disabled.
HIPS - safe mode / disabled - did not change.
Virusscope - enabled (only for sandboxed apps)
Avast: 17.1.2286
Windows 10, Pro, 64 bit, up to date
Windows Defender off.
Removing behaviour shield solved the problem. (Had to boot in safe mode)
Regards,
Attila
-
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.
Sure. Comodo version: 8.4.0.5165 - when I click update, says Up to date.
Firewall - safe mode.
Auto sandbox - disabled.
HIPS - safe mode / disabled - did not change.
Virusscope - enabled (only for sandboxed apps)
Avast: 17.1.2286
Windows 10, Pro, 64 bit, up to date
Windows Defender off.
Removing behaviour shield solved the problem. (Had to boot in safe mode)
Regards,
Attila
It left you with less protection.
Following the instructions posted by d4m4g3 would have given you full protection.
-
I have had exactly the same problem using Windows 10 x64 version (uptodate) on a DELL Latitude 3550. I am using Comodo firewall.
The problem is caused by the 'Behaviour Component'. With this switched on it seems to prevent any 32bit software from running.
You are right, you can't uninstall, can't run System Restore, or disable Avast.
My workround is as follows.
1. Start Windows in Safe Mode.
2. Set the 'Avast Antivirus' service to Manual.
3. Restart normally.
4. Go to Control Panel/Programs & Features
5. Select 'Avast Antivirus' and choose 'Change' then 'Modify'.
6. Unselect the 'Behaviour Shield' component.
7. Say 'NO' to restart now.
8. Closedown and restart in Safe Mode.
9. Set the 'Avast Antivirus' service to 'Automatic Start'. (Do NOT start it.)
10. Restart normally.
No requirement to uninstall Comodo (unless you want to).
:)
You are the hero ! thx
-
I have had exactly the same problem using Windows 10 x64 version (uptodate) on a DELL Latitude 3550. I am using Comodo firewall.
The problem is caused by the 'Behaviour Component'. With this switched on it seems to prevent any 32bit software from running.
You are right, you can't uninstall, can't run System Restore, or disable Avast.
My workround is as follows.
1. Start Windows in Safe Mode.
2. Set the 'Avast Antivirus' service to Manual.
3. Restart normally.
4. Go to Control Panel/Programs & Features
5. Select 'Avast Antivirus' and choose 'Change' then 'Modify'.
6. Unselect the 'Behaviour Shield' component.
7. Say 'NO' to restart now.
8. Closedown and restart in Safe Mode.
9. Set the 'Avast Antivirus' service to 'Automatic Start'. (Do NOT start it.)
10. Restart normally.
No requirement to uninstall Comodo (unless you want to).
:)
You are the hero ! thx
This again leaves you less protected.
Your computer, your choice.
-
I was the first one who talked about HIPS and Viruscope in this post but I didn't mean that disabling those options helped to solve the problem, they where already disabled when I started having problems so I mean they should not be related with the errors.
-
Uninstalled and reinstalled multiple times. Avast still crashes after a reboot. 0xc00000e5 same error for multiple programs.
What else can be done? Windows AV and firewall are turned off. No Comodo or other AV.
-
Hi All, apparently I have the same problem as many of you have. The difference between how many have solved it and what is happening to me is that I cannot get internet to work. And apparently, without that, I cannot actually uninstall Avast, whether through using avastclear.exe or not. When I try to use avastclear.exe, it simply stops pretty early on in the process and then nothing happens.
I tried to re-install the latest Avast, thinking that doing so might bring everything back to working status, including internet. But that also does not work.
I have successfully uninstalled comodo, it seems.
I am running windows 10 with two profiles, one is with a microsoft account and the other is a local account that I created. I can no longer use the microsoft account even with valid credentials (I checked using another computer that they are still valid). The reason probably is that the computer cannot validate without an internet connection. So then when I use the local profile, which is _also_ supposed to have admin privileges, certain things like turning avast off or turning it to "manual" mode through services does not work.
Am I going to have to manually delete avast folders and then go through the pain of regedit to remove all avast related entries? It feels like if I could get an internet connection, everything would get a lot easier..
-
I fixed this issue.
After trying to get rid of Avast and failing because my internet was not working, I tried to "repair" Avast, which also failed. But, I was able to turn off all the "components" of Avast.
Looking at services, I saw that many of the services had been disabled. Not exactly sure how or why that happened. I could not figure out a way to enable them en masse. So I used this list by blackviper to figure out what all the defaults should be: http://www.blackviper.com/service-configurations/black-vipers-windows-10-service-configurations/ It was painful but I got it done.
A reboot after the changes to services seemed to fix things - sort of. The internet would not come up but at least it recognized there was an adapter. The windows trouble shooter could not fix it. Looking at adapter properties, there were a ton of "items" it could use to set up the connection. I unchecked most of them, leaving only these checked on: ipv4, ipv6, qos pkt scheduler, and two related to link-layer topology. That seemed to fix the internet.
Once the internet connection was back on, I was then able to to use avastclear.exe to get rid of Avast completely. After another reboot, I reinstalled Avast. I turned off the "behavior shield" component.
Once Avast was installed and survived a reboot, I installed Comodo. As far as I know I only have the firewall turned on. I need to still figure out how to silence the annoying geekbuddy popups. But that can wait.
A couple of more reboots later, everything seems to be working. I noticed that Comodo has added itself to the Ethernet adapter properties as one of the protocols (in addition to the ones I mentioned above).
I created a system restore point, just in case.
Here is to hoping the computer stays operational !
-
I was able to install and run Avast on the second PC, as told on the previous page.
I followed the same steps as on the first one: Uninstall Avast in Safe Mode using the Utility.
Uninstall Comodo - important even if you have an older version like 8.2 or 8.4, restart, and then I installed Comodo 10 again, all shields running, and after that Avast Free (online installer).
It worked and everything seems fine. But this is a workaround, because we shouldn't do anything and Avast should just work after updating.
But now... It's too late for that. I'm glad anyway it works now. I don't know about other inexperienced users who don't know what should do now.
-
any other Fixes?? windows 10 and no comodo. Everything worked until the last upgrade. Computer down for two days. Uninstalled and reinstalled. Something wrong with the install from avast!
-
any other Fixes?? windows 10 and no comodo. Everything worked until the last upgrade. Computer down for two days. Uninstalled and reinstalled. Something wrong with the install from avast!
Try booting into Safe Mode . Once in safe mode, use a System Restore point prior to your update.
-
uninstalled and reinstalled multiple times. Using windows defender now. Avast will install and start to run then it will fail or it will stall while scanning the computer. Still something wrong with the update. How do I send in a crash report to Avast?
-
How do I send in a crash report to Avast?
-> https://www.avast.com/faq.php?article=AVKB160
-
The scanning problem has already been acknowledged by Avast as a bug.
-
We have been able to induce the problem in our labs. This conflict seems to be present only between Avast with Behavior Shield and Comodo FW 8.X. We were unable to induce the problem with Comodo FW 10. Although the problem is caused by Comodo code, we were able to implement a fix and release it through an update so Avast should be compatible with Comodo FW 8.X again from now on. Could someone please verify? Also, if you still have an affected machine were processes don't run, you can fix it by re-installing Avast or by upgrading Comodo FW to version 10. Thank you all for your help.
-
Just now I have installed updated Avast free. As I'm also Comodo FW 8 user I can confirm there is already no problem with Avast and Comodo. Thank you very much. Hopefully no problem will appear later... I'm testing it just a while.
-
Just installed Comodo 10 and updated Avast, same problem. Is there a correct sequence?
-
Just installed Comodo 10 and updated Avast, same problem. Is there a correct sequence?
You could try the latest beta: https://forum.avast.com/index.php?board=15
-
Just installed Comodo 10 and updated Avast, same problem. Is there a correct sequence?
The correct sequence was to totally remove both Avast and Comodo.
Once that was done, install Avast first, followed by Comodo.
-
The scanning problem has already been acknowledged by Avast as a bug.
Has this been fixed??
-
Installed beta and powered off.
After power on, all working.
Tks a lot.
-
You're welcome.
-
It is a bad idea to use Avast and Windows Defender at the same time. You should disable Windows Defender when you are using Avast. Windows Defender is good for basic protection when you don't have any antivirus software, but if you have an antivirus then it is best to disable to Windows Defender.
Take help from this link in order to disable Windows Defender:-
http://www.howali.com/2017/04/disable-turn-off-windows-defender-in-windows-10-8-7.html
Thanks & Regards
MJ Haider
-
It is a bad idea to use Avast and Windows Defender at the same time. You should disable Windows Defender when you are using Avast. Windows Defender is good for basic protection when you don't have any antivirus software, but if you have an antivirus then it is best to disable to Windows Defender.
Take help from this link in order to disable Windows Defender:-
http://www.howali.com/2017/04/disable-turn-off-windows-defender-in-windows-10-8-7.html (http://www.howali.com/2017/04/disable-turn-off-windows-defender-in-windows-10-8-7.html)
Thanks & Regards
MJ Haider
This all depends on the version of Windows that's installed on the system.
In windows 10, Defender turns itself off whenever a third part AV is installed.
In windows 7 and below, Defender is an Anti-malware not an AV program and should be removed.
-
And in Windows versions prior to 10, avast is disabling Defender when you install avast.
-
It is a bad idea to use Avast and Windows Defender at the same time. You should disable Windows Defender when you are using Avast. Windows Defender is good for basic protection when you don't have any antivirus software, but if you have an antivirus then it is best to disable to Windows Defender.
Take help from this link in order to disable Windows Defender:-
http://www.howali.com/2017/04/disable-turn-off-windows-defender-in-windows-10-8-7.html (http://www.howali.com/2017/04/disable-turn-off-windows-defender-in-windows-10-8-7.html)
Thanks & Regards
MJ Haider
This all depends on the version of Windows that's installed on the system.
In windows 10, Defender turns itself off whenever a third part AV is installed.
In windows 7 and below, Defender is an Anti-malware not an AV program and should be removed.
Yes of course bob3160, I accept that.