High CPU Usage Caused by model_host.exe – Looking for Advice After Two Weeks Without Escalation (Case #25057125)

Hello everyone,

I have been using Avast products for many years, and my company has also relied on Avast for around ten years.

I’m posting here because I’m hoping to hear from other users who may have experienced something similar—both regarding the technical issue itself and the support process.


The technical issue

For almost two weeks my Windows 11 system has been heavily affected by Avast (Premium Secruity).

The problem causes one of Avast’s background processes (model_host.exe) to consume excessive CPU resources. On my Intel Core i7-12700K this results in all E-Cores running at or near 100% utilization during very common tasks such as watching YouTube videos.

The impact on my system is significant:

  • severe slowdowns

  • audio and video stuttering

  • poor overall responsiveness

  • reduced productivity

  • loss of working time

After many hours of troubleshooting I was able to narrow the issue down to Avast.

The troubleshooting included:

  • Windows Performance Recorder (ETL) traces

  • Windows Performance Analyzer analysis

  • Event Viewer investigation

  • driver verification

  • hardware acceleration tests

  • process analysis

  • multiple reproductions of the issue

The ETL traces consistently point towards Avast’s model_host.exe.

As an additional test, disabling or removing Avast makes the issue disappear completely.

All requested logs and diagnostic information have already been submitted to Avast Support.


My experience with Avast Support

The technical issue is only one part of the story.

The larger frustration has become the support process itself.

Case #25057125 has been open for approximately two weeks.

During that time I have:

  • contacted Avast Support five separate times

  • spoken with five different Level 1 support agents

  • submitted ETL traces, logs and diagnostic information

  • answered every request for additional information

I would like to make something very clear:

This is not a complaint about the Level 1 support agents.

Every representative I spoke with was polite, professional and genuinely tried to help within the limits of their role.

My concern is directed solely at the escalation process.


Repeated callback promises

During these two weeks I have repeatedly been promised callbacks from the escalation team.

Among the promises were:

  • callback within 24–48 hours

  • callback on Monday

  • callback the following day

  • callback within another 48–72 hours because the case had entered “Senior Supervision Review”

Unfortunately none of these callbacks ever took place.

Each time I contacted support again, I received another promise that someone from the escalation team would contact me soon.

Even during my latest conversation, I was once again told that my case had been marked for priority handling and that I would receive a callback within another 48–72 hours.

That callback also never happened.


Why I’m posting here

I understand that complicated technical issues sometimes require time.

I also understand that Level 1 support has limited permissions and cannot directly influence the escalation team.

What I find difficult to understand is the repeated commitment to callbacks that are never carried out.

After almost two weeks, four separate contacts with first-level support, multiple promises of callbacks that never happened, and still no contact from the escalation team, I honestly feel completely let down by Avast’s customer support.

Until this experience, I was genuinely happy with Avast and trusted the product to protect my system. Unfortunately, the way this case has been handled has seriously damaged that trust. Waiting for days, repeatedly being promised a callback that never comes, and receiving virtually no communication has been extremely discouraging.

I never wanted this post to become a complaint about customer service. I came here because I need help with a technical problem that significantly impacts my daily work. But after nearly two weeks without any meaningful response from the escalation team, I feel I have no other option than to ask the community for advice and to share my experience.

At this point, I would simply like to ask the community:

  • Has anyone experienced excessive CPU usage caused by model_host.exe?

  • Has anyone else had a similar experience with Avast’s escalation process?

  • Is there any alternative way to communicate with Level 2 support besides waiting for callbacks?

I’m genuinely interested in hearing whether this has happened to other users or whether my experience is unusual.

Thank you for taking the time to read this.


I believe this is the same issue reported here:

For now you have to disable Deepfake Guard to stop Avast from consuming your CPU. As I stated in that topic, DeepFake Guard uses its own AI model and if there is no available AI-capable GPU and user still wants Avast to run it (maybe unintentionally), Avast runs it on CPU which causes high CPU usage.
Deepfake guard analyse YouTube video for possible AI-made fraud, which is the reason why you observed high CPU while watching it.

1 Like

Thank you for your reply and for pointing me to that thread.

I already came across the Deepfake Guard suggestion during my troubleshooting, but unfortunately it doesn’t seem to be the cause in my case.

Here are the steps I have already taken:

  • Deepfake Guard was disabled.

  • Hardware acceleration was tested both enabled and disabled.

  • The issue was reproduced in multiple browsers (Firefox, Brave and Edge).

  • Windows Performance Recorder (WPR) traces were captured and analysed with Windows Performance Analyzer (WPA).

  • The traces consistently showed Avast’s model_host.exe as the process responsible for the excessive CPU usage.

The most important observation is this:

As soon as Avast is disabled or uninstalled, the problem completely disappears. CPU usage immediately returns to normal and the system behaves as expected.

As soon as Avast is enabled again, the issue returns.

Because of that, I don’t believe this is solely related to Deepfake Guard. It appears that model_host.exe is triggering excessive CPU usage under certain conditions while YouTube videos are playing, regardless of whether Deepfake Guard is enabled.

If there are any additional logging options or internal diagnostic builds available, I’d be happy to test them. I already have ETL traces and would be glad to provide any further information that could help identify the cause.

PS:
Short review after i deinstalled Avast at full:
Avast has been completely removed, yet YouTube works normally. CPU usage is around 12%, the workload is distributed across the cores as expected, and the excessive E-core utilization is gone. This strongly suggests that the issue was not caused by YouTube itself, but by Avast’s model_host.exe interacting with video playback.

1 Like