Windows 10: how i can solve this vc installation error?

Hello! When I try to install the latest version of VC_redist I get this error, does anyone know how to fix it?

:)

 

Microsoft Visual C++ 2012 redistributable (x64) - 11.0.61030 Installer Error

Tried the two steps listed in the bottom link but I still get the same error log when trying to install the vc++

Sfc return no corrupt file on my pc

 

VC++ 2012

I have a game I'm trying to install. As part of the install it wants to install Visual C++ redistributable 2012 (x64) 11.0.61030. Whenever the vcredist_x64.exe is ran my computer instantly wants to reboot (even with /norestart being used). The package
is listed as installed under Apps & features, but if you try to repair it, it will instantly reboot the system. If you just run vcredist_x64.exe it will instantly reboot the system. I can uninstall it and it will instantly reboot the system and not be listed
as installed anymore. But then the game will try to install it again, which will force a reboot, the game install never sees that the VC finished installing so it keeps trying, which keeps causing a reboot. How can I identify what's broken in windows 10 that
causes the VC 2012 package to behave this way? It also runs installs for VC 2010 packages with no problem.

 

need specific VC redist packages for repair of installed vc redist packages

Just a little addendum to my last post.

I decided to just go ahead and axe the whole lot of vc redist's that were installed on my machine. everything but the vc redist 2017 x86. when i uninstalled the 2013 x64 redist the entry for the older version disappeared and did not reappear when i reinstalled
the vc redist, so i guess that issue is solved. Now for the reason for this second post.

All the reinstalls of the vc redists went well until i got to the vc 2015 x86 redist. setup for the redist kept erroring out saying another version was installed. no amount of tinkering i could do would get it to say otherwise. then i stumbled across the
reason. having vc 2017 redist installed will keep the 2015 redist from being serviced (installed, updated, etc). this is because they are both registered as version 14. the x64 version of 2015 went well, but because i had the 2017 x86 version already installed
the install of the x86 2015 redist setup program aborted the install.

the quickest way for the end user around this is to uninstall the 2017 redist before servicing the 2015 redist. this is far from an optimal solution, but there you have it. At least until Microsoft fixes the issue.

the best way for M$ to fix the issue is to release a patch or whatever that changes the 2017 redist version to version 15.

Update..... finished installing the 2017 VC redist's looks like the 2017 files actually are meant to replace the 2015 versions. this is something that was not occurring before. my system was saying that both the 2015 and 2017 versions were installed before.

so i guess i don't need to install the 2015 redists anymore, and just skip ahead to the 2017 redist from now on?