Why is AddInProcess.exe Using Nearly 100% CPU on My ASUS TUF F15?

September 21, 2026 3 answers
Asked by MellowQuill27
I'm using a 2022 ASUS TUF F15, and it occasionally becomes almost unusably slow, with severe cursor lag. Task Manager shows CPU usage around 99%, while memory usage is only about 37% of my 24 GB. AddInProcess.exe is responsible for roughly 96.2% of the CPU load, and my NVIDIA GPU temperature reaches about 83ยฐC. I don't know what this process does or why it is consuming so many resources. Could it be caused by overheating, malware, or another application, and what is the safest way to troubleshoot and fix it?

Answers

NovaHarbor6
You can end the process temporarily from Task Manager to restore performance, but that only treats the symptom. Check the Startup and Installed apps lists for anything unfamiliar, especially mods, injectors, or unofficial add-ins. Also install pending Windows and ASUS driver updates and reboot. If the process returns, note its exact path and any related application rather than removing a system file manually.

QuietPanda44: The GPU temperature alone isnโ€™t proof of malware; around 83ยฐC can be normal under gaming load. Check CPU and GPU temperatures while idle and under load, and clean dust or improve airflow if temperatures remain high.

Reply to this answer
CedarFox_81
First check where the executable is located. In Task Manager, right-click AddInProcess.exe and choose โ€œOpen file location,โ€ then inspect its Properties and digital signature. AddInProcess.exe can be a legitimate Microsoft .NET component, but malware can use the same filename from a different folder. Donโ€™t delete it just because the name looks suspicious. Run a full scan with Windows Security, including the offline scan if the problem continues, and check for recently installed programs or game add-ons.
Reply to this answer
AmberTide19
Be very careful with advice telling you to take ownership of a file in the Microsoft .NET Framework folder and delete it. That can damage Windows or break applications. Verify the fileโ€™s path and signature first, repair or reinstall the related .NET component if necessary, and use reputable antivirus scans before considering removal. If scans find a threat, quarantine it through the security software instead of deleting protected framework files by hand.
Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions