[FIXED] You are unprotected! Avast Background service is not running.

Repair Avast:
Control Panel> Program and Features (Add/remove program)>Select Avast> Select Repair. Reboot when completed
https://www.avast.com/faq.php?article=AVKB204
If Repair doesn’t fix the problem, try the following:
Clean Install of Avast:
https://goo.gl/4Ptzkf

Did a complete uninstall / reinstall and it seems to have fixed the issue cheers, hopefully this won’t come up again.

Ofcourse it should have fixed it because emupdate runs when you do that.
Easier was to follow the fix mentioned in the first post. :wink:

What’s important is that the user now has a properly working Avast. :slight_smile:

No. Didn’t work.
I still get the security center notification that Windows doesn’t find any antivirus on the computer.

Do a repair if that doesn’t work do a clean install.
Repair Avast:Control Panel> Program and Features (Add/remove program)>Select Avast> Select Repair. Reboot when completed https://www.avast.com/faq.php?article=AVKB204

If Repair doesn’t fix the problem, try the following:Clean Install of Avast:https://goo.gl/4Ptzkf

First you have put your question within petr’s comments (code marker ‘[’ missing, have fixed it in my quote).

Now to the meat of your question, this is different to the issue being discussed here.

The incorrect message You are unprotected! Avast Background service is not running. was from the avastUI. Which is why the fix hasn’t had any impact.

The error you are talking is a notification from the Windows Security Centre or the Windows Action Centre. Commonly this is because of a corrupt WMI.

But it’s the same cause, it started as soon as I rebooted from the update on Sunday.

Tried a repair.
I was hoping I wouldn’t have to bother with a fresh install because of Avast’s screw up.

No, it isn’t. Please follow the steps in the link DavidR posted and/or open your own thread. Your problem is not related to this one.

I am still getting the “You are unprotected! Avast Background service is not running.” message periodically. I can resolve it from the GUI or doing a reboot. I have done the repair install several times as well as a clean install twice.

I’m running Windows 10 Anniversary 64bit with avast 12.3.2280

Follow instructions: https://www.avast.com/faq.php?article=AVKB33#artTitle

I’m still having the same problem. This is after running the avast uinstaller in safe mode then installing avast again. This started after the Windows 10 1607 update on my desktop, but laptop started having this problem and its on Windows 10 1511. There is a bug in the avast application itself due to many people having the same issue. I’m to the point of jumping ship to another application and it sucks because I’m running a paid license.

Follow instructions: https://www.avast.com/faq.php?article=AVKB33#artTitle

I seem to be having the same issues. Its very annoying. I’ve been using Avast for years & typically recommend it.

I’m running Windows 7 Ultimate SP1

I’ve tried the various suggestions in the posts , but no resolve.

Thanks in adavce

ST

Follow instructions: https://www.avast.com/faq.php?article=AVKB33#artTitle

Check your installed programs. I had this persistent problem recently on one computer. My other computers with Avast! installed did not have the problem. One difference was a program was installed on the problem computer that was not installed on the others. That program was Advanced System Care 9. I uninstalled the program and now the problem has disappeared. This application may be the cause of your your problem. Hope this helps.

Iobit’s products aren’t really products that should be on your computer. :slight_smile:

Any suggestions for what to do if there is no protection and the support tool isn’t working either when dealing with this issue? It just sits uploading the support file well beyond the few minutes it’s said to take.

Edit: I managed to get it to finally upload.

Perfom a restart of Pc. :wink:

I really have to repeat my request not to update the software so often and only after testing it in real beta environment.
Afte the new fiasco with Avast 17.1.2286, I more and more think that all users are BETA testers indeed.