A faulty graphics driver update from AMD is leaving some Windows 10 users with non-functional Radeon GPUs, the company confirmed late Thursday. The problematic software—AMD Software: Adrenalin Edition 26.6.2—can corrupt the installation of Radeon drivers, triggering a yellow warning triangle in Device Manager and rendering the graphics card unusable until users roll back to a previous version. AMD has acknowledged the issue publicly and is advising affected customers to immediately revert to the Adrenalin 26.6.1 driver while it investigates the root cause.
The scope of the damage is still emerging, but early reports indicate the bug strikes across multiple Radeon RX series, from aging Polaris-based cards to the latest RDNA 3 silicon. The timing is especially painful for PC gamers and productivity users who rely on stable GPU performance. With no hotfix yet available, the only safe path forward is a manual driver downgrade—a process that, while relatively straightforward, often catches less technical users off guard.
What Went Wrong
Adrenalin 26.6.2 arrived as a routine maintenance release, promising minor stability improvements and game optimizations for titles like Horizon Forbidden West and Senua’s Saga: Hellblade II. Within hours of its publication on AMD’s website, however, users began flooding community forums and Reddit with reports of black screens, system freezes, and—most critically—graphics adapters showing error code 43 in Device Manager. That code, per Microsoft’s documentation, indicates “Windows has stopped this device because it has reported problems.”
Anecdotal evidence suggests the issue is not universal. Many installations proceed without a hitch, but for the unlucky subset, the driver appears to leave behind broken registry keys or improperly signed components that Windows 10’s driver validation subsequently rejects. The result: no display output from the Radeon GPU, forcing a fallback to basic Microsoft Basic Display Adapter or, on systems without integrated graphics, an outright unbootable state until Safe Mode intervenes.
AMD’s Acknowledgment
In a post on the AMD Community forums, an employee confirmed that “AMD Software: Adrenalin Edition 26.6.2 can break normal Radeon driver operation on some Windows 10 PCs.” The statement stopped short of detailing the triggering conditions but promised a fix “as soon as possible.” The company also updated the driver’s release notes with a prominent warning and pulled the automatic update from the Adrenalin software’s in-app check, though the driver package remains downloadable from the official site—albeit with a cautionary banner.
“We are actively investigating reports of installation failures and GPU detection issues on Windows 10 with the 26.6.2 driver,” the spokesperson wrote. “For now, we strongly recommend that users roll back to the previous release, 26.6.1, or stay on any earlier stable version.” The advisory did not mention Windows 11, where the driver appears to function correctly, pointing to a possible Windows 10-specific regression.
Which GPUs Are Affected?
While AMD hasn’t published a formal list, user reports span a broad portfolio. Affected hardware includes:
- Radeon RX 7000 series (RDNA 3)
- Radeon RX 6000 series (RDNA 2)
- Radeon RX 5000 series (RDNA 1)
- Radeon RX 500 / 400 series (Polaris)
- Radeon Pro workstation cards (select models)
Curiously, some integrated Radeon Graphics in Ryzen APUs also join the casualty list, suggesting the bug may lie in a core component shared across the driver stack. Laptops with switchable graphics seem particularly vulnerable, as the driver often fails to properly enumerate the discrete GPU, leaving the system reliant on integrated graphics.
The Rollback Fix: Step-by-Step
AMD’s guidance is clear: immediately roll back to Adrenalin 26.6.1. For users who can still boot into Windows normally—perhaps because the primary display is connected to a secondary GPU or integrated graphics—the process is simple.
- Open Device Manager (right-click the Start button and select it).
- Expand “Display adapters” and locate your Radeon GPU. It may appear with a yellow triangle and the name “AMD Radeon RX …” or a generic “Microsoft Basic Display Adapter.”
- Right-click the affected entry and choose “Properties.”
- Go to the Driver tab and click “Roll Back Driver.” Follow the on-screen prompts. If the button is greyed out, Windows has no previous driver to revert to, and you’ll need the clean install method described below.
- Restart the system. On reboot, Windows should load the older driver.
For those who can’t reach the desktop because the corrupted driver prevents any display output, you’ll need to boot into Safe Mode. Reboot and repeatedly press F8 (or shift-click Restart from the login screen) to access the Advanced Startup Options, then select Safe Mode. Once in Safe Mode, open Device Manager and follow the same rollback steps.
If Rollback Isn’t Enough: Clean Install
A rolled-back driver may still carry corruption if the 26.6.2 installer left artifacts. To ensure a pristine environment, use Display Driver Uninstaller (DDU) to wipe all AMD driver traces before reinstalling 26.6.1.
- Download DDU from a trusted source (Guru3D, for instance) and the Adrenalin 26.6.1 driver from AMD’s website.
- Disconnect from the internet to prevent Windows Update from automatically installing a generic driver while you work.
- Reboot into Safe Mode (required for DDU’s full cleaning).
- Run DDU, select “GPU” and “AMD,” then click “Clean and restart.” The tool will remove every AMD display driver file, registry entry, and folder.
- After the reboot, stay offline, run the 26.6.1 installer, and choose “Factory Reset” during installation for an extra layer of clean setup.
- Reconnect and reboot once more.
The latest 26.6.1 driver remains fully stable and current enough for all modern games and applications. Users who prefer extra caution can stick with the WHQL-certified Adrenalin 24.12.1 from December 2024, but 26.6.1 has performed without a hitch for the vast majority.
Community Frustration Boils Over
Unsurprisingly, the incident has reignited long-simmering complaints about AMD’s driver quality. While the company’s recent track record has markedly improved—RDNA 3 launch drivers were a triumph compared to the rocky RDNA 1 debut—a zero-day driver bug that cripples GPUs is a stinging setback. On Reddit’s r/Amd, one user with a Radeon RX 7900 XTX lamented, “I trusted the auto-update and now my PC is a paperweight. This is exactly why people buy Nvidia.” Another, whose RX 6600 received the update through Windows Update’s optional driver delivery, noted, “I didn’t even install it manually—Microsoft pushed it. Now I’m stuck in Safe Mode for an hour.”
Several users reported that the bug corrupts the AMD External Events Utility service, leading to a cascade of failures in the Adrenalin control panel. “After rolling back, the control panel refused to open, reporting ‘No AMD graphics driver installed,’ even though Device Manager showed the correct driver,” wrote a forum member. The solution in those cases involved a full DDU pass plus a clean install of the chipset drivers as well, highlighting how deeply the corruption can burrow into system components.
A Pattern of Driver Hiccups?
Is Adrenalin 26.6.2 an isolated mishap or part of a larger trend? AMD’s 2024–2025 driver releases have been largely stable, but occasional stumbles do creep in. Last November, an Adrenalin 24.11.1 beta caused excessive power draw on RX 6000 cards, and January’s 25.1.1 introduced stuttering in Call of Duty: Modern Warfare III before being patched. The difference this time is the sheer severity: a driver that not merely degrades performance but physically prevents the card from being recognized is rare from any vendor.
Industry observers note that AMD’s aggressive unified driver architecture—supporting everything from integrated RDNA 2 APUs to high-end discrete GPUs in a single package—creates complexity. A change intended for one product line can inadvertently send shockwaves through others. With Windows 10 still commanding roughly 60% of all Windows installs according to Statcounter, a Windows 10–specific bug hits a huge segment of AMD’s user base, making the oversight particularly damaging.
Lessons for GPU Driver Updates
For end users, the episode underscores two perennial best practices:
- Never install a brand-new driver on day one unless you need a critical fix. Game Ready or Adrenalin drivers typically go through months of internal validation, but real-world diversity always unearths edge cases. Waiting a week for community smoke tests is free insurance.
- Use system restore points and backup drivers. Windows’ built-in System Restore can snapshot your driver state before an update. Third-party tools like DDU also let you export a driver package. In this case, a restore point created before installing 26.6.2 would have undone the damage in minutes.
Power users may also choose to disable automatic driver updates through Windows Update. While convenient, Microsoft’s hardware driver distribution mechanism can sometimes push vendor drivers without the vendor’s consent or testing, as this incident suggests. Blocking driver updates via Group Policy (on Windows 10 Pro and above) or the “Device Installation Settings” popup maintains hands-on control over what’s installed.
What AMD Must Do Next
The obvious short-term fix is a reissued 26.6.2 hotfix or a 26.6.3 that remedies the corruption. But AMD’s credibility demands more: a detailed post-mortem explaining what went wrong, how it evaded testing, and what mechanisms will prevent a repeat. The company’s software team has drawn praise in recent years for transparency and community engagement; a swift, thorough response would restore trust. Anything less risks feeding the “AMD drivers bad” meme that rivals eagerly exploit.
Meanwhile, the episode casts a shadow over the upcoming Adrenalin 26.7.0 preview driver with support for Windows 11 24H2 and new DirectX 12 Ultimate optimizations. If the regression stems from changes meant to enable those features, AMD may need to decouple the code paths more cleanly before that release.
The Bottom Line
AMD Software: Adrenalin Edition 26.6.2 is a defective update that should be avoided on Windows 10 until further notice. Affected users should roll back to 26.6.1 or perform a clean driver installation using Display Driver Uninstaller. The company is aware and working on a fix, but no timeline has been offered. For now, patience and a spare hour of tinkering are the only remedies. The incident serves as a stark reminder that even mature hardware ecosystems remain vulnerable to software missteps—and that the rollback button is sometimes the most valuable feature of all.