Everything posted by abbodi1406
- Visual C++ Redistributable Runtimes
-
Visual C++ Redistributable Runtimes
Either use the 3-addons per architecture: vcredist_x64_2019_WinAll_14.22.27706.WA vcredist_x64_2013d_WinAll.WA vcredist_x64_SxS_Win7.WA vcredist_x86_2019_WinAll_14.22.27706.WA vcredist_x86_2013d_WinAll.WA vcredist_x86_SxS_Win7.WA - or only use the AIO addon: vcredist_x64_Win7_20190523.WA vcredist_x86_Win7_20190523.WA
- Visual C++ Redistributable Runtimes
-
Microsoft .NET Framework 4.8 for Windows 7
Updated .NET 4.8 addon KB4495626 (4.8.3801.1)
-
Microsoft .NET Framework 4.8 for Windows 7
Added .NET 4.8
- Visual C++ Redistributable Runtimes
- Visual C++ Redistributable Runtimes
-
Microsoft .NET Framework 4.8 for Windows 7
Updated 4.7.3394.3 (KB4488666)
- Visual C++ Redistributable Runtimes
- Visual C++ Redistributable Runtimes
- Visual C++ Redistributable Runtimes
- Visual C++ Redistributable Runtimes
-
Visual C++ Redistributable Runtimes
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
- Visual C++ Redistributable Runtimes
-
Microsoft .NET Framework 4.8 for Windows 7
Updated 4.7.3362.1 (KB4486546)
-
Microsoft .NET Framework 4.8 for Windows 7
It's doable, but will not be complete 2017 is updated constantly maybe i will make two, one with 2010/2012/2013, and one with 2017 only which i could easily update 2005/2008 are WinSxS assemblies, they cannot be properly added offline, so they are out of the picture for now
-
Microsoft .NET Framework 4.8 for Windows 7
Updated 4.7.3353.2 (KB4483451)
-
Microsoft .NET Framework 4.8 for Windows 7
No, it's real addon integrated as installed, doesn't need runonce installer
-
Microsoft .NET Framework 4.8 for Windows 7
Updated 4.7.3324.1 (KB4480096)
-
Microsoft .NET Framework 4.8 for Windows 7
Updated (KB4480055)
-
Microsoft .NET Framework 4.8 for Windows 7
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
-
Microsoft .NET Framework 4.8 for Windows 7
Updated (KB4470640)
-
Microsoft .NET Framework 4.8 for Windows 7
Updated (KB4467088)
-
Microsoft .NET Framework 4.8 for Windows 7
Updated (KB4459942)
-
[14 janvier 2020] Update list GDR pour Windows 7 SP1 x86/x64 (Fr-En-De-Es-It)
It was correct at that time WU check for appraiser telemetry components, not updates number and if present, it offer KB3150513 KB2952664 components are fully included in Monthly Rollup KB3150513 is old and superseded, and Microsoft should expire it