Jump to content

abbodi1406

Members
  • Posts

    458
  • Joined

  • Last visited

  • Days Won

    191

Posts posted by abbodi1406

  1. 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
     

  2. 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
     

  3. 10 hours ago, simplix said:

    Hello, abbodi1406!

    If you have plans to create an addon of VisualCppRedist AIO, I will add its support in UpdatePack7R2. If people need it at all, because I have seen an outdated topic in this section of the forum.

    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

  4. 12 hours ago, simplix said:

    Hi abbodi1406! Thanks for this wonderful addon. I will try to add his support to the UpdatePack7R2.

    To test, I decided to first integrate it manually and chose x64 version. There were several questions.

    1) Not all data from NDP472-KB4470640-x64.reg is imported into the registry - Classes\CLSID\{FEDB2179-2335-48F1-AA28-5CDA35A2B36D} can write only TrustedInstaller, so if Win Toolkit works with user rights, this entry will be skipped. I can get around this problem by importing twice - from the administrator and from TrustedInstaller.

    2) Does it make sense to add LangPacks? I think they do not do anything useful for the work of the programs, but maybe I'm wrong?

    3) I also see no reason to leave automatic start of services NGEN, according to my observations, they only periodically load the processor, but I don’t think there is a practical sense from this optimization, programs do not run faster. Please correct if it is not, otherwise we need to disable these services.

     

    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

×
×
  • Create New...