Yesterday, after months of wandering, absent communication and deafness to complaints from its customers, AMD finally launched its AMD Adrenalin 26.6.2 drivers. The nice surprise is that these pilots were expected in July 2026, so they arrived a few days early, that’s cool…! If they optimize support for a few games, the latter has completely taken a back seat with the arrival of support for FSR 4.1 to Radeon RX 7000. Needless to say that this episode of tension could have been avoided a long time ago, and that it is not impossible that it was the deserved shitstorm on this abandonment of support which forced AMD to review its plans, the recent TSME affair is a blatant example, or the voluntary lack of precision on the arrival of FSR 4.1 on RDNA 3.5 chips. It is a shame for AMD to proceed in this way and to evolve its communication according to the crises triggered, the embers of which must be extinguished. This harms him more than it helps him!
However, this launch yesterday was not a synonym of happiness for everyone, because there were some hiccups at the start. It was normal that there were broken eggs, it’s complicated to validate everything despite everything. Those who use Windows 10 have been confronted, not all of them anyway, with non-recognition of the card, massively in RDNA 3, but users report the same error on RX 9060 XT and on iGPU Ryzen 9000. If they switch back to AMD Adrenalin 26.6.1, the problem disappears, and for the moment this is the only course of action until AMD finds a solution after having recreated the problem. Because you understand that those running Windows 11 did not have this problem.
The firm said it was carrying out investigations, which will lead to the creation of a new pilot. For those in RDNA 3 and W10 affected by error code 43, be patient, your time will come, for the others, have you tested the driver and noted an improvement in quality compared to FSR 3, and increased performance despite everything despite the greater greed of FSR 4.1?
