Jump to content

abbodi1406

Members
  • Content Count

    369
  • Joined

  • Last visited

  • Days Won

    93

Everything posted by abbodi1406

  1. Nothing different, mine is kind of preinstall the package manually and saves install time later ricktendo's and yumeyao's install the package after installing the system regarding managed code, don't know for sure
  2. - Never haved Vista, therefore, no - If the mechanism is still like Windows 8.x, yes i could and probably will
  3. Never encountered such error i even copied Wintoolkit to system drive root which is usually extra UAC protected, still works
  4. Yes it makes an important difference regarding how junction points and symbolic links are captured / managed inside the wim don't know the exact details or behavior, but the option RP_FIX is always set in microsoft releases (all wim files), that should be a strong clue Edit: here's a clear explanation i think: http://blogs.technet.com/b/zhou_minxiao/archive/2007/04/05/what-is-norpfix-switch-and-what-does-it-do.aspx so, it's necessary, but neither two options affect size
  5. I recommend checking for %MOUNT%\Windows\winsxs\pending.xml if exist, StartComponentCleanup process will not work and regarding SPSuperseded, it's useful only for Win7 RTM + SP1 i don't think we will see Service Packs for Windows anymore
  6. I'm not really familiar to PE projects or used it before a direct test failed as expected: i know that the correct way will be by creating .script or plugin like the one used for .NET 2/3 in Win7PE SE, but would require some skills and walking through i'll see if i could
  7. Yes same thing, framework 4 is separate from 3.5 and below XP don't have any, so you need to put them all
  8. He means x64-based edition of Wintoolkit
  9. Updated only Regular Addon this time if you want the Full use the previous one, or copy netfx_Full_LDR.mzz file of it
  10. 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++ 2019: 14.24.28127.4 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_2019_WinAll / vcredist_x86_2019_WinAll: Visual C++ 2019 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++ 2019 runtimes are binary compatible and upgrade to VC++ 2015-2017 and cover all VS 2015-2017-2019 programs # To complete VC++ 2019 function 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_20191015.WA vcredist_x86_Win7_20191015.WA vcredist_x64_2019_WinAll_14.24.28127.WA vcredist_x86_2019_WinAll_14.24.28127.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: d13217e04e4c27bdb9b6f462eabf1a10fa852b72 *vcredist_x64_Win7_20190716.WA ef0ba3513031651effc100a1f1828e88d81b5640 *vcredist_x86_Win7_20190716.WA 57585ffad5478d6f0d7ba8238c51d6a26d91464e *vcredist_x64_2019_WinAll_14.22.27821.WA 1de5c09f237a2873b92126c170abf9272d947fdf *vcredist_x86_2019_WinAll_14.22.27821.WA 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
  11. Description: The Microsoft DirectX® End-User Runtime provides updates to 9.0c and previous versions of DirectX — the core Windows® technology that drives high-speed multimedia and games on the PC. read more. Info: The addon will Slipstream DirectX runtimes into the windows image as Pre-Installed OS: Windows 7 / 8 / 8.1 - x86 / x64 Version: 9.29.1974 Download: DirectX_June2010_x86.WA Mirror Size: 13.13 MB MD5 : 19d9de7038fc9f869e3126f20a785785 SHA1: a2a0880986ed464403035822d296fc2b76f7ff25 DirectX_June2010_x64.WA Mirror Size: 27.83 MB MD5 : 78797de2739070bbc6329bc52a75d440 SHA1: 7244d80c532c882a0a945d9d97e0067dd0b35294 Note: on Windows 8/8.1/10 you need first to enable .NET Framework 3.5 feature
  12. anyway, i checked WU in windows 8 but couldn't get the update, never offred or installed
  13. And how is this related to Wintoolkit Bugs?
  14. Yes IE11 is part of Windows 8.1 system like IE8 to Windows 7
  15. Only security update KB2972216 is needed you are welcome
  16. You do'nt even need to specify msiexec, it's enough to launch the patch file itself with parameters: blah.msp /passive /norestart tested working with Office updates
  17. Delete the current text file and re-download it
  18. Yes but those are just the related to KB2919355 (Update1)
  19. @BrokenZer0 there are an updated version of both text files for systems that already have KB2919355: 1. KB29750612. KB29668703. KB29599774. KB2934018for RTM systems that don't have KB2919355: 1. KB2975061 (Prerequisite)2. KB29668703. KB29193554. KB29320465. KB29375926. KB29384397. KB29599778. KB29340189. KB2938772
  20. Updated i didn't use v4.5.3 since it's a pre-release
  21. They can be integrated normally after 2919355 but 2919355 must be integrated first in a separate dism session "Install pending" has no affect or prevent the integration nevertheless, it's recommended to use latest released Update ISO that have 2919355 already integrated
×
×
  • Create New...