True for sure…but too many BSODs after GUI update. Seems a lot centered around XP and a lot of folks have a lot of conflicting software. I used Avast in its most basic state and I’m on W7 64-bit SP1 on all machines…which I’m guessing avoids 90%+ of the “posted” BSODs. Also, after reading all the posts one thing is for sure…I’ll take the extra time to do a clean uninstall/install and not GUI…that seems worth the time.

…old man like me :slight_smile:

You guys do a great job…I am just going to wait for another crank or two of the program code.

…this post really is about a solid Avast 8. So, I did some tests and looked at Event logs. The 3 machines that booted down DID a clean shutdown…in other words no MinDumps…and the Event viewer shows that exactly after the Avast completion they shut down. Funny thing is I’ve run each of these “Full Scans” manually today with no problem…which I’ve done time to time in past. I don’t think it is “Avast” per say but something Avast was trying to do that the system burped on. Each of these PCs has a external USB flash drive for small file backups (MyDocs) via a script…one of the three a large USB 500GB HDD…which has same MyDocs and a full Macrium Reflect image to it each night. All those “backups” went fine since before Avast…even the MBAM Pro 4am scans went fine. So, very weird that exactly at completion they shutdown. So, tonight a re-created my custom scans and enabled on one of the PCs and unscheduled the Full Scan on it. The Custom scan is System Drive, AutoStart, RootKit (quickscan). The other PC I’ve left alone with Full Scan, the third I checked the “Shut Down on Completion” then back to it an unchecked…I did this because it behaves like this flag/bit is set.

Anyway, we’ll see and I’ll post.