AMD Releases Ryzen Chipset Drivers 4.06.10.651

[Uskompuf]

AMD has recently released new chipset drivers for Ryzen processors on a wide range of platforms including A320, B350, X370, B450, X470, X399, A520, B550, X570, TRX40, and WRX80 that are running Windows 10 & 11. The new drivers include additional program support, display & airplane mode notifications, Ryzen 9 Mobile improvements, and various bug fixes. This latest release also sees the introduction of six new drivers including official USB 4.0 support, the complete changelog and download link can be found below.

Download: AMD Ryzen Chipset Drivers (4.06.10.651)





Release Highlights

• New program support added.
• Six new drivers added.
• Fixed pop-up message "AMD Chipset Software is not responding" when the installer is launched and UI screen is clicked.

Known Issues

• Sometimes custom install fails to upgrade to latest drivers.
• Text alignment issues may be seen on Russian language.
• Manual system restart required on Non-English OS after the installation is complete.
• Windows Installer pop-up message may appear during the installation.
• Uninstall summary log may incorrectly show uninstall status as fail on non-English OS.

View at TechPowerUp Main Site | Source

 

[Ferrum Master]

Buggy installer as usual.

I had to do manual and put the source exes on D drive as their script asks to properly do inf update.

 

[Ibizadr]

Buggy installer as usual.

I had to do manual and put the source exes on D drive as their script asks to properly do inf update.

Buggy again? Wtf AMD, second time in a row

 

[Sake]

Buggy installer as usual.

I had to do manual and put the source exes on D drive as their script asks to properly do inf update.

For me, not.

 

[TheLostSwede]

Buggy installer as usual.

I had to do manual and put the source exes on D drive as their script asks to properly do inf update.

Had zero issues. In fact, never had an issue with their driver installer.

 

[usiname]

Buggy installer as usual.

I had to do manual and put the source exes on D drive as their script asks to properly do inf update.

Check the device behind the keyboard, that is usually the problem

 

[Ferrum Master]

Thanks for your kind support and feedback.

 

[trsttte]

Check the device behind the keyboard, that is usually the problem

The screen?

 

[ARF]

Had zero issues. In fact, never had an issue with their driver installer.

I have issues on my PC with Ryzen 9 5900X and the MSI MAG X570 Tomahawk - the installer refuses to proceed, at all, so for me it's impossible to continue the installation.

My guess is that it is because I deleted these folders from my C:/ drive:

 

[usiname]

The screen?

If behind your keyboard is the screen then you have serious problem with the orientation

 

[Divide Overflow]

Buggy installer as usual.

Zero installation problems for me as usual.

 

[Ibizadr]

I think some people don't understand what he means with bugged driver. To me in last release after the instalation computer becomes weird and it happens to other people too. So many of us passed last update.

 

[magician2905]

Never had an issue with Chipset Drivers before.
Startup was slow with drivers and programs slow to start.
These made my system run terribly. Everything was slow to load a web page took upto 1 minute to load.
Even installing the previous version took nearly 30 mins to complete.
On checking Processes/Resource Use in Task Manager these drivers were hammering my GPU with massive power use for no good reason.
Once rolled back everything is snappy and fine.
DO NOT INSTALL THESE DRIVERS.
Win 10, Ryzen 5800X, MSI MAG Tomahawk X570

 

[LifeOnMars]

No issues here, smooth as always. B450 Asrock board.

 

[Tomorrow]

No problems here. Install went smoothly with X570 Aorus Master 1.0 (BIOS f36c) and 5800X3D.
This on my half broken Win10 2009/20H2 install.

All values are normal tho it did reset my High performance power plan modification (my disabled Idle state was enabled again after the update).
I did not touch any folders on disk and i made sure Workstation service was running as having this disabled can cause issues with the installer.

 

[olymind1]

Uninstalled previous driver, restarted, installed this one, install was successful (according to the installer), but the log said only 2 out of the 6 driver were installed, the rest failed. Restarted. Run the installer again, now 6 of 6 driver was install successfully according to the log.

Previous drivers did similiar failures, so there is definietly something wrong with their installer. There wasn't any driver installation failure while i was on Intel.

 

[Makaveli]

The screen?

lol I don't know about your setup but generally the keyboard is front of the screen not behind.

 

[Tomorrow]

Uninstalled previous driver, restarted, installed this one, install was successful (according to the installer), but the log said only 2 out of the 6 driver were installed, the rest failed. Restarted. Run the installer again, now 6 of 6 driver was install successfully according to the log.

Previous drivers did similiar failures, so there is definietly something wrong with their installer. There wasn't any driver installation failure while i was on Intel.

I did not uninstall anything prior to installing the new one. I did do a restart just in case tho even that's not necessary.

 

[LabRat 891]

Last release was a bit of a PITA to get installed, but 99% sure that was my fault. (I'd recently tried out a 3rd party video driver that included a modded PCI driver).
Will give these a go.

 

[Dave65]

I must be lucky, never had any problems with AMD drivers in quite a long time.. This one went smooth for me!

 

[Ferrum Master]

I think some people don't understand what he means with bugged driver. To me in last release after the instalation computer becomes weird and it happens to other people too. So many of us passed last update.

What kind to elven language you have to use, when I said INSTALLER? It ain't about the drivers itself. Some people really just post because they don't understand.

I can write off the issues to certain W11 builds and the working ones are using w10.

Are we all happy misters everything is fine? It is like windows works for everyone the same and everyone has the same software/hardware config. It ain't Apple. sheesh.

My guess is that it is because I deleted these folders from my C:/ drive:

I had close. Just look at the error log and put the files where it wants. Plan B is to use Windows magic add drivers button. The mojo factor is that I don't know if it the installer adds special registry settings besides the drivers. Just my wild guess.

 

[Cutechri]

I wonder how many more security vulnerabilities AMD added to their crappy drivers this time?

 

[Tomorrow]

I wonder how many more security vulnerabilities AMD added to their crappy drivers this time?

Problably less than the amount that remain in Intel's.

 

[Mussels]

Zero issues on my three AM4 systems



If you have constant issues, i'd be blaming any driver cleaner programs you have for trashing them and reinstalling a non-broken OS

I have issues on my PC with Ryzen 9 5900X and the MSI MAG X570 Tomahawk - the installer refuses to proceed, at all, so for me it's impossible to continue the installation.

My guess is that it is because I deleted these folders from my C:/ drive:

View attachment 252779

Thats literally where the drivers are unpacked to, and install from

 

[olymind1]

If you have constant issues, i'd be blaming any driver cleaner programs you have for trashing them and reinstalling a non-broken OS

Doubt it, just last week i installed a fresh windows on a new NVMe SSD after upgrading from SATA. After fresh Windows install the previous chipset driver also failed to install propery the first time. Same goes for this new driver, it didn't matter for the installers if i was using SATA or NVMe SSD, or i used 3600X or 5600 this year, or 2600 in 2020 with older chipset drivers. Sadly there is something always up with the chipset driver installers, i am not the only one who experience this, luckily my system is rock stable, no other anomaly other then an occasional failed chipsed installs.