Discussion in 'Application Software' started by abbodi1406, Mar 9, 2018.
You need to login to view this posts content.
Minor update, to fix potential issue that may occur if Windows Script Host registry key has Enabled value set to 1
Cool, it finally works again, but I will keep the original batch version, I like it better anyway, no msi popups.
what does this redistributable do?
Many Windows programs created with various major versions of Visual Studio C/C++ tools are built to link the C++ runtime dynamically to save some storage space and possibly to ease development. This means the appropriate runtime must be present on your system for such programs to work correctly. Unfortunately Microsoft doesn't make it easy to get the latest runtimes and software developers often bundle old runtimes with their software. This turned Visual C++ runtime into the most unpatched software on Windows. Thank goodness cyber criminals don't target the C++ runtimes, but we can't afford to wait for them. While there is an official KB article where you can download the alleged latest versions, they often aren't the latest. Visual C++ AIO packs were born to fix this mess by providing the following features:
- remove old runtimes;
- install latest version for each runtime edition: legacy (2002-2003 NET - C++ 7.0 and 7.1), 2005, 2008, 2010, 2012, 2013 and 2015-2017 (finally Microsoft made the new versions of C++ runtime replace older versions, but too little, too late);
- maintenance (you can use this tool to clean the mess that gets created when various programs decide to either downgrade a certain C++ runtime or sideload an older version along with the latest).
As an extra this AIO pack also includes the lesser used Visual Studio Office Tools Runtime and the legacy Visual Basic runtime.
oh, thats alot information can u tell me i have already installed vcruntime in pc via iobit driver boaster pro so is it the same or diffrnce bcoz the one i have is for gaming Application.
Patch managers like those don't have the latest versions so you should run it anyway.
1. Remove this software.
2. Learn how to properly search for and install drivers/runtimes.
3. Don't be a plzbro, read the repack's description and what people tell you.
4. If you need performance in games, look into proper hardware, not "magical software" that "boosts" gaming performance.
5. If you already have an overkill pc, then you're simply messing our OS up with software like driver booster.
I think so too weird..
I already do sir, i search for the hell of it. WTF is a plzbro?
i always manually download my mobo and graphic card drivers but when i use iobit driver booster pro its say your most of the drivers is outdated or not installed why is that? anyone knw?
They use adware or a toolbar I guess going from a few searches about the software, recommend action and show a driver as being outdated (Even if the user has something newer installed.) to get the user to open the software and they get some revenue out of displaying that I would think.
(Or it's not just updated to handle newer driver versions and at least it does not seem to be outright malware, that's something to be careful about with optimizer programs or what they might call themselves these days.)
EDIT: But to return to the topic here good to see another update to the installer.
(And it seems I missed a update from last week too, guess it's time to install this then.)
Honestly, in this particular case(as in many others), "if it ain't broken, don't fix it". You don't necessarily need to install it every time there's an update. Only if something requires a newer runtime version.
There were runtime updates:
- May 25 - Updated Office tools runtime;
- May 27 - Updated Visual C++ 2017 runtime.
What happened if there are error messages? Do we have to uninstall and re-install it again? Any recommendations for solution?
It depends on what kind of errors, during installation?
Just in case anyone was wondering, altering the filename to include /argument works.
Maybe others can confirm the rest.
Something I just came across, since the modules themselves are being installed via the Windows Installer running the pack under a WinPE environment leads to the erroneous message in the end saying that it was installed correctly when it actually wasn't.
The main installer tries to execute the individual modules but there's no handle or support for msi there so you get the usual dialog asking you to choose a program to open that file with, skipping through those gets you to the last page of the main installer.
I think there's a way to detect if you're running under WinPE instead of a full fledged Windows installation via the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WinPE registry key, but I don't know if it would be worthy to add such test I mean... how many dumb enough people like me try to install this there... haha
You need to login to view this posts content.