As stated in the title: Where are the driver updates for AMD graphics cards?

I have a 7900XTX and haven't received a driver update since November 2024. Multiple large titles have come out since then which could really use help with driver timeouts, crashes, and general performance since November. I feel like AMD is reverting back to their old days of terrible communication and a terrible driver release schedule. The 7XXX series launch and driver support over the last two years of owning that card has really left a bad taste in my mouth as a consumer and makes me regret switching from Nvidia. Just wanted to see if this was just me or if the community feels the same in general.

Also, if they don't pass on FSR 4 to the 7XXXX series cards I think I'm done with AMD for graphics cards.

I am a complete and utter tech noob. I found an "how to" article on AMD's website on how to check for driver updates, but the "how to" guide shows a completely different AMD system screen than what I have. According to the article, you're supposed to click on AMD system settings, and then click on the update button to see if there are any available updates. I have a system button, but no where on there is an option to check for updates.

Clicking on show details, just opens a drop down menu of various providers and versions already installed.

I'm afraid to just manually download a driver from the AMD website, because if I screw something up, I won't be able to fix it.

Honestly, I feel like an idiot. I've spent months troubleshooting driver issues, stuttering, and Adrenalin crashes. I had BSOD and my computer would actually reboot while in game sometimes.... I thought I was safe because I had "Device Installation Settings" set to OFF in Windows.

Well, turns out this setting is complete bullshit. Windows still "ninja-installs" a generic driver the split second you reboot after a DDU wipe, even with that toggle off. It happens so fast you don't even see it, and then you install your actual driver on top of that mess. Result? Instant stability issues and weird errors.

The only way to actually fix it: Download your driver. Kill your internet. Physically unplug the Ethernet or disable your ethernet adapter / disable Wi-Fi. Run DDU in Safe Mode and restart. Install the new driver while OFFLINE.

Only then, put the internet back on.

Boom 💥, just did this and the difference is night and day, no more crashes in bf6, no more unstable UV and OC, 6800xt runs like a charm on latest drivers (26.5.1), awake screen from sleep works again...

If you're on AMD and fighting with your drivers, stop trusting the Windows toggles and just pull the damn plug.

EDIT: After going through the comments, I want to clear a few things up and own my mistake.

I didn't follow DDU's instructions to stay offline. I genuinely thought having Group Policy set to block drivers and the Windows toggle switched off was enough. Felt like I'd done everything right. I hadn't. Those settings are, bluntly, theater.

GPEdit and Device Installation Settings don't actually do anything

I trusted them for months. Turns out Windows just ignores its own rules. Even with Group Policy blocking driver installs and the toggle set to OFF, the second you reboot after a DDU wipe, the OS quietly pushes a generic driver anyway. You never see it happen. You think you're clean. You're not, and that's why Adrenalin keeps behaving weird.

Don't use the Auto-Detect tool

Just don't. Go to AMD's site, find your exact card, and download the full standalone package yourself (Adrenaline). Have it sitting on your desktop before you start the process.

The fix (no cable-pulling required)

Control Panel > Network and Internet > Network Connections > right-click your adapter > Disable.

The actual workflow:

Download driver > Disable network adapters > DDU in Safe Mode > Reboot > Install driver while offline > Re-enable adapters.

If Windows can reach the internet during that reboot, it will race you to the install and win. Disabling the adapter manually is the only way to guarantee it can't. Don't trust the toggles, they're simply not working. Windows doesn't care and bypass them.