Friday, May 22nd 2026

AMD Updates "Polaris" and "Vega" GPU Drivers With Adrenalin Edition 26.5.2 Version

AMD has released a new GPU driver update for its older "Polaris" and "Vega" GPU architectures, which are now almost a decade old. The latest Adrenalin Edition 26.5.2 drivers, released a few days ago, are specifically designed for these two architectures, which were AMD's popular gaming GPUs before the RDNA 1.0 generation. Interestingly, the Adrenalin Edition 26.5.2 driver update for "Polaris" and "Vega" GPU architectures includes only a single fix: resolving an application crash issue in Apex Legends on Radeon RX 400/500 series graphics cards. No other changes have been made, aside from updating this driver version from the August 2025 release of Adrenalin Edition 25.8.1 for these two GPU architectures.

Officially, the driver supports Radeon RX 400, Radeon RX 500, Radeon 500X, Radeon RX Vega, Radeon VII, Radeon Pro Duo, and Radeon 600 Mobile GPUs, which encompass all the series AMD released based on these GPU architectures. As some may recall, AMD's "Polaris" debuted in 2016 for OEM systems and appeared in 2017 for gaming GPUs, while the "Vega" GPU generation lasted until 2019, with the Radeon VII being AMD's last release. Although these GPU architectures have been replaced by RDNA, they have lost some relevance, but there are still millions of these GPUs in use worldwide, prompting AMD to issue a few final fixes like the one we see today.
Sources: AMD, via VideoCardz
Add your own comment

35 Comments on AMD Updates "Polaris" and "Vega" GPU Drivers With Adrenalin Edition 26.5.2 Version

#2
Event Horizon
Strongly recommend switching to Linux if you have those GPUs as they're still getting performance work in RADV.
Posted on Reply
#3
Kwadratowicz
Trrrryt
lexluthermiesterI thought they retired Polaris?
It looks like they just releasing 2-3 updates per year.
RX 470 Win 11 driver release dates:
Adrenalin 26.5.2 (WHQL Recommended)
2026-05-21

Adrenalin 26.1.1 (WHQL Recommended)
2026-01-21

Adrenalin 25.8.1 (WHQL Recommended)
2025-08-04

Adrenalin 25.5.1 (WHQL Recommended)
2025-05-08

Adrenalin 24.9.1 (WHQL Recommended)
2024-10-01

Adrenalin 24.3.1 (WHQL Recommended)
2024-03-20

Adrenalin 24.1.1 (WHQL Recommended)
2024-01-23
Posted on Reply
#4
JustBenching
lexluthermiesterI thought they retired Polaris?
They did, retired drivers always fix issues present with the latest official ones. They just don't add anything new or improve performance and compatibility in new games.
Posted on Reply
#5
cucol
B-b-b-b-b-b-b-but they told us they had been abandoned...

How can that be?
Posted on Reply
#6
Fouquin
AleksandarKwhile the "Vega" GPU generation lasted until 2019
The latest Vega GPU released in February 2025 when AMD refreshed Cezanne (Zen 3) APUs for the second time.
Posted on Reply
#7
JustBenching
cucolB-b-b-b-b-b-b-but they told us they had been abandoned...

How can that be?
They are, that's how retired drivers has always worked. No new features or performance in newer games, just fixing bugs present on the latest stable
Posted on Reply
#8
Chrispy_
I'm going to assume that the lack of bugs that need fixing in these old architectures directly correlates with the amount of bugs already resolved, and the amount of experience game devs and engine devs have with these.
Maybe there aren't problems because everyone in the industry know what to do and what not to do?
Posted on Reply
#9
_roman_
Event HorizonStrongly recommend switching to Linux if you have those GPUs as they're still getting performance work in RADV.
I cant and won t do o my refurbished noteobok. Too much hassle to deal with ubuntu / debian derivatives.
when you dealt years with the limited package manager which does not allow parallel installation / uninstallation / package manager usage -> N O P E

-- I wonder if my rzyen 4650u is covered under that. I suppose. The driver is years old for the amdgpu in windows 11 pro

epic game store did not launch several months ago, last time i tried on my 20 year old gnu gentoo linux installation. i know it too well all those limiations since kernel 2.0.0

