By your own explanations you're pointing that it's NOT AMD's fault.
You yourself said more than one time that the AMD driver (that may be contributing to the problem but may also not be the only culprit) was working as intended on Microsoft's current OS, Windows 10, probably following Microsoft's guidelines. You yourself is saying that AMD's driver is working.
What changed, the driver or the OS?
Yes, the OS.
It's AMD's fault if some new feature that should be for exclusive use by a future rival's product that wasn't even launched yet is causing problems for it's CPUs? Something that AMD have no ways to control, nor say in how that new feature should work?
The most that AMD can do is pay attention to "bugs" on the development builds and ask Microsoft to fix it, and we have evidence that this was done and it was working as it should in recent builds. It's AMD's fault if Microsoft launched W11 on a broken build? That they did this giving zero warnings to the users? Why wasn't the fix available at day 1 if it was already available?
A new driver by AMD is not a fix, it's a workaround.
And isn't concerning that Microsoft rushed a new OS that may have changed rules about how drivers should be made and may cause problems for many others besides AMD?
You are confusing two different things here. There are two separate performance related issues with AMD and Win 11 right now. One is the scheduler (that's on MS, but I'm highly surprised AMD didn't notice this before or after RTM and the actual release) and then there is the UEFI issue that is on AMD for not updating the driver before launch.
No, I'm pointing out the UEFI issue IS AMD's responsibility. It is their driver/software to maintain and did not update it before the release and upon release, issued a KB letting users know they were aware of the issue and working on it.
Let this sink in, why aren't you still using drivers from Windows Vista or past OSs? By nature, things change within the OS during development because code is update, changed and added. This can and does cause functionality issues with old drivers that are based on the code of an older OS. The OS change, but the driver did not change with it! MS isn't responsible for the software/driver.
The UEFI issue has nothing to do with the issue that Microsoft is working on for the scheduler picking the highest performing cores.
No, it's not concerning that Microsoft "rushed" a new OS. This OS has been known about for a long time and AMD had the ability to work on their UEFI issue well before after launch.
Notice on how September 20th, nVidia released finalized version of Windows 11 drivers? Other companies did too, but this is an example.
Nvidia released updated Game Ready and Studio drivers for the final version of Microsoft's Windows 11 operating system today.
www.ghacks.net
"he company did release its
first Windows 11 ready drivers back in July, but the drivers released today are designed for the
final version of Windows 11, which Microsoft plans to release on October 5, 2021."
It's amazing that another company can release finalized drivers several weeks before the actual launch of Win 11. you know, cause Microsoft rushed the OS and everyone was caught by surprise!
Regardless of all of this, the fix is company and this isn't really a huge deal in the grand scheme of things.