It seems some AMD graphics card users are running into a frustrating bug. Windows Update is slipping in driver version 25.10.6 without a heads-up, and it’s leading to all sorts of headaches like random crashes and black screens.
One user says the switch hit while he was playing Company of Heroes 3. The display went dark, the game crashed, and when the system came back the Adrenalin interface showed Microsoft’s driver in the corner instead of the usual AMD version. Others on Reddit confirm the same pattern. The new driver appears through Windows Update, installs automatically, and breaks things that worked yesterday.
It’s especially rough on Windows 11 users, where updates in January and April this year stirred up similar messes, including blue screens of death on AMD setups. Even as late as June, people were dealing with crashes tied to updates like KB5063060, hitting games with anti-cheat software hard.
Luckily, it seems affected users can fix the problem by rolling back the update, but it does require some time and patience. Start by grabbing two small tools from Guru3D: the latest AMD Adrenalin installer and the Display Driver Uninstaller utility. Disable your internet so Windows does not try the same stunt again. Reboot into Safe Mode, run DDU to wipe every trace of the Microsoft driver, then restart normally and install the fresh Adrenalin package you downloaded. A second reboot locks everything in place.
To keep this from happening again, tell Windows to leave your GPU alone. On Windows 11 Pro you can open the Group Policy editor, navigate to “Computer Configuration > Administrative Templates > System > Device Installation Restrictions”, and enable the policy that blocks drivers matching your card’s hardware ID. Home users can achieve the same result with a registry tweak, though AMD’s community guide suggests the free Winaero Tweaker as an easier option. Save your hardware IDs in a text file so future updates take seconds instead of hours.
For a detailed step-by-step guide, you can check out this post on Reddit by u/Substantial_Fox_121, who outlined the process. AMD hasn’t piped up much on this wave, but community fixes are holding strong. Feel free to drop a comment below letting us know if this solution worked for you.
TechIssuesToday primarily focuses on publishing 'breaking' or 'exclusive' tech news. This means, we are usually the first news website on the whole Internet to highlight the topics we cover daily. So far, our stories have been picked up by many mainstream technology publications like The Verge, Macrumors, Forbes, etc. To know more, head here.
Dwayne Cubbins
1209 Posts
For nearly a decade, I've been deciphering the complexities of the tech world, with a particular passion for helping users navigate the ever-changing tech landscape. From crafting in-depth guides that unlock your phone's hidden potential to uncovering and explaining the latest bugs and glitches, I make sure you get the most out of your devices. And yes, you might occasionally find me ranting about some truly frustrating tech mishaps.
Follow Us
