vs2010 installation failed at installing vc runtime 86x

[Necuno]

vs2010 installation failed at installing vc runtime 86x

any ideas why this might happen ?

tried now from a different installation sources, installing vc runtime on it's own, removing c++ from vs 2005, removing vs2008's c++....

 

[Necuno]

...interesting, fixed by doing this
http://support.microsoft.com/kb/555989

 

[Gnome]

VC Runtime?

Is it per chance the Visual C++ Redistributable Package (x86)?

If that is the case you can download the latest versions from the internet and just install them directly. I usually integrate the latest versions into my development machine Windows install directly (using nLite and Kels Runtimes addon). The versions included with the .NET framework are seriously outdated.

It's worth noting that the runtimes can and should be installed before anything else (the kel pack is a installed at T-14 installation phase, to those who know their customized Windows installations).

 

[Necuno]

VC Runtime?

Is it per chance the Visual C++ Redistributable Package (x86)?

If that is the case you can download the latest versions from the internet and just install them directly. I usually integrate the latest versions into my development machine Windows install directly (using nLite and Kels Runtimes addon). The versions included with the .NET framework are seriously outdated.

It's worth noting that the runtimes can and should be installed before anything else (the kel pack is a installed at T-14 installation phase, to those who know their customized Windows installations).

thanx, but as i said it's already fixed , some how that part broke and well after doing the steps in the KB article vs2010 installed without any issues. got the clue after i tried to do the .net, prereq and vc runtimes separately; the .net 4.0 said untrusted installer and that's how i got to the KB article.

...interesting, fixed by doing this
http://support.microsoft.com/kb/555989

 

[Raithlin]

Wish I'd found this 2 weeks ago. I had the same problem after reinstalling my laptop, and ended up not only redoing the laptop again, but found that removing the bundled Office 2007 fixed the issue I was having! :erm:

I always said Office was a virus. Now I have proof.