I have been using Avast Free for several years now without problem, until very recently.
I decided to pay and upgrade to the Pro version 2015
Whenever I start my laptop none of the shields nor the Avast Background Service start automatically. The rest of Avast starts and seems to function fine, but these specific components do not. Now every time I start up my laptop I need manually start the Shields and background service.
After looking through some older threads I have tried using the “repair” option in the Avast uninstaller to no effect (including reboot). I have also tried completely uninstalling (including reboot) and then subsequently reinstalling Avast, also to no effect.
After a quick search I’ve found the relevant uninstall tool (https://www.avast.com/en-us/uninstall-utility) and will try using it to remove avast. I completed this in safe mode. restarted, restarted again, installed and I have the same issue.
So Basically I’m back where I started. The uninstaller did not appear to have any discernible effect on the behavior of Avast.
Also, no definition or software updates work properly.
Farbar Service Scanner Version: 21-07-2014
Ran by USERNAME (administrator) on 05-01-2015 at 16:23:05
Running from “D:\Users\USERNAME\Google Drive”
Microsoft Windows 8.1 Pro with Media Center (X64)
Boot Mode: Normal
Internet Services:
Connection Status:
Localhost is accessible.
LAN connected.
Google IP is accessible. Google.com is accessible. Yahoo.com is accessible.
Windows Firewall:
Firewall Disabled Policy:
System Restore:
System Restore Disabled Policy:
Action Center:
Windows Update:
wuauserv Service is not running. Checking service configuration:
The start type of wuauserv service is set to Demand. The default start type is Auto.
The ImagePath of wuauserv service is OK.
The ServiceDll of wuauserv service is OK.
Windows Autoupdate Disabled Policy:
Windows Defender:
WinDefend Service is not running. Checking service configuration:
The start type of WinDefend service is set to Demand. The default start type is Auto.
The ImagePath of WinDefend: “”%ProgramFiles%\Windows Defender\MsMpEng.exe"".
C:\Windows\System32\nsisvc.dll => File is digitally signed
C:\Windows\System32\drivers\nsiproxy.sys => File is digitally signed
C:\Windows\System32\dhcpcore.dll => File is digitally signed
C:\Windows\System32\drivers\afd.sys => File is digitally signed
C:\Windows\System32\drivers\tdx.sys => File is digitally signed
C:\Windows\System32\Drivers\tcpip.sys => File is digitally signed
C:\Windows\System32\dnsrslvr.dll => File is digitally signed
C:\Windows\System32\mpssvc.dll => File is digitally signed
C:\Windows\System32\bfe.dll => File is digitally signed
C:\Windows\System32\drivers\mpsdrv.sys => File is digitally signed
C:\Windows\System32\wscsvc.dll => File is digitally signed
C:\Windows\System32\wbem\WMIsvc.dll => File is digitally signed
C:\Windows\System32\wuaueng.dll => File is digitally signed
C:\Windows\System32\qmgr.dll => File is digitally signed
C:\Windows\System32\es.dll => File is digitally signed
C:\Windows\System32\cryptsvc.dll => File is digitally signed
C:\Program Files\Windows Defender\MpSvc.dll => File is digitally signed
C:\Program Files\Windows Defender\MsMpEng.exe => File is digitally signed
C:\Windows\System32\ipnathlp.dll => File is digitally signed
C:\Windows\System32\iphlpsvc.dll => File is digitally signed
C:\Windows\System32\svchost.exe => File is digitally signed
C:\Windows\System32\rpcss.dll => File is digitally signed
OK all services are good, so lets now check the veracity of the files. This can be caused by the wrong version system file being present
Open an elevated command prompt
Type Command in the search box
Right click Command Prompt when it appears and select run as administrator
In the black box that opens type in the following command :
sfc /scannow
Then press enter
On completion reboot and let me know if the problem is still present