Jump to content

abbodi1406

Members
 View Profile  See their activity

  • Content Count

    356

  • Joined

  • Last visited

  • Days Won

    79

Everything posted by abbodi1406

  1. abbodi1406
    Ah, forgot to change that, nothing serious
  2. abbodi1406
    Updated VC++ 2019: 14.22.27724.0
  3. abbodi1406
    2019_WinAll_14.22.27706.WA
  4. abbodi1406
    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
  5. abbodi1406
    - Updated: VC++ 2019 redist 14.22.27706 - Added AIO standalone addon for Win7 (mainly for Simplix Pack) @snorlax212 2015/2017/2019 are all the same runtimes, they cannot co-exist, latest 2019 should work for all
  6. abbodi1406
    Updated .NET 4.8 addon KB4495626 (4.8.3801.1)
  7. abbodi1406
    Added .NET 4.8
  8. abbodi1406
    @Pavel Those are original names in msi packages, changing it might cause unseen errors in future
  9. abbodi1406
    Update VC++ 2017 addon to VC++ 2019 14.20.27508
  10. abbodi1406
    Updated 4.7.3394.3 (KB4488666)
  11. abbodi1406
    Updated all addons with Display Icons
  12. abbodi1406
    Jan Krohn Thank you @Pavel DESIGNER is part of Visual Basic 6 runtimes You must start Wintoolkit as TrustedInstaller. Read the Important Note again
  13. abbodi1406
    Icons are overrated but i will see about it
  14. abbodi1406
    Updated SxS 2008/2005 addons
  15. abbodi1406
    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
  16. abbodi1406
    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
  17. abbodi1406
    Updated 4.7.3362.1 (KB4486546)
  18. abbodi1406
    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
  19. abbodi1406
    Updated 4.7.3353.2 (KB4483451)
  20. abbodi1406
    No, it's real addon integrated as installed, doesn't need runonce installer
  21. abbodi1406
    Updated 4.7.3324.1 (KB4480096)
  22. abbodi1406
    Updated (KB4480055)
  23. abbodi1406
    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
  24. abbodi1406
    Updated (KB4470640)
  25. abbodi1406
    Updated (KB4467088)
×
×
  • Create New...