Author Topic: avast status can't start agent after stop/start service  (Read 5063 times)

0 Members and 1 Guest are viewing this topic.

REDACTED

  • Guest
avast status can't start agent after stop/start service
« on: June 18, 2017, 07:01:00 PM »
Hi,

new problem
When stop and start service aswbIDSAgent; avast say not all agent started and: clic RESOLVE button not work.
restart manually action suspect agent not work.

workaround: disable AVAST; and enable all agent

Offline Be Secure

  • Long Time Avast User(10years.....) Security Enthusiast.
  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1908
Re: avast status can't start agent after stop/start service
« Reply #1 on: June 20, 2017, 01:37:13 PM »
Repair Avast:
1. Control Panel -> Add/Remove programs -> Avast
2. Click on 'Repair'.
3. Follow instructions.
4. Reboot.
PC- Windows10 EDU 64Bit,avast! free 21.1.2449,uBlock Origin,NVT_OSA,GoogleChrome(64bit),CCleaner,Unchecky,ZAM Free,Shadow Defender.
Security Enthusiast

REDACTED

  • Guest
Re: avast status can't start agent after stop/start service
« Reply #2 on: June 20, 2017, 03:49:33 PM »
How will this fix the bug?

It's already a new install. and why repair ?  It's a bug, repair operation not work. Disable all agent/ enable all work.

Offline PDI

  • Avast team
  • Full Member
  • *
  • Posts: 159
Re: avast status can't start agent after stop/start service
« Reply #3 on: July 13, 2017, 05:01:50 PM »
Hi Baudav,

we are looking into this issue but the agent is not supposed to be stopped via SCM. The AvastUI should be used for it.

Regards,
PDI

REDACTED

  • Guest
Re: avast status can't start agent after stop/start service
« Reply #4 on: July 13, 2017, 05:22:20 PM »
yes, but avastUI not stop it.
It display the agent is disabled, but service stay running and continu to request my NAS (I see it when my NAS not hibernate).

Offline PDI

  • Avast team
  • Full Member
  • *
  • Posts: 159
Re: avast status can't start agent after stop/start service
« Reply #5 on: August 12, 2017, 09:34:17 AM »
Hi baudav,

the problem is fixed in the 17.6.2307 Beta build.

Regards,
PDI