Hi everyone
I just recieved this morning this new ADM Graphics card driver throught Windows Update did you get it too ?
But i cannot open Adrenalin Software now
I can't see any change in dxdiag tool ... anybody knows what is this driver ?
Thanks a lot
In order to complete i've found something interesting because there was an Adrenalin Software update on Windows Store this morning too ... without any changelog i checked
The first time i've seen Adrenalin Software update on Windows store but it's OK why not
Maybe a new Adrenalin Update on Windows Store coming soon in order to fix this little issue ?
Is it a new Rolling Release update mod for Adrenalin Software throught Windows Store ?
Wait & See
Same problem here. After a few tries to launch AMD Software, it stopped giving me the above mentioned error but I got this instead:
It's stuck at Downloading 0%. Reinstalling it from Microsoft store does not help.
I'm having the exact same issue, I own a 6700 XT and the AMD Software is stuck at 0% as well. I'm just going to use the Clean Up Tool and try to disable Windows 11 from downloading drivers.
I did a rollback and everything seems to be working fine so I'd wait till the next adrenaline edition comes out to update the amd windows driver version
I have no idea why people are using Windows Update and the Microsoft Store to update their GPUs. Use the Adrenalin software instead, or download and install direct from the AMD website. You can update Adrenalin from within the application itself. Most of all, never use the Store version. There was a new Adrenalin edition released December 5th.
The driver installed itself automatically for me (not optional). It seems the only way to avoid it for now is to block drivers in Windows update.. which is not something I really want to do, nor should any normal user ever need to do.. AMD screwed up by pushing this undocumented beta driver to everyone (?).
hi I have same issue... also in my ssytem - MSI Afterburner cannot see GPU temps or clock... HWinfo shows all... but cannot benchmark properly with MSI Afterburner... have you experienced it as well? Tried to rollback the drivers but the issue is still there...