Author Topic: REGISTRY CHANGES TO UNINSTALL AVAST FREE - ever been sent them?  (Read 1820 times)

0 Members and 1 Guest are viewing this topic.

Offline bob3160

  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 43710
  • 60 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: REGISTRY CHANGES TO UNINSTALL AVAST FREE - ever been sent them?
« Reply #15 on: January 23, 2020, 11:38:03 AM »
Hi Andrew-Dillon,
it looks like avast logger's severity is set to debug. You can change it in Avast UI  Settings -> Troubleshooting There should be a checkbox "Enable debug logging" - uncheck it please !

! Please do not delete all files in c:\ProgramData\AVAST Software\Avast\log folder ! but use this powershell commad which will delete only amsi log files :
Remove-Item "c:\ProgramData\AVAST Software\Avast\log\Amsi.log.tmp*" -Force

How to launch powershell :
https://www.digitalcitizen.life/ways-launch-powershell-windows-admin

Thank you for report !

 
Getting an unexpected token error?

Unexpected token '-Force' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnexpectedToken
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 10 Pro v1909 64bit, 24 Gig Ram, 1TB SSD, AvastOmni 20.3.xxx, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq

Offline kwiq

  • Avast team
  • Sr. Member
  • *
  • Posts: 250
Re: REGISTRY CHANGES TO UNINSTALL AVAST FREE - ever been sent them?
« Reply #16 on: January 23, 2020, 12:21:37 PM »
Try to omit -Force argument ?