So I’m using Avast free and have been for some time, seemingly since the last windows update when I right click the avast Icon on the taskbar and hover over Avast Shields control it states 1 shield is disabled, it won’t re-enable it by clicking the enable all shields button. The only shields the Avast user interface shows me are File, Behavior, Web and Mail and they’re all showing as on. So whats this fifth shield I can’t find and can’t enable?
does this change anything? https://support.avast.com/en-eu/article/Repair-Antivirus
There are already a couple of topics reporting on this, not sure if the repair suggested by Pondus would change things, but it is worth a try.
EDIT: Check and follow this one https://forum.avast.com/index.php?topic=217998.0.
Nope, still the same after, thanks anyway.
Thanks, I didn’t find that thread when searching this problem, good to know I’m not the only one with the issue.
You’re welcome.
Getting same 1 shield disabled on right click of Avast in system tray. on Windows 10 Home. Protection shows all shields enabled though.
I have since heard from Avast who state it’s a known issue, they’re working on a fix and no shields are actually disabled. 
I expect the fix won’t be until the next program update as it’s not a security issue and not causing any problems.
Not a security issue. Its a known bug that’s already being worked on.
That’s what I said.
Thanks for the info guys.
Hi,
Win XP / 32-bit / Avast Free
Noticed the same for last month-odd.
I can advise that I am damn sure that there were 5 shields, and they were all together in Components.
(I guess installing an earlier Avast Version will confirm what shield is now ‘missing’ (or now hidden).
Just updated to V18.4.2338 and still the same.
Why doesn’t someone at Avast simply inform what the fifth shield was/is and where its’ gone!
(or where it can be found).
Seems silly not to!
Andy HMTDuvN
It’s just a GUI bug, nothing to worry about.
-I know I’ll be accused of “kicking a dead horse” with this reply/post, because this topic is nearly a month old, but AFAIC the issue is still present… and from my observations over the years, it appears to have been an issue since around 2014 or so. Issue is still present in V18.4.2338 build 3895.326.
—I would be so inclined to believe the issue is brought on by “sandbox”. I have never had a problem with Avast until this came to be a visible part of the program…
… and it seems to be the part of the program that they cannot make up their mind, whether or not it is included in the free version. Now, maybe it has to do with Avast not understanding what a USB port is or how to scan it, and the most recent onslaught of virus infecting USB ports… but before I lay judgement against Avast, I’ll do a full* uninstall (like I’d do to something unwanted like AOL… LOL) and a fresh install, to see if the issue is still present.
—I am sick of seeing “Enable all shields (1 disabled)” in my taskbar and really don’t care is someone says “there’s nothing to worry about”. A glitch is a glitch and in these days with 10yr old kids doing more than mastering Super Mario… and hacking the pentagon like the kids whose leader invented/designed Sygate Personal Firewall, I don’t like even the slightest glitch, so it will be the end of me liking Avast.
—… but before I lay judgement, I’m flushing Avast and wiping all traces, then unpacking again for hopefully, another pleasant stay.
—Completed complete flush of Avast and installed supposedly the latest from the site (saved prior to uninstall> disabled networks> restart> install> restart> enable networks>) and showing now version 18.4.2338 build 18.4.3895.0, which to me says it is a less recent copy of what I had before, but still showing “enable all shields (1 disabled)”.
—I think I’ll move onto another APV until they figure it out; maybe even purchase a license again so I am insured… but again, somewhere else. I don’t, at all, like, hearing… “don’t worry about it”. It doesn’t, one bit, make me feel secure.
As already stated, it’s an old bug that hasn’t been fixed. Nothing more.
Try the beta and see if it’s fixed there if it’ bothers you that much.