Windows 11 available on October 5

Barman58 said:

It looks like this was a driver issue, so would be something that AMD wold be responsible for, Microsoft does not and has never written drivers for other than Microsoft hardware. Microsoft will include others hardware drivers in the os or updates for convenience of users

Yes, HW manufacturers always submit drivers to OS developers to include in their OS. Only HW manufacturers know all details needed for it's exploitation and tend to keep close lid on HW "secrets" because of industrial espionage. Still there has to be close cooperation of MS and HW makers as MS provides important links between drivers and Windows in form of conditions and APIs, .DLLs, :NET version and other runtime applets.
In order to make a piece of HW work at all during Windows clean installation drivers included in Windows installation set they have to be very simple (comparing to full drivers) or their updates to cover whole series of similar HW. Other step is for drivers included for distribution thru Windows update which are more detailed with some of most important application for their control bur more than often than not they are still simpler and smaller than full fledged drivers available thru HW manufacturer.
So, as simple as it may sound, a Driver is very complicated thing to implement properly and fully.
Actually, "drivers" are just small part Driver Package released from HW manufacturer available for general download and most of time encompass drivers for similar products in one package. That's why such downloaded drivers are much larger than need be although only small part is changed/updated and used for update.
In this particular case with AMD, there's apparent miscommunication between AMD and MS that has to be resolved with effort from both sides at same time and solution may have to come from both sides. It's pretty obvious that MS changed some conditions between Insider developer version and release version of which AMD was either unaware or failed to respond in timely manner. Looks like patch for Beta is already in effect so should be coming to release version in short order.

The other thing that has to be considered, as far as I know this issue is not happening with all systems using an AMD processor and Windows 11 - I did not notice any issue on my system though most of the time the 5950 Processor in my system is running at less than 50% except when I am performing major image processing so is not a true test.

Obviously if you are unlucky enough to have the maximum 15% power loss reported by some with some games it is not good and needs to be corrected quickly. The problem in modern computing systems used for Windows is the variability - it could be any hardware component or software code that is the cause - It could easily be a driver for something not even related to the processor, causing interference.

These things may take a little time - why it happens only after the RTM release is unknown but could be due to an RTM issued driver for some other component or subsystem. It's annoying and not good for MS, AMD, or most importantly the users, but it can take time

pietcorus2 said:

Again ..........again and ....again , many reasons for waiting upgrading to 11...........

Many MANY reasons to skip to a Linux distro! (Got my eyes on Zorin OS!)

RingTailCoon said:

Many MANY reasons to skip to a Linux distro! (Got my eyes on Zorin OS!)

Zorin ??? No, not real replacement for Windows, use some serious Linux like Mint or Fedora. if you must.