New
#81
It's all good - I am rarely offended by anyone's comments.
c++ redists get installed when a program is installed that relies on that version; the install package carries the c++ lib it needs and if it's not installed, the pkg will install it. This is one way a 4 month old system can become unstable - some program has a bad or outdated lib. It's rare.
I took the shotgun approach and gave you every single c+ redist lib - both the 32 and 64 bit versions. Without doing a full analysis of the software on your machine (that's not going to happen) this is the best way to ensure a program has the correct lib. Some pgm might need the 32 bit version while another might need the 64 bit version.
It isn't clear if SP1 versions are where you want to start - some say they need a base install others don't mention it. I'm cautious that way, start at the ground and let Windows Update offer what it knows is needed.
msvcrt 2013 is fairly new, it's doubtful that many pgms are using it. I don't see any list of redists other than your laptop (I think it's on your laptop anyway). If 2013 isn't on the desktop now, don't worry about it, many system don't have 2012 on them. Go ahead and clean up the msvcrt installs - install all the versions I referenced - if they're not needed, they won't be called. If a pgm is installed later that needs it, then that version is already on your system. At least for these versions, you know they cam from MS and should be golden.
Many of the versions predate Windows 7, so that cannot be a pre-req for them.
Regarding the reinstall option ... I mentioned a clean install, which is slightly different from using the OEM recovery partition.
Take a read of these tutorials:
Clean Reinstall - Factory OEM Windows 7
Clean Install Windows 7
I hesitated providing the links before because some people do more than just read - they act even though I state that it's for reference only.
Either path has it's drawbacks, neither is guaranteed. Both require a good amount of time.
I offered a reinstall because when trouble shooting my own systems I have to make the same decision - keep plugging along, or restart fresh. With an issue like the one on your machine, you have to protect the fresh install as much as possible - that means pre-emptively install core tech (.NET, msvcrt ...) and NOT installing anything non-essential for a while. It's a hard discipline - I've been running Win8 f0r 5 months now and I'm just beginning to apply changes that require manual modifications of the registry or files.
Almost forgot, running anything before all msvcrt versions are installed, might force that application to install the version in it's pkg. Worse, the pgm might just crash. Don't run other apps until you get c++ libs up to date (Windows Update is ok to run).
MS has tied .NET to the OS, but depending on the OS, versions can be uninstalled and re-installed. I don't want to get into the details because it's hard to understand and even harder to explain. I cut my teeth on Vista and .NET 3.0 - what a mess!
Bill
.