I have updated avast last sunday and apparently everything was working fine. Suddenly, the PC starts to behave strange. My .jpg photos do not open with windows built in visualizer, getting this message “Server execution fail”. I’ve decide to look at windows event viewer and a lot of event ID 10010 appears. So, I’ve roll back my system (with true image) before the update and everything works again.
Its occure when many com+ app run on your pc
read this, it maybe helps to you
http://support.microsoft.com/kb/870655
if your problem still their then
I suggest an installation from scratch:
- Download the latest version of avast! Uninstall Utility and save it.
- Download the latest avast! version and save it.
- Uninstall avast from Control Panel (if possible). If, for any reason, you can’t run it, try booting in Safe Mode and doing it from there. Anyway, boot after that.
- Run the avast! Uninstall Utility saved on 1. If, for any reason, you can’t run it, try booting in Safe Mode and doing it from there. Anyway, boot after you’ve run it.
- Install avast! using the setup saved on 2. Boot.
- Register your free copy or add the license key for Pro.
- Check and post the results. If, for any reason, you did not solve, try doing the step 3 in Safe Mode anyway.
Another step is needed so as to not be on the internet without protection.
2a. Disconnect the computer from the internet.
Well, then another step is needed.
5a. Reconnect to the internet.
That’s interesting, but i think this a bug!
In my other computer, i have win7 premium 64 bits and updating avast cause the same problem too. Before this release, there was no problems.
In windows XP SP3 that i have in my netbook, there was no problems. I think that there is something related with win7 64 bits.
I have no problem on my Windows 7 system. 8)
I did to the clean install after the last update though.
My other PC has version 5.1.864 and no problems. My PC is using version 5.0.677. In both, using the auto update get the problem. I will try a clean install and post the results.
No way… :'(. I’ve made a clean reinstall and the problem persist !!! A lot of event viewer errors related to DCOM and problems when opening jpg files with built-in visualizer. Back to previous version!!!
I get very few DCOM errors but I ignore them
These DCOM error messages are benign, and you can ignore them. As noted in the “Cause” section of this article, do not change your DCOM settings to prevent these error messages from being logged.http://support.microsoft.com/kb/298095
Try running sfc /scannow
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Some informations:
My PC: Win 7 Ultimate 64b, Phenom II X2, AMD Chipset
Using auto update from 5.0.677 to 5.1.889 - Problems
Clean Install of 5.1.889 - Problems
My Wife PC: Win 7 Home Premium 64b, Athlon X2, NForce Chipset
Using auto update from 5.1.864 to 5.1.889 - Problems
My Netbook: Win XP Home, Celeron, Intel Chipset
Using auto update from 5.0.677 to 5.1.889 - No Problems
My Wife Notebook: Win 7 Home Basic 32b, Pentium dual, Intel Chipset
Using auto update from 5.0.677 to 5.1.889 - No Problems
Looking at forum, a saw a amount of problems with others users using Win 7 64b. So, based in my home tests, i think there is some problem in 64b environment. In 32 bits everything is working like should be.
moses_x, try to disable Behavior Shield and test. If it does not, try uninstalling just it and test.
I had to make sure I had all the latest driver updates for my Gigabyte GA-G31M-ES2L E5200 2.5GHZ motherboard as that fixed many strange problems with my Windows 7 system.
Disable i already test in a clean install. I will try unistalling.
New info:
i use auto-update to get v5.1.889.
The problems appears: event ID10010 and problems using windows photo viewer (attached picture below).
Try to disable again behavior shield: same problem.
Try uninstall behavior shield: go to add remove and just after the boot: problem SOLVED !!! No more DCOM error and windows photo viewer working as supposed to do.
So, if this is a bug and i have to wait, which is best: continue using v5.0.677 or using the new version without behavior shield?
No contest, the new 5.1.889 version, as even without the behaviour shield it is better than 5.0.677.
Some news:
I’ve update my system from Catalyst v10.4 to Catalyst 10.12 (Video+Chipset) and realtek v2.48 to v2.56 and problem solved !!!
My wife system is a little old and there are no new drivers for it, so I’m using the latest legacy drivers: Catalyst v10.2, Nforce 15.53 and realtek v2.47 and i Still getting the problem. The only driver i can update is the audio driver, but i doubt that it is the culprit, because in my system only with the video+chipset update the problem was solved.
Wrong conclusion !!! The culprit is Comodo Firewall v4.1. Updating Comodo to v5.3, avast 5.1.889 works flawless. In my XP netbook, both (comodo v4.1+Avastv5.3) works without problems. Probably something with 64bits platform.