-- I suppose this is more a CVE release than anything else. Good :) I will test a few weeks later if it applies for the ryzen 4650u or not.
FouquinThe latest Vega GPU released in February 2025 when AMD refreshed Cezanne (Zen 3) APUs for the second time.
that sounds like the driver date i had to download manually as windows 11 pro can not download any gpu drivers properly for 4.5 yera old lenovo business laptops

--

It seems they have a hidden url.

www.amd.com/en/support/downloads/drivers.html/processors/ryzen-pro/ryzen-pro-4000-series/amd-ryzen-5-pro-4650u.html
Kinda interesting that windows update does not pulled the older releases.

2024-10-01 vs 2025-05-08 vs 2025-08-04 vs 2026-01-21 vs May 2026. Not that worse in regards of amd driver quality and releases.

-- those steam deck ownres etc should talk if it is this gpu architecture nor not!
i disagree with that " they have lost some relevance, " - there are millions of business notebooks in the wild with ryzen apus
Posted on Reply
#10
windwhirl
lexluthermiesterI thought they retired Polaris?
For the most part. Updates are only for bug fixes (not many bugs left at this point), security issues (? Haven't ever seen one mentioned so no idea what security issues there might be) and the occasional "make sure the driver works with a newer Windows version" that also doesn't get mentioned but happened at least once.
Posted on Reply
#11
Chrispy_
I guess they can't really abandon Vega drivers just yet. They launched "brand new" Ryzen 7000 products with Vega IGPs in 2023 and those were legally defined as "current products" until superseded by the 8000-series in December 2026. Since AMD must legally honour their 3 year warranty, the earliest they can get away with dumping Vega driver updates is December 2026, though even then they'll presumably need to negotiate with OEMs who have sold 5-year extended warranties to their customers?

I don't know how much work it is to maintain a driver but I'd imagine maintaining the driver is less effort than renegotiating deals with Acer, Asus, Dell, Clevo, Compal, HP, Lenovo, MSI, Supermicro, and probably dozens of smaller OEMs making laptops, mini-PCs and possibly gaming devices.

Or maybe not. Maybe OEMs selling extended warranties take on the risk of customer backlash past the point that the primary hardware support officially expires.
Posted on Reply
#12
Aquinus
Resident Wat-man
I still use a Vega 64 in my tower in both Windows and Linux. Works great for what I use it for.
Posted on Reply
#13
windwhirl
Chrispy_though even then they'll presumably need to negotiate with OEMs who have sold 5-year extended warranties to their customers
Eh. If it's anything like the driver updates some AIBs do, OEMs most likely don't update anything unless they have to. The warranty is for stuff breaking, not a promise of stuff getting updates all the time
Posted on Reply
#14
Chrispy_
windwhirlEh. If it's anything like the driver updates some AIBs do, OEMs most likely don't update anything unless they have to. The warranty is for stuff breaking, not a promise of stuff getting updates all the time
Yes and no. If you buy hardware to do a job and that job cannot be done with a current, security and audit-compliant driver, then that product is no longer fit for purpose as sold.

Warranties are for manufacturer defects, but AFAIK the mandatory warranty enforced by some governments include more than manufacturer defects - they entitle the buyer to an exchange or partial refund if the product ceases to operate as sold before the warranty runs out.

This is a much greyer area with software though, and outdated drivers that can't keep up with the moving target of "current software" might not fall foul of legislation the same way as, say, shutting down a cloud service for some hardware that then loses some functionality without workarounds or alternatives.
Posted on Reply
#15
MikOnTopGG
So my RX 580 will still receive driver support?
Posted on Reply
#16
Dr. Dro
lexluthermiesterI thought they retired Polaris?
GCN 4/5 remains on a legacy support status, the driver branch is ancient (23.19), but AMD has loosely maintained it because they still actively manufacture and sell products with this GPU IP.
cucolB-b-b-b-b-b-b-but they told us they had been abandoned...

How can that be?
There are no new features and no major bug fixes included. Fixes targeting newer hardware do not apply. I understand the confusion and I have explained at length on the forums: AMD releases three different drivers under the same name, an almost deceptive practice, especially since they have taken active steps to hide this.

23.19 for GCN4/5
25.10 for RDNA 1/2
26.10 (or whatever is most current) for RDNA 3/4

They are completely different internally
Posted on Reply
#17
Rulumi
Well, as said here already from other users AMD is actually just being deceitful since the whole RDNA 2 maintenance mode drivers outrage from people, to keep people calm even if they haven't actually changed course of how they are managing it or other "Maintenance Mode" (legacy) driver branches, they stopped listing the actual driver version to make people think all of them are updated in the same way. In fact and specifically for this "AMD Software: Adrenalin Edition 26.5.2 for Polaris & Vega" release real driver version: "2605200757-23.19.25.01-260423a-201039C-AMD-Software-Adrenalin-Edition"

AMD only is issuing security fixes and the occasional application and software bug fix for Polaris and Vega. No new major driver code fixes or improvements, no major features or compatibility, no kernel mode driver updates, no API updates (for example Vulkan is stuck at 1.3.260, but that applies to other graphic APIs updates too and this kind of actually does affect performance and compatibility), basically no major updates or back-ports to note. It's a bit funny of the versions and packages actually because AMD is making like 4 (5 or 6 with Pro drivers) now because all of this as follows:



1) 23.19 branch based driver package for Polaris and Vega.
2) Standalone 25.10 branch based driver for RDNA 1 and RDNA 2 (-a package).
3) Current updated branch driver for RDNA 3/.5 and RDNA 4 (-b package).

4) Combined package with 25.10 for RDNA 1 and 2 and current branch for RDNA 3/.5 and 4 (-c package).
The driver will install the corresponding one based on the system hardware. If mixed architectures this installs both with their own instance for the different driver, which really is something that just doesn't work well in Windows, problem to note because this usually causes a lot of problems in such mixed combinations in systems with integrated RDNA 2 graphics and a RDNA 3 or RDNA 4 dGPU unless you disable the integrated graphics, and such situation happens with all current non F desktop Zen 4 and Zen 5 systems.

5) Separate 25.10 branch based driver AMD Software: PRO Edition driver for RDNA 1, 2, and 3 Radeon PRO systems and based integrated Ryzen PRO systems, including RDNA 3.5 ones like Strix Halo. No RDNA 4 support at all including the Radeon AI PRO products, you have to use normal Adrenalin drivers with Radeon AI PRO products (example: R9700).
This driver is nowdays restricted to these Radeon PRO and Ryzen PRO systems only because AMD choose to, so it'll refuse to install and work with consumer models now. It is obvious AMD is aware of the issues that the two instances loading can cause so they ship for now an unified 25.10 for these PRO branded products. (Aside note, technically there's also a PRO package for Vega and Polaris mostly intended for Ryzen PRO systems with Vega graphics that mostly corresponds to the 23.19 branch based one for Polaris and Vega, I think that one may actually still install on consumer models)

In fact there are actual remnants of more proper and honest explanations of the Maintenance mode driver situation in one of the driver packages, which I think AMD may just have forgotten to remove because they actually went out of their way to remove it in the standalone package. Again they are being deceitful in purpose after the Maintenance mode driver announcement fiasco without actually changing much or anything of the RDNA 1 and RDNA 2 situation apart from there being sometimes monthly minor bugfixes. But it seems their strategy has worked and most common users have been deceived and appeased despite not changing much of the situation, so I guess they achieved their goal.


Posted on Reply
#18
Readlight
Atleast back then graphic cards was afordable almos 100-200 euros.
Posted on Reply
#19
Youseethis
It wouldn't be a problem to be on an older branch IF there was not much optimization available in the first place OR new features. Same thing with bug fixes, if there is nothing to fix...
Now, the problem with Vega is that some new games throw errors at you. The latest example is Forza Horizon 6.

Also I just tested the driver. The resizable bar trick remains broken. So this driver compared to 24.9.1 remains inferior. The difference for forza horizon 5 by the way was more than 10% with rebar on.
Finally, the drivers for vega are so neglected that amd forgot to put the usual release notes on 26.1.1.
Posted on Reply
#20
Ols-Hol
Is there any way to get these new (or "new") Vega drivers working alongside the current drivers for RDNA 3/4 dedicated cards?

I was wondering if you can still make desktop hybrid graphics work on AM4. In such situation, your integrated graphics would be a Vega core, but when you want to use a recent dedicated Radeon card, their current drivers (for example www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-26-5-2.html) only provide support for the rdna/rdna2 branch and rdna3/4 branch.

Currently I can get RDNA2 integrated graphics on AM5 working with a Radeon RX 7700 XT, because of that. And when I open device manager, I can see that the dedicated GPU uses driver version 32.0.31007.5012 while the integrated uses 32.0.21043.10005 which are both in the 26.5.2 package linked above. When I tried to install a driver that lacked the branch for one of the GPUs, it would not work (RDNA3/4 only driver would result would show driver error on the RDNA2 iGPU in device manager. However, as long as you stick to drivers that package both branches, you are OK.

On AM4 though, Vega/Polaris iGPU would require the 31.0.21925.1001 driver from this package www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-26-5-2-POLARIS-VEGA.html which lacks the newer branches for RDNA1/2 and RDNA3/4. I don't think there is a way to sneak that driver into the system alongside the RDN3/RDNA4 driver?
Posted on Reply
#21
Dr. Dro
YouseethisIt wouldn't be a problem to be on an older branch IF there was not much optimization available in the first place OR new features. Same thing with bug fixes, if there is nothing to fix...
Now, the problem with Vega is that some new games throw errors at you. The latest example is Forza Horizon 6.

Also I just tested the driver. The resizable bar trick remains broken. So this driver compared to 24.9.1 remains inferior. The difference for forza horizon 5 by the way was more than 10% with rebar on.
Finally, the drivers for vega are so neglected that amd forgot to put the usual release notes on 26.1.1.
Yes. Nothing that requires touching the kernel mode driver will be changed going forward, even if it's broken as you've mentioned. It's feature frozen. The RDNA 2 cards are in the same precarious situation. May see slightly better treatment because it's much more capable hardware and so many people still use it, but it's about the same thing.
Ols-HolIs there any way to get these new (or "new") Vega drivers working alongside the current drivers for RDNA 3/4 dedicated cards?

I was wondering if you can still make desktop hybrid graphics work on AM4. In such situation, your integrated graphics would be a Vega core, but when you want to use a recent dedicated Radeon card, their current drivers (for example www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-26-5-2.html) only provide support for the rdna/rdna2 branch and rdna3/4 branch.

Currently I can get RDNA2 integrated graphics on AM5 working with a Radeon RX 7700 XT, because of that. And when I open device manager, I can see that the dedicated GPU uses driver version 32.0.31007.5012 while the integrated uses 32.0.21043.10005 which are both in the 26.5.2 package linked above. When I tried to install a driver that lacked the branch for one of the GPUs, it would not work (RDNA3/4 only driver would result would show driver error on the RDNA2 iGPU in device manager. However, as long as you stick to drivers that package both branches, you are OK.

On AM4 though, Vega/Polaris iGPU would require the 31.0.21925.1001 driver from this package www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-26-5-2-POLARIS-VEGA.html which lacks the newer branches for RDNA1/2 and RDNA3/4. I don't think there is a way to sneak that driver into the system alongside the RDN3/RDNA4 driver?
You have to install both. What I'd do is install 26.10, and then extract and install 23.19 through the device manager. That way you'd get the latest driver's Adrenalin control panel, and a way to communicate with the old hardware. But it might not work. I haven't really been able to test that for some time.
Posted on Reply
#22
Lew Zealand
YouseethisIt wouldn't be a problem to be on an older branch IF there was not much optimization available in the first place OR new features. Same thing with bug fixes, if there is nothing to fix...
Now, the problem with Vega is that some new games throw errors at you. The latest example is Forza Horizon 6.

Also I just tested the driver. The resizable bar trick remains broken. So this driver compared to 24.9.1 remains inferior. The difference for forza horizon 5 by the way was more than 10% with rebar on.
Finally, the drivers for vega are so neglected that amd forgot to put the usual release notes on 26.1.1.
RandomGamingInHD yesterday tested FH6 with his Ryzen 5600G iGPU and needed to revert back to a significantly older driver to get it to work (June 2023) as Vega isn't officially supported despite relatively current drivers. He only mentioned initially trying "the latest drivers" but assuming a day or 3 of video lead time, it's likely they weren't these 26.5.2 drivers but it's unlikely these newer ones will deliver a different experience.
Posted on Reply
#23
_roman_
RulumiWell, as said here already from other users AMD is actually just being deceitful since the whole RDNA 2 maintenance mode drivers outrage from people, to keep people calm even if they haven't actually changed course of how they are managing it or other "Maintenance Mode" (legacy) driver branches, they stopped listing the actual driver version to make people think all of them are updated in the same way. In fact and specifically for this "AMD Software: Adrenalin Edition 26.5.2 for Polaris & Vega" release real driver version: "2605200757-23.19.25.01-260423a-201039C-AMD-Software-Adrenalin-Edition"

AMD only is issuing security fixes and the occasional application and software bug fix for Polaris and Vega. No new major driver code fixes or improvements, no major features or compatibility, no kernel mode driver updates, no API updates (for example Vulkan is stuck at 1.3.260, but that applies to other graphic APIs updates too and this kind of actually does affect performance and compatibility), basically no major updates or back-ports to note. It's a bit funny of the versions and packages actually because AMD is making like 4 (5 or 6 with Pro drivers) now because all of this as follows:
hmm
my personal install logs of my box says - do not mix up with when the software was released or put on the servers!

Fri May 26 16:15:21 2023 >>> dev-util/vulkan-headers-1.3.246
merge time: 4 seconds.

Thu Jun 15 11:33:02 2023 >>> dev-util/vulkan-headers-1.3.250
merge time: 6 seconds.

Thu Aug 31 13:34:59 2023 >>> dev-util/vulkan-headers-1.3.261
merge time: 6 seconds.

Mon Nov 27 22:30:38 2023 >>> dev-util/vulkan-headers-1.3.268
merge time: 6 seconds.

So amd ships 3 Year old software stack, really?

-- your screenshot hurts. I bought myself a radeon 6600xt and 6800 non xt and sold them. not that long ago. if the msi 6800 z trio would not have been such a garbage, I would not have sold it after 3 months and bought 3 months later the powercolor 7800xt hellhound. no driver support for recent harware, as shown by the screenshot. you need older driver branch


--

I never tried it, but motherboard uefi etc. advertise to use the cpu graphic and enhance it with a dedicated amd grpahic card. how shall that work when the cpu graphics never gets any updates and has lower hdmi and dp specifications? those hybrid graphics shall safe power or have other reasons. the core arguemnt is, you need working driver when you want to use the graphic outputs of the cpu on an amd motherboard with newer amd graphic cards. they need the same driver branch and same software stack. interesting what i see posted above me and what i maybe see between the lines.
Posted on Reply
#24
lexluthermiester
_roman_So amd ships 3 Year old software stack, really?
Older does NOT mean useless or unstable. It usually means quite the opposite. 3 years is not very long ago , but it's long enough for the code in question to have had plenty of time to be examined, optimized and refined.
Posted on Reply
#25
Dr. Dro
_roman_So amd ships 3 Year old software stack, really?
...yes, that is what 23.19 is. A 3 year old driver, minimally patched to ensure full compliance with the latest versions of Windows. AFAIK the code split happened sometime around the release of what they call "23.9.1"
lexluthermiesterOlder does NOT mean useless or unstable. It usually means quite the opposite. 3 years is not very long ago , but it's long enough for the code in question to have had plenty of time to be examined, optimized and refined.
I kinda have to disagree, for a graphics driver, three years is enough to consider it archaic, especially if you happen to be a gamer that plays the newest games out there or if you enjoy the latest generation codecs and stuff. AMD's software suite from back then just about makes a competent enough iGPU driver, though, which is pretty much the intent here anyway.

How long can AMD keep up with the façade until the cracks start to show is what I really think about. Development is clearly fractured, and having to maintain three different versions is very difficult unless you've got bottomless engineering and R&D resources. As mentioned earlier, 23.19 is already causing problems with some of the latest games.

This will begin to manifest with Nvidia 900/10 series GPUs sooner rather than later, they don't quite yet have problems, but some of the latest games already warn about the previous branch (R580) drivers being out of date, for example Subnautica 2. The game runs, but there are no guarantees that future versions will be fully compatible with, or optimized for these drivers.

Posted on Reply
Add your own comment
Nov 21st, 2026 16:21 PST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts