Free version 11.2.2262. Windows 10, 64-bit. While I can click the Component Stop display to disable the shields, nothing happens! It used to work, and I don’t know if it stopped after the latest Avast program update or not. The same program version on another machine running Windows 10, 32-bit is working normally.
I uninstalled using Avastclear in the safe mode, rebooted, and reinstalled, but nothing changed. HELP!!!
Thanks for the tip; but as I said, I did a clean uninstall followed by a new install fresh off the site. Nonetheless, I tried the repair function with no effect. I recently installed a couple new programs, on the 64-bit machine affected, and wonder if any of them could have somehow messed things up. Guess I’ll have to try System Restore to find out. Has anyone else ever experienced this problem?
I wouldn’t think so. The recently installed programs are:
Acronis True Image
IDLE Python (development system)
IDM UltraCompare (software development)
WYSIWYG Web Builder
I haven’t tried System Restore yet – would hate to lose the programs and have to reinstall; unless of course, one of them is conflicting. All of those programs AND Avast were working fine until I recently “upgraded” to Windows 10. Huuuummmmmm!
Those applications are very unlikely to cause problems with avast.
I suggest to post the Farbar log files (FRST.txt and Addition.txt) to your next post.
Perhaps we can find something in them that is (possible) causing the problem.
Thanks Eddy, and I’d like to comply, but where do I find the logs you mentioned? (I’ve just spent the last hour trying to get back online after fooling with msconfig What a joke! Would only reset to normal in the safe mode.) Thanks!
No wonder I couldn’t find the logs, I was looking in Avast – not Malwarebytes! I have something else to try first, and if doesn’t work, I’ll see about postiong the logs tomorrow. Thanks for your help!
FALSE ALARM! Skipping the long story, everything is back working the way it should! As is usually the case, I often “tweak” a few things at a time, being more in a hurry to fix things than discovering exactly what’s going on. (Yeah, I know, that sometimes creates more problems than it solves.)
I can’t be sure, but I think when I did a custom install of Avast, I might have neglected to check File Shield (or something else), but can’t explain why it was working before. Reinstalling on top of the existing program got things going again. Sorry I can’t be more specific – I’m totally confused at this point … confused, but happy!
Are there any settings that could prevent disabling the shields?