Forum Discussion
Thanks @Konform103
As long as the fact that x64 and x86 have the same version for a given year, and it doesn't necessarily matter that it matches the version you have in your screenshot, I think I'm OK here. It looks like the Apex Installer ships with redists for vc2010, 2012u4, and 2015.
- 7 years ago
Sorry, should have clarified, I have 2005, 2008, 2010, 2012, 2013, 2017 installed, and in the cases you highlighted, I have x86 and x64 with the same versions, just not the exact same that you have.
For a given C++ release, is it best practice to install the latest from that particular year? E.g., if some other game installs a version of 2013, is it safe to install the latest of 2013 and assume that game will work with it? Or does the particular version matter? I have no idea how VC++ guarantees their APIs match from year-to-year and version-to-version.
- 7 years agoWell this configuration is offering me more stability on my pc i had a lot of issues with games which seems to have been solved by this.. I dont think you need exactly the latest version for every year i have but then again it wouldnt hurt to have it.. I'm no expert on the subject this is working for me.. But then again if you install some random software and it installs visual c++ 2010 10.0.1 in the background it could cause issues i believe.. I think it is best practice to keep it in mind when a game is not working to check your visual c++ installs and find if some app had installed an older version without you knowing.. Are you still not able to play the game?
- 7 years ago
Yea, still not working for me. I've had random failure in a variety of games that are unexplainable. Just Cause 3, Dark Souls III, both are unplayable on my rig and installing them actually screws up other games. I've long suspected VC++ issues, but have no idea which versions to keep, which to update, and which to remove.