According to the log, all VC++ 2026 files are installed only thing missing is the registry entry for "2022 x86 Minimum Runtime", so the script will try to remove both 2022 x86 msi, and reinstall them Code: >echo Installing 1 of 2: 2026\x86\vc_runtimeMinimum_x86.msi >echo Installing 2 of 2: 2026\x86\vc_runtimeAdditional_x86.msi Try these steps one at a time: - run the installer normally one more time - if the issue persist, run it with /aiP parameter and choose "2. Show" - if the 4 entries for 2022 still not showing, run the following in Command Prompt as administrator, then run the installer normally afterward: Spoiler Code: start /wait MsiExec.exe /X{773AD50D-AAE6-4BA1-AD01-B5A38874C840} /quiet /norestart reg delete HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{773AD50D-AAE6-4BA1-AD01-B5A38874C840} /f 2>nul start /wait MsiExec.exe /X{5A0DFA55-3851-45BC-8B20-95EA4BF5812D} /quiet /norestart reg delete HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{5A0DFA55-3851-45BC-8B20-95EA4BF5812D} /f 2>nul start /wait MsiExec.exe /X{AECD4ED0-8A3B-41E9-92D1-6BEE0374CCAF} /quiet /norestart reg delete HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{AECD4ED0-8A3B-41E9-92D1-6BEE0374CCAF} /f 2>nul start /wait MsiExec.exe /X{61B44572-8722-4DAF-8ACF-8E742D30BCC5} /quiet /norestart reg delete HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{61B44572-8722-4DAF-8ACF-8E742D30BCC5} /f 2>nul
AFAIK the version is already displayed in a dedicated column and doesn't need to be part of the name again.
@Radel46 Uninstaller.cmd use msi and original exe files for uninstallation (plus clearing registry keys) it does not check or delete runtimes files (if still exist) if the files are locked (being used), then a restart is needed to complete deletion if the files are rogue (manually copied, leftovers from fail or collided msi installation), then they will not be deleted if you need cleanest or best result, run the uninstaller, reboot, then run the installer normally, and restart again
I cannot install when using the newly installed 26200.7462. Perhaps I need to switch to a lower version of Windows. update: It turns out that the cause was WMIC being installed. When I uninstalled WMIC, the problem was solved.
Probably a silly question..just installed last AIO, and want to know VC 2005, until 2013 are necessary to install, and why not install latest one?? Thanks for the work and for answer..
Because different programs require different versions. The runtimes' purpose is to substitute the respective version of visual studio, so rather than having multiple gigabytes of visual studios, you only have ~200 megabytes of runtimes.
Just noticed Microsoft Visual C++ 2015-2022 Redistributable (x86 and x64) - 14.44.35211.0 installs when updating Office 2024, regardless of what runtimes you have installed. I don't like that. Wondering, can that installation override what I have already installed via this script?
It mess up some registry entries but runtime files themselves will not be overridden if higher version is installed
I guess the worst that can happen (as has happened in the past) is that this pack will reinstall the latest package even if it is already there. This usually fixes the reg entries.
@abbodi1406 Would you consider adding the "Microsoft Visual C++ UWP Desktop (Runtime) Package(s) / Microsoft.VCLibs.140.00.UWPDesktop to this vcredist? They are VC++ dependencies for Windows Store Apps/Games and match the philosophy of your package I feel. It would be great for instance, when trying to either enable Windows Store functionality on 10 LTSC Enterprise IoT or existing for compatibility even without the store if you use a 3rd party store app downloader. Likewise I think also the Windows App Runtime and Microsoft.UI.Xaml v2.8 are dependencies that could be useful to integrate.