> Does it behave like this all the time or just at specific moments? Strangely, but these were... specific moments, but not too specific. I mean, it wasn't run

> Does it behave like this all the time or just at specific moments? Strangely, but these were... specific moments, but not too specific. I mean, it wasn't running from the startup till the shutdown, but I also don't remember any specific triggers such as running untrusted applications or something similar. However, I guess that, according to the CPU usage, it most probably were full system scans. One thing remains unclear though: why, despite me turning off this feature, it was still quite frequently (I'd say way too frequently for normal operation) performing the full scan. I have no ideas. I'll not list everything I tried and checked here - because it would be too long - but the most "suspicious" thing I downloaded at the time was ImHex executable. And I don't think any anti-malware would spend ~80% of CPU processing power just to scan one relatively small app. I checked different things that could trigger it - but found nothing. > Right now the antimalware executable process is using 196.4 MB of memory and 0% CPU for me as I type this. Likely because it's idle as you type this. It wasn't using all of my CPU resources all the time, it's just that it could randomly spike up at some moment, run for ~1-2 minutes (sometimes more), drag the system into thermal throttling despite the active cooling (a bit of hyperbole here but still, it was really able to heat hardware up) and then disappear. > if it's doing an active periodic scan. As I mentioned, most likely that was the issue: frequent periodic full-disk scans. For me, the worst thing was not that it was happening at all. To be honest, the worst thing was that I didn't understand why it was happening or how I could fix it. I just felt humiliated by the system that I, supposedly, owned. I know that I might have done something wrong or missed something, but... That still doesn't feel any good, you know.