AMD Adrenalin 25.10.1 Pulled Mid Rollout: What Happened and Who Got Bitten

Downloading a driver the day it appears is not the same as installing it. That distinction is the whole story behind AMD Adrenalin 25.10.1, a package that went up, got pulled, and left a trail of half-updated systems behind it. If you clicked Install because the notification badge was there, you were part of the experiment.

Here is what I can piece together, and more importantly, what to do with a machine that already swallowed it.

What actually happened

AMD published Adrenalin 25.10.1 to the public download flow, then withdrew it partway through the rollout. This is not unique to AMD. It happens with every vendor eventually, and it almost always means the same thing: something in the package was bad enough that pulling it was cheaper than shipping a hotfix the same week. Sometimes it is an installer issue. Sometimes it is one GPU family. Sometimes it is a specific Windows build combination that slipped through validation.

What I cannot tell you, honestly, is the exact defect. AMD did not put out a detailed post-mortem I can point you to. Anyone claiming a definitive root cause without a citation is guessing. What I can tell you is the shape of these pull-backs, because I have watched this pattern on AMD and on the other side of the fence for years.

The important part for you is not the why. It is whether the driver is sitting on your disk right now.

Two groups of people, two different problems

There are really two situations here, and they need different handling.

You saw the update and did not install it

Good. Stay where you are. Nothing about a pulled driver requires you to act. Your current Adrenalin version keeps working, your games keep running, and the next stable release will show up in the companion app when it is actually ready.

If the update badge is still nagging at you, remember that Adrenalin checks through the AMD Install Manager, a separate utility it opens when you click the settings cog and then Manage Updates. If a pulled package is still cached there, you can simply decline the install. Do not force it through a manual download link you found on a forum. A withdrawn driver is withdrawn for a reason.

You already installed it

Then you need a plan, and the plan depends on what your machine is doing.

If the system boots, displays fine, and games run without artifacts, you may have dodged whatever the defect was. Not every card, not every Windows build, gets hit. Leave it alone and wait for the next stable release. Do not “fix” a working system out of paranoia.

If you are seeing stutter that started near the update, black screens, crashes, or a driver that fails to load at boot, your setup is showing the familiar fingerprints of a driver gone in wrong. The clean way out is a rollback first, and a clean install only if rollback is not available or does not stick.

The rollback path, done properly

Windows keeps the previous driver package in the driver store, which is why rollback works at all. Bring up Device Manager, unfold the graphics section, right-click your GPU, choose Properties, switch to the Driver tab, and hunt for Roll Back Driver. If it is greyed out, Windows has already discarded the old package and you are going to need a clean install instead.

A few things that trip people up here. Rollback only works if you have not run a disk cleanup that removed old driver packages, and only if you have not manually installed over the top several times. If you have done either, plan for the clean route.

One more thing: rollback restores the driver, not your Adrenalin tuning. Your undervolt, fan curve, and FreeSync settings may need to be reapplied. Annoying, but it is a five-minute job.

When a clean install is the right call

If rollback is unavailable, or you rolled back and the problem came back, you want a clean install of a known-good older Adrenalin release. This is the one scenario where I reach for Display Driver Uninstaller.

DDU strips the driver stack, the leftover registry entries, and the driver-store packages that a normal uninstall leaves behind. Those remnants are exactly what causes a new install to fail or misbehave. The current build, 18.1.5.6.0, also changed how it handles laptop driver extensions: it leaves vendor tweaks in place on Intel and Qualcomm machines out of the box, since stripping them can keep the GPU from ever coming up and hand you a Code 31. On a laptop, do not override that default unless you know exactly why you are doing it.

The safe order:

  • Download the older Adrenalin package from AMD first, while you still have a working display driver.
  • Disconnect from the network so Windows Update cannot shove a driver back in mid-process.
  • Run DDU, pick your graphics card vendor, then let it wipe and reboot. The low-resolution screen after reboot is normal.
  • Still offline, run the AMD installer. Choose Full Install.
  • Reboot, then reconnect the network.
  • Reapply your Adrenalin settings.

Do not skip the offline part. Windows Update has a bad habit of installing an older or mismatched GPU driver on its own, and it will happily do it while you are trying to fix things.

Should you ever install a fresh AMD driver on day one?

My honest take: not on a machine you depend on. Wait a week. Let the early adopters find the landmines. This is not a knock on AMD specifically. A pulled release is a normal cost of doing business in driver land, and it happens across every vendor.

The exception is when a specific game or feature you need is broken and the new driver fixes it. In that case, install it, but keep the previous installer on disk so you can get back. That single habit saves more headaches than any tuning guide.

If you are mid-rollout casualty right now, the order of operations is simple. Stutter or crashes near the update, roll back. Rollback unavailable, DDU and clean install the last stable version. Working fine, do nothing. Wait for AMD to ship the next stable Adrenalin and check the release notes before you click install this time.