Installs fine from setupcomplete.cmd (W7U x64). I used it unpacked in my $oem$\$$\Setup\Scripts folder Code: (...) pushd _burf_vcredist call x64.cmd auto popd (...) Thank you so much.
When I do version 50 I'll put a message on the front screen of the installer as I can see how confusion could easily occur.
Thanks. Superb installer. Wish you would prominently mention the latest version in the OP. Many might not notice/realise that there is a later version. A link to the post with the latest version in the OP would be helpful too.
Usually there might be one RC, maybe two if there are issues, but there seems to be more RC releases than that. The reason why this is strange is because RC stands for 'Release Candidate', meaning there should only really be one before release. I guess they are either finding last minute notable bugs or are targetting a 'perfect' release. As long as it's not like the old joke about levelling off the bottom of a chair or tabl. Wherever you seek perfection in a final product you're likely to find a never-ending number of changes that could be made to achieve that perfection. Of course, that needs to be balanced against not releasing buggy crud either!
I never thought of this nor investigated before. So most likely it happens in all runtime installations around the world. Am I right? If so, does burfadel's one will clean up an existing messed up runtime installation and next install all visuals correctly?
Windows version detect not always name: "Version" (depend of windows language) Installer.cmd: Code: title Quick installer for Visual C++ Runtimes V50 by Burf ver|"%windir%\system32\findstr.exe" /c:"Version 5." if %errorlevel% equ 0 ( better to Code: title Quick installer for Visual C++ Runtimes V50 by Burf ver|"%windir%\system32\find.exe" "5." >nul if %errorlevel% equ 0 (
Good point! I'll change that in v51, except to " 5.x" otherwise when there is a version with 5. somewhere in the version string, using "5." without a preceding space will detect a 'false positive'.
v50 seems to have a bug. your redists_x64.txt and redists_x86.txt files contain the following: vcredist_x64_2017\vc_runtimeMinimum_x64.msi vcredist_x64_2015-2017\vc_runtimeAdditional_x64.msi and vcredist_x86_2017\vc_runtimeMinimum_x86.msi vcredist_x86_2015-2017\vc_runtimeAdditional_x86.msi but there is no 2017 directory in the archive, only the 2015-2017 directory is present, and it contains all the msi files. -andy-