Timur Born's latest activity

09 keeps the counter set to 0x330 indefinitely now, even after quitting HWinfo. On my first test I had the curious case of a Defender...

Maybe you can ask the TS/CC author what he is doing exactly? He specifically mentions HWinfo in the Readme, so maybe he is willing to help!?

Unfortunately still happening here: 2024-04-03 14:25:52 00:01:21 0x330 Normal 2024-04-03 14:25:53 00:00:01 0x222 Defender...

Another day, another full virus scan. Build 07 after 12 minutes, 4:30 min of which where running the full scan. Comparing this to the...

Comparing build 06 vs. 07 after 1 hour of various desktop load - aka not fully controlled - with all C- and P-states disabled ("Disable...

Ok, I think we can rule out that starting Counter Control was the reason for the back and forth. It's likely rather running a full scan...

I accidentally quit Counter Control, but as you can see in this log there is a time-span where Defender fought harder for control and...

What I don't like about it is that the counters keep switching every second for two minutes when it happens (sometimes multiple times...

Maybe there is a conflict between HWinfo and Counter Control? Here HWinfo - running in the background - did not successfully reset the...

Is the 2 minutes interval expected for your implementation? This fits the 2 minutes it takes for Defender to take over again after...

This single occurrence of prolonged Defender time is rather puzzling, because from what I can see otherwise Defender tries to use the...

Unfortunately I celebrated too early: 2024-04-02 18:04:58 00:00:23 0x222 Defender 2024-04-02 18:04:59 00:00:01 0x332 Warning...

I will let HWinfo run for a few hours to watch how stable this is over prolonged runtime.

Yep, that worked. Took about 2 minutes for Defender to take over again after closing HWinfo. :)

Unfortunately you cannot just check for the Defender process to know whether Realtime Protection is enabled or not, because the process...