Hey there Guest!
Hey - did you know if you click on the title of a thread it will take you to the first unread post since you last visited that thread?
but were afraid to ask: 
STOP!! Never post your email address in open forums. Bots can "harvest" your email! If you must share your email use a Private Message or use the 
smilie in place of the real @
Pretty Please - add it to our Events forum(s) and add to the calendar! >> 
D
Deleted member 8987
Guest
Guest
Offline
I used to use AVG...until one program update years ago where it was NOT written for AMD processors, and I became one of thousands with all files wiped clean and the OS impacted to where the machine shut down.
I went to various, settled late last year again on Avast.
Unbeknownst to me, Avast and AVG merged in 2016. They are virtually the same, including user interface and settings.
Well, month or so ago, my wife's 64 bit machine presented a BSOD (blue screen of death) with fltmgr.sys failure.
I was able to msconfig and deselect certain items and get it going again, albeit with Behavior Shield inop.
Three days later my 64 bit machine did the same thing (so we know it isn't machine specific). Since hers had MS updates still on, it was a question..but mine are killed, so it ain't MS this time.
This year Avast and AVG seem to want to reboot with every definition update...and you start all over.
Go to the Avast forum, all sorts of posts on this...various failures with BSOD reported, a lot with fltmgr.sys listed.
Couple I saw with Windoze 10, fair amount with 7-64, a whole lot with XP-64.
Renewed the license for ESET which I used for two years, and now I can light it off with startup and services in msconfig set to "normal".
Morons.
I went to various, settled late last year again on Avast.
Unbeknownst to me, Avast and AVG merged in 2016. They are virtually the same, including user interface and settings.
Well, month or so ago, my wife's 64 bit machine presented a BSOD (blue screen of death) with fltmgr.sys failure.
I was able to msconfig and deselect certain items and get it going again, albeit with Behavior Shield inop.
Three days later my 64 bit machine did the same thing (so we know it isn't machine specific). Since hers had MS updates still on, it was a question..but mine are killed, so it ain't MS this time.
This year Avast and AVG seem to want to reboot with every definition update...and you start all over.
Go to the Avast forum, all sorts of posts on this...various failures with BSOD reported, a lot with fltmgr.sys listed.
Couple I saw with Windoze 10, fair amount with 7-64, a whole lot with XP-64.
Renewed the license for ESET which I used for two years, and now I can light it off with startup and services in msconfig set to "normal".
Morons.
A friendly reminder - be careful what links you click on here. If a link is posted by someone you don't know, or the URL looks fishy, DON'T CLICK. Spammers sometimes post links that lead to sites that can infect your computer, so be mindful what you click.