2005 SP1 (needed but not installed automatically, if not installed SideBySide error will appear), 2012(both version x86/64), 2013, 2015. It's ok? or something wrong here?
I don't understand your question. All needed packages are included with our driver.
INFORMATION REQUIRED WHEN POSTING A QUESTION
The question is simple, why 2005 SP1 not included in driver if it's needed - if not it must be builded without library depences, and why so many packages I need to install just for VGA driver. It's philosophical question for community/dev. team to make driver better.
I feel more clarity is needed to the OP, but fortunately I know exactly what he/she's talking about.
This is true even with the newest AMD Desktop Graphics Driver which was released today, version 17.10.1 (I am using an AMD RX Vega 64 card), so even if I'm replying to a 6-month old post this issue still occurs today.
The issue is that the Windows 10 Event Viewer's "Application" log will show an error at every boot, unless the vcredist C++ 2005 SP1 x86 is installed, then the error goes away for good. (even for Windows 10 x64 need to install the x86 version of the vcredist C++ 2005 SP1).
So, to me it sounds like the vcredist 2005 isn't included with the driver, and I wonder it this may cause other issues other than just an error in the Event Viewer.
Event Viewer error details:
More info here (issue was described here): Dependent Assembly Microsoft.VC80.CRT error - Microsoft Community and here: side by side error reported in eventlog
And some users may not do
Doesn't help much. The fact remains that the driver has a dependency on vcredist 2005 x86 (as evidenced in the Windows Event Viewer Application Log), which is not installed along with the driver, contrary to what is indicated in the second post.
I don't have an issue with requiring multiple versions of vcredist, but with the fact that there's an error in the Event Viewer which is due to vcredist 2005 not being installed by the AMD driver, when it *is* required by the driver. Install vcredist 2005 and the error is gone.
For the driver team to know of this issue, you should use the Report Issue function.
Would you mind posting a pic of the expanded app error (might come in handy for others).
Here's the screenshot:
I have these,
Maybe amdmatt or @ray_m will take a look.
Retrieving data ...