just simply do this one time after it automatically updated to its wrong version. boom now it's never gonna roll back to that previous wrong AMD Adrenaline edition. it keeps with a working version of yours. ps: don't reply to me :)
Windows 11 is keep installing the wrong AMD driver
I installed the proper version on the amd website with auto detect and windows 11 is keep installing the old driver which is causing graphics problems. How to stop this ?
Windows for home | Windows 11 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
72 answers
Sort by: Most helpful
-
Anonymous
2023-07-06T07:50:58+00:00 -
Anonymous
2023-02-02T23:05:49+00:00 This is messed up and Microsoft has to be doing this on purpose since it's ben an ongoing issue since Beta Win 11. I'm not pointing fingers of collusion or anything but I find it interesting that Microsoft has no answer for this, two years into Win 11. Yet, Intel and Nvidia continue to be trouble free.
-
Anonymous
2022-09-10T17:36:16+00:00 Don't feel left out, I am on Pro insider build (beta I think) and the 'how to block drivers' doesn't work for me either. In my case it is downloading workstation drivers. The one step I have not tried is turning off ALL driver updates as I leave it up to Windows to deal with my intel wifi/Bluetooth card.
-
Anonymous
2022-12-04T18:44:56+00:00 I have not found a fix for this nothing I look up helps but I have found an temp fix pause windows update then go to device manager and locate the device (in my case it is under display adapters and AMD Radeon (TM) Graphics) right click and hit properties then go to the driver tab and hit roll back driver and your AMD driver will be back. This is a lot faster then re-downloading amd software. Make sure to update in the adrenaline software.
-
Anonymous
2022-10-01T12:13:42+00:00 Confirming that wushowhide manager finally found the display driver in the list and was able to properly hide it. I will report back for more if it gets ignored in the future. PS: It was not possible pre-22H2. I still consider it a hijack and not an official compatibility solution. :)