simplix

Updated
KB5004755 (4.8.4410.1)

Updated
VC++ 2022: 14.30.30423.0

Description=Microsoft Visual C++ Redistributable 2019

Updated
VC++ 2022: 14.30.30401

Updated

I always set encoding to ANSI, but i forgot this time
fixing

Updated
VC++ 2019: 14.28.29515.1

Updated .NET 4.8 addon
KB4495626 (4.8.3801.1)

Added .NET 4.8

Thank you!
I'm starting to test, so far I checked x86.
1) In the Uninstall section "2010  x86" has 2 spaces.
"DisplayName"="Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219"
2) No icons in many entries. Pic1 what is it seen, Pic2 how can it be.


3) I think the changes between SxS_Win7 and SxS_Win810 are too small to make different addons.
4) A few errors in the entries:
vcredist_x86_SxS_Win7\VC_x86_2005.reg in Components\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6229_none_cbee8c4a4710d003 has "\" in "f!mfc80u.dll" and "f!mfcm80.dll".
vcredist_x86_SxS_Win7\VC_x86_2008.reg in Components\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.7523_none_4bf3b680bf9ea69d has "\" in "f!mfc90u.dll" and "f!mfcm90.dll".
1-3 items are not critical.
P. S. Checked x64 - all the same.

Updated SxS 2008/2005 addons

1) The two speces are the default state from original installer
2) i use slim msi installers for all vcredist, msi entries do not have display icon by default
https://github.com/abbodi1406/vcredist
using original installers (specially 2017/2013/2012) will add many bloat files and registy:
https://forums.mydigitallife.net/posts/1472819/
i could add custom display icon for each msi file (similar to .NET addon), but i'm trying to keep things minimal and default as much as possible
3) actually, upon further tsting, there are more diffirent registry values in COMPONENTS keys
i will update Win810 addons
4) thanks for notifying, SxS entries are hard to keep an eye on
i will fix that ASAP
 

Project Rebooted
make sure to read the notes, specially about SxS 2008/2005 addons
i kept 2017 addon separate so it can be easily updated

Description:
 
The .NET Framework is a popular development platform for building apps for Windows, Windows Store, Windows Phone, Windows Server, and Windows Azure. The .NET Framework platform includes the C# and Visual Basic programming languages, the common language runtime, and an extensive class library. read more.
 
Info: The .NET package will be slipstreamed as pre-installed
OS: Windows 7 SP1
Notes:
- The addon will conflict with some Windows Updates (.NET 3.5 Family), so leave the addon's integration to the last.
- Add main addon first before LangPack addon, to get ASP.NET service localization properly.
- To function properly, .NET 4.7.x require D3DCompiler_47.dll component, which is found in either the current "Monthly Quality Rollup" or "update KB4019990". It is recommended to integrate it first, or you can install it later.
Windows6.1-KB4019990-x64.msu
Windows6.1-KB4019990-x86.msu
.NET 4.8:
.NET 4.7.2:
Languages Codes Reference:
 

Description:

The Visual C++ Redistributable Packages install runtime components that are required to run applications that are developed by using Visual Studio. These packages install run-time components of these libraries: C Runtime (CRT), Standard C++, ATL, MFC, C++ AMP, OpenMP and MSDIA. read more.

OS: Windows All

Versions:
VC++ 2022: 14.40.33807.0 VC++ 2013: 12.0.40664.0 VC++ 2012: 11.0.61135.400 VC++ 2010: 10.0.40219.473 VC++ 2008: 9.0.30729.7523 VC++ 2005: 8.0.61187 VC++ 2003: 7.10.6119.0 Vc++ 2002: 7.0.9975.0 + Legacy Visual Basic Runtimes Files Contents:
vcredist_x64_Win7 / vcredist_x86_Win7: All runtimes for Windows 7 SP1 vcredist_x64_2022_WinAll / vcredist_x86_2022_WinAll: Visual C++ 2022 vcredist_x64_2013d_WinAll / vcredist_x86_2013d_WinAll: Visual C++ 2013, 2012, 2010, 2003, 2002 Visual Basic 6.0 Runtimes vcredist_x64_SxS_Win7 / vcredist_x86_SxS_Win7: Visual C++ 2008, 2005 for Windows 7 SP1 vcredist_x64_SxS_Win810 / vcredist_x86_SxS_Win810: Visual C++ 2008, 2005 for Windows 8.1/10 Important Notes:
# Integrating SxS 2008/2005 addons require launching Wintoolkit with TrustedInstaller privileges, to gain write access to WinSxS directory
for that, you need to use NSudo (or other similar tools):
- download and extract latest release Binary.zip
- launch Win32\NSudo.exe or x64\NSudo.exe, or run NSudo.bat as administrator
- make sure User is set to TrustedInstaller
- check "Enable All Privileges"
- paste Wintoolkit.exe path in the lower box (or Browse to the file)
- click run
if you are using Windows 7 Simplix Update Pack, you don't need that, it already handle the required privileges
# vcredist_x64_Win7 / vcredist_x86_Win7 is AIO addon, mainly to be used with Simplix Update Pack, or else you need Wintoolkit with NSudo
# VC++ 2022 runtimes are binary compatible and upgrade to VC++ 2015-2017-2019 and cover all VS 2015-2017-2019-2022 programs
# To complete VC++ 2022 functions for Windows 7/8.1, you need to integrate Universal CRT components, which is available with latest Monthly Rollup, or updates KB3118401/KB2999226
Download:
vcredist_x64_Win7_20240411.WA
vcredist_x86_Win7_20240411.WA
vcredist_x64_2022_WinAll_14.40.33807.WA
vcredist_x86_2022_WinAll_14.40.33807.WA
vcredist_x64_2013d_WinAll.WA
vcredist_x86_2013d_WinAll.WA
vcredist_x64_SxS_Win7.WA
vcredist_x86_SxS_Win7.WA
vcredist_x64_SxS_Win810.WA
vcredist_x86_SxS_Win810.WA
you can find latest releases -> here
SHA1 checksums:
05e938f354c059d89d846d2e9a7591d05154aa70 *vcredist_x64_2013d_WinAll.WA 534f1e53080819aeb58e3b060d7c6a0a76b4d4d4 *vcredist_x86_2013d_WinAll.WA 8cc9f65fc444a878d8cabd0ad317597edb552f07 *vcredist_x64_SxS_Win7.WA 886faa949e7d51a40dc8d467f65c373f887c2ec3 *vcredist_x86_SxS_Win7.WA 94e267e5e6ff89854bd64b6260333664a266c754 *vcredist_x64_SxS_Win810.WA 206fda69fa2d3fd838dd9e3ee33f35c4cd7a2cae *vcredist_x86_SxS_Win810.WA Credits to ricktendo for original repack AIO

Hello, you are welcome :)
1) Wintoolkit correctly import all registry keys, even those TrustedInstaller ones, i verified that since the  beginning :)
i don't really know how the developer accomplish that
2) I only started creating LP addons since 4.7.1 due requests, indeed, they are not very useful except to silence Windows Update
3) I don't know for sure, but i tend to leave configurations as default like original setup, the user can disable it then
 
regarding integration, i actually have mini pack for personal use, which extract/prepare/integrate the addon without Wintoolkit :)
i use NSudo to get TrustedInstaller rights