- Mar 30, 2005
- 9,144
- 929
- 126
Running Windows 7 64 bit. AMD Settings app notified me that new video drivers were available for download. SO I downloaded. (I've been running 19.4.something)
Sadly, installing driver package Adrenaline 2019 19.5.2 failed with an error just now. Error 1603 - a general error.
https://www.amd.com/en/support/kb/faq/gpu-kb1603
Following steps outlined at the link above, I attempted running DISM at an elevated command prompt. BUUUUT, DISM couldn't process the command line option /RestoreHealth.
Probably because that option isn't available for Windows 7.
(see here: https://answers.microsoft.com/en-us...up-image/33be783f-6e3f-408b-9d0c-901cd19c14ea)
I ran SFC /Scannow and everything checked out, no disk integrity issues to fix.
Looking at the log file created by the Adrenaline installer ... the install process failed on the AMD Settings app installation. The other packages installed fine - Control Center, Visual C++, Display Driver, HDMI Audio driver.
( The AMD Settings app doesn't seem too system critical, IMO. )
At this point. What do I do?
(see log file below)
Do I revert to the latest Windows Restore Point? Run DISM with different command parameters? Avoid any reboots?
Sadly, installing driver package Adrenaline 2019 19.5.2 failed with an error just now. Error 1603 - a general error.
https://www.amd.com/en/support/kb/faq/gpu-kb1603
Following steps outlined at the link above, I attempted running DISM at an elevated command prompt. BUUUUT, DISM couldn't process the command line option /RestoreHealth.
Probably because that option isn't available for Windows 7.
(see here: https://answers.microsoft.com/en-us...up-image/33be783f-6e3f-408b-9d0c-901cd19c14ea)
I ran SFC /Scannow and everything checked out, no disk integrity issues to fix.
Looking at the log file created by the Adrenaline installer ... the install process failed on the AMD Settings app installation. The other packages installed fine - Control Center, Visual C++, Display Driver, HDMI Audio driver.
( The AMD Settings app doesn't seem too system critical, IMO. )
At this point. What do I do?
(see log file below)
Do I revert to the latest Windows Restore Point? Run DISM with different command parameters? Avoid any reboots?
Last edited:
