@Fiery Thank you for the update. While most of us knew that this is a Windows 11 bug, we were more upset of the fact we were not getting much of a explanation as to why other programs have found work arounds and Aida64 has not. Thanks for the explanation, this makes sense.
On the support side, Aida has been very quiet as of late. Some of the paid customers have filed tickets about this issue and never received a response. Me included. So naturally it's going to be frustrating to your customers when we don't get any answers, good or bad. Microsoft has Hundreds of doors to bang on (which door do we bang on?), and a good majority of your customers don't know the difference and/or won't be able to explain what is happening clearly in a support ticket to Microsoft. Lots of people don't understand testing methodology, test environments, outside variables etc. So we come to you for help hoping that Aida can work with Microsoft as an advocate for us and for it's software. As a software developer myself, my team is always trying to find workarounds to problems outside of our control.
There are plenty of people, me included that would like to help test this bug with you and help narrow down a cause.
Maybe a good start would be to create a new Form Topic for incorrect CPU usage and have people post system specs, screen shots etc and start from there? That way support team could reach out.
Thanks for the temporary workaround in the next beta build. Let us know if you need any help diagnosing this issue in the future.