Again, true but not true.
Yes, the last loaded driver is posted…AND “that” driver is out doing something before the next shows it has loaded.
You have no idea if the “action” of that driver is causing the issue or if the next driver cannot be loaded.
You don’t think that the “action” of the loaded driver has an effect ?
Just look a the Forum posts…it is all coincidence that the same exact Avast driver loads on all these different setups but it is not the issue ?
I’ll admit…this is only my conjecture…why ?..because no one from Avast it saying a thing about this.
Luckily Essexboy is truly helping where he can for these hosed up machines…some of which are too far gone and need O/S repair or FULL format/install to use…that is a bricked machine. Does this happen to everyone ?..no, of course not…is it happening to a lot of people…YES, simple Forum search will tell you that. Is it relevant to the question of this thread because of the type of issue ? Yes it is…IMHO.
My only point in all this is not to abandon Avast…I still am a believer in the software but am I a believer in the risk/reward of Avast 9 over 8 ?..no, I am not.
Will I continue to monitor this Forum and the updates, YES…once it is clear that the frequency and severity of events die down.
For those of the folks that are all OK about this because their install went well…ponder this.
These system locks occurred after Windows updates…I ask you…have you done a Windows update since your good install ?
Wonder what is going to happen during next MS release of updates and a reboot with Avast 9 ?..guess you guys sleep OK with that…not me. :-\
You honestly wont know what will happen with your own system till you try, found that out myself when I tried updating the vista computer in the house.
Honestly though you can wait all you want but you dont need to be posting on every thread about topics such as this, we get your point and its starting to get very annoying to re-read it over and over. Your starting to sound like a broken record and if it were mine I would of thrown if out a long time ago(honestly surprised it hasnt happened already).
Thanks to all who responded with personal experience with this update (and no great thanks for those who simply speculated and turned this into a debate or criticism of others).
The only real power of a forum such as this is in the sharing of personal experience.
After successfully testing the update in a Win 8.1 virtual machine, and using it for a few days, I updated my host system by visiting the Avast UI page and having it install the update (then reboot).
Seems to have worked, and the system is stable, though I have had one glitch: Some time after I logged in this morning (system was left running, just logged out), the Avast icon in the System Tray told me I was unprotected. I haven’t seen that happen before. The only time in recent history that I messed with the protection was to Disable the Shields for 10 minutes to run a benchmark day before yesterday (I NEVER disable Shields permanently). Possibly the re-enable process never automatically occurred as it was supposed to. I don’t know if this is a new problem, as I only rarely disable the shields temporarily anyway.
I checked the water first myself on a test system AND asked around. Note that besides a number of folks apparently wanting to turn this into a social meet, no one actually came on here and said “it trashed my system”.
More experience sharing from me:
With 2014.9.0.2013 I just completed a full scan of the 1 TB of data on my 2 TB system volume. It completed in 25 minutes (nice!) and found 0 infected files.
Having had much trouble here with the update to 2014.9.0.2011, which ultimately resulted in my having to do a full uninstall of Avast, clean, and reinstall, I’m going to be wary of Avast updates for a while - some months at least.
Trust is built up over time, but lost in an instant.
I don’t know if some of the above critical postings were directed at me, specifically, but if my posting a thread on a forum asking for others’ experience before blindly trusting software that has recently shown itself to cause problems bothers you somehow, I suggest you need to find some other hobby.
I sincerely apologize to anyone that felt I was directing comments to them personally…I was not.
I am just a very techy user (like I’m sure many folks here) and have used Avast…and previous A/Vs for years.
I’m also a avid reader of Forums and moderate others.
Having gone thru the AVG8 to AVG9 nightmare I always do some reading when major code changes happen in software.
This is even more true with a type of software like a “A/V” that by nature is intrusive to the system.
Reading from Sept/Oct to now the code has improved I just was giving my impression of some of the “types” of risks.
Features not working are a PITA but not always mission critical…like disabling AOS or uninstalling Web Browser.
I was just pointing out some of the others more critical in my view.
Anyway, I just was giving the other side of the viewpoint…which seems to hit a sensitive cord here…sorry for that.
The only one that I think has the “total trash effect” is the aswRvrt.sys boot hang issue.
You can search on this and there are a tons of threads.
What is bothersome is not only Normal mode but also Safe mode hangs.
A lot of help from Essexboy on FRST to remove Avast…some successful some not.
It is unclear if this aswRvrt.sys driver is the issue or what I understand is the mup.sys past it.
It is also hard to tell with all the different system configs if there are file system issues already on those systems.
What makes it more suspicious is many of these come up after a Windows Update and subsequent reboot.
Essexboy says the Avast Team is looking into this and trying to re-produce.
Since good portion of folks have to re-install there O/S then perhaps the recommendation is for people to first make sure you have a offline “image” of your HDD before upgrade…because you may not be able to use a system-restore or even a manual file system recover.
Also, as many have posted on threads…preferable to do a clean uninstall/install of Avast as opposed to GUI.
Lastly, perhaps a check of your system to make sure any old/previous A/V remnants have been uninstalled/cleaned.
Thus, perhaps the discussions/recommendations should not be “if” you upgrade but steps/preps when you do.
