Uninstall Avast by control panel [If you don’t have Avast in control Panel go to #4]
Uninstall in safe mode using Avastclear.
Run Rejzors Uninstall Utility in Normal Mode (removes traces avastclear doesn’t) - reboot.
Check : Once uninstalled check in device manager>view>show hidden devices if there is anything related to avast with a yellow triangle… if so, uninstall it and reboot.
Sorry, but how crazy is that??? You tell me in fact not to use the built-in updater and not to click on “UPDATE” inside avast (to update from 2014.9.0.2008 to 2014.9.0.2011) but to first uninstall and then reinstall the whole bunch??? Are you serius or just kidding???
Sorry, but …
Btw: I’d rather know a reason why that could happen and how to avoid it – and I consider it as a bug!
More aptly put, Avast! update appears to require access to a web site the mvps maintainers perceive as a “parasite” web site and have blocked. That’s not just a bug but a design bug.
I fully agree with Anacunga: If the Avast! updater causes an installation to corrupt itself - even given that it tries to access a blocked web site and fails - then there is a serious bug in the product. I have experienced such a bug myself recently, and have had to uninstall and reinstall to restore operation. My confidence, built over nearly a decade, in Avast is greatly shaken.
With computers nothing is about “luck”, it’s about robust - or not - design.
It does no one any good to try to claim the concept of failure is normal and expected and based on luck. With critical security software, the designers MUST NOT allow failure to happen! The term “failsafe” is not new.
The updating procedure from [insert version here] to 9.0.2011 does require the emergency updater to put all the relevant fixes in. If that doesn’t work, most likely, the installation would not be successful/not working properly.
You might want to look at the logs of any other security program(s) you are using to see if one may have blocked the shields.
Also check your Windows event logs and see if there are any related errors, and the Avast setup log located in \Application Data\AVAST Software\Persistent Data\Avast\Logs.
If it was a failure as you put it then every computer that has avast installed on would behave the same, since that isnt the case and only the minority of the users using avast is having such issues then I would call it more of a conflict with something else, and since every computer is unique its not like each one will always go as smoothly as expected.
It’s a DESIGN FAILURE plain and simple if a network problem results in Avast corrupting its installation.
It could verify hashes, etc. to determine that files have not been corrupted. It could back out and fail safe if the update cannot be completed.
Luck has nothing to do with this. Network problems must be expected to happen. There will NEVER be a time when you can 100% guarantee the ability to reach a web site on the other side of the world - or even at the other end of a LAN cable.