What Is Vc Redist
Why does Steam insist on installing a new version of this thing every 2nd game I install? I checked my installed programs list, and there are about 15 different versions of this installed.I would assume that the latest version has all the content you need from the previous iterations, right?I’m mainly concerned because some games will actually behave badly if older versions of the redistributable are installed.Can I safely uninstall all but the latest of these? I notice that there are 32 bit and 64 bit installations for almost every iteration. Keeping the latest 32 bit and 64 bit installations should be adequate, right? Aren’t you guys slightly exaggerating? I mean, 15 versionsI never had more than maybe three installed at any one time.Anyway, from what I understand (as somebody programming and referencing DLLs himself) I’d say you need to keep at least the latest version of each itertion - i.e. If you add in the version number to the control panel you’ve notice they all either vary by one or more of the following:.
Version number. x64 vs.
X86. Visual Studio 2005, 2008, 2010. Service pack number.What’s going on is that each game uses the exact version of the VS redistributable it was built for, and only that version; this greatly reduces compatibility problems. Occasionally a major security bug will be found that updates in-place a specific one of the above, but that’s rare.This is all the XP+ way of fixing the old Windows 98 problem.Can I safely uninstall all but the latest of these?Nope; there’s no real way to tell which is used by what.
They’re like 20MB a piece tops and will never cause any problems, so don’t worry about it. This obviously isn’t ideal, but none of the other solutions to the general problem of reusable components that themselves update are, either.I’m mainly concerned because some games will actually behave badly if older versions of the redistributable are installed.Like what? Wouldn’t it be easier to just bundle the required.dlls in the game folder then, that installing a gazillion different versions on the system?
Even though this goes against the whole dll system (or the superior AMiGA Libraries) to begin with, as it would seem that it is not working properly.I suppose it could also be caused by shoddy installers, who insist on installing everything without running any version checks, i.e. Install 1.5 libs only if 1.5.x or higher is not installed. Or does Microsoft not have their libraries backwards compatible for a X.
Vcredist X64
Linoleum:Then you end up with thousands of runtime library files instead of say, thirteen.True, but at least this way they are tied to the exact game installation that is somewhat frakked, and not having the system infected with 15 installations of ‘basically’ the same Library.The main thing is, is Microsoft removing functions from 1.1 to 1.1SP1, or from 1.1 to 1.5, or from 1.1 to 2.0 etc? In those cases where it is not, shouldn’t the installer check if a latter version is installed before installing a older one, i.e. If the game came with 1.1, but the user has 1.1SP2 installed, surely there would be no reason to install 1.1 as well. Firstly, distributing the installer rather than the actual unpacked DLL files is in-line with microsoft’s recommendations, and possibly license requirements for the files.Secondly, the point is that applications compiled against a particular version of libc should use that version only. They should not use a newer or older version. That’s why you have however many slightly different versions installed. The rationale behind this is to reduce compatibility problems, and for a few hundred megs of disk space and 10 seconds per game install I really don’t think it deserves more than a ten page thread every few years.
Instant0:The main thing is, is Microsoft removing functions from 1.1 to 1.1SP1, or from 1.1 to 1.5, or from 1.1 to 2.0 etc?Sometimes that happens, perhaps because a function is deemed a security risk. Other times the exact way of how a function works changes, and that can be enough to break programs – especially poorly written ones that rely on undocumented behavior, including API bugs that got fixed. It’s better to always give applications the exact versions they were built with, rather than gamble on them being able to handle an updated version.
We were recently asked a question by one of our readers:What is VCRED file in Windows? I did not download it and it randomly appeared on my external drive with other files? Is it a virus? Please help.The VCRED file (or vcred file) is a harmless and vital file associated with the VCRED program on a Microsoft Windows-based personal computer.
The file and associated files are installation files for the Visual C Redistributable. When you install some software, they will need Microsoft Visual C which is already installed on a Microsoft Windows computer.If you delete VCRED file from Windows it can render some applications unusable. However, if you notice these files have randomly placed themselves on your external drive they are safe to delete because they are simply installation files and not the actual program. It is unknown how these files may have been placed on an external drive.
What Is Vcredist_x64
The following updates are the latest supported Visual C redistributable packages for Visual Studio 2015, 2017 and 2019. Included is a baseline version of the Universal C Runtime see MSDN for details. Executable files may, in some cases, harm your computer. Therefore, please read below to decide for yourself whether the VCredist.x64.exe on your computer is a Trojan that you should remove, or whether it is a file belonging to the Windows operating system or to a trusted application. Click to Run a Free Scan for VCredist.x64.exe related errors.