Free Avast 22.10.6038 (build 22.10.7633.752) keeps crashing every minute

Hi all,

A few days ago I noticed that my free Avast crashes within seconds after startup, and after each restart. The display message is: “Sorry, We’ve Crashed.”
In the Task Manager, many instances of Avast are working, except AvastUIexe/nogui. It has a red X.

I have Windows 10 x64. A Toshiba Satellite laptop. I have been using Avast since 2010, and this laptop never ever had any problem with Avast.

I read a few articles about this. So I first tried to repair Avast. It did not last, because after restart, it crashed again. Then I removed Avast completely, eradicated it even from the Registry meticulously. I made a clean install.
It crashes after a few minutes.
I have no idea of what causes this problem. I have no other antivirus running. In fact, I have not modified the system, nor installed anything recently. I just did not do anything. It started alone.
Any idea how to overcome this or I should move onto the next free antivirus?
Thx in advance

Hi,

Please provide a support file ID. https://support.avast.com/en-ww/article/submit-support-file/

Thank you. I have generated a report.

In the meantime I restored my PC with Macrium to the last disk image I had from this summer. Avast was working fine for 2 days thereafter. Then it started again, out of the blue: The Service Control Manager tried to take a corrective action (Executar o programa de recuperação configurado) after the unexpected termination of the Avast Antivirus service, but this action failed with the following error:
No recovery program has been configured for this service.

The Avast Antivirus service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 5000 milliseconds: Executar o programa de recuperação configurado.

param1 Avast Antivirus
param2 3
param3 5000
param4 3
param5 Executar o programa de recuperação configurado
610076006100730074002100200041006E0074006900760069007200750073000000


Binary data:

In Words

0000: 00760061 00730061 00210074 00410020
0010: 0074006E 00760069 00720069 00730075
0020: 0000

In Bytes

0000: 61 00 76 00 61 00 73 00 a.v.a.s.
0008: 74 00 21 00 20 00 41 00 t.!. .A.
0010: 6E 00 74 00 69 00 76 00 n.t.i.v.
0018: 69 00 72 00 75 00 73 00 i.r.u.s.
0020: 00 00 …

And now I just verified that Avast immediately crashes when I boot in Windows in Safe Mode. I am trying to schedule a boot-time scan but it just hangs until crashes. But for instance, I managed to instal the new definitions for boot-time scan.

What’s more: I reinstalled Avast, and as long as I did not restart my PC I could schedule a boot-time scan. So I restarted again, ran a boot-time scan which found no issues whatsoever. I booted in Windows and voilà, Avast Crashed. So I had to uninstall again.

I guess this has to do something with an update, a bug in a novel Avast version. BUT: why don’t I see many people asking for help here? Does it affect only me? How is it possible?
Anyway, let’s wait for the analysis of the ticket I sent with the troubleshooting tool.

Hi,

Can you please uninstall all other antivirus/malware/spyware applications and try again?

Thank you for your feedback.

As I stated in the opening post:
"Then I removed Avast completely, eradicated it even from the Registry meticulously. I made a clean install.
It crashes after a few minutes.
"

Then as I stated in the next post:
In the meantime I restored my PC with Macrium to the last disk image I had from this summer. Avast was working fine for 2 days thereafter. Then it started again, out of the blue:
Which means that the OS was put back to the best configuration, and Avast reinstalled itself to the newest version, and then it started to crash. Before updating itself completely, it was working for 2 days.

I don’t really trust other antivirus programs, neither do have experience with them, but I guess I just have to move on.

So as I see, everyone is clueless about why Avast crashes constantly.
Is there any way to install an earlier version that was still functioning, and prevent it from updating to the not working version?

Probably a silly suggestion but I noticed you’re referencing version 22.10. Have you tried updating to 22.11?