1. nokialpha

    nokialpha MDL Novice

    Aug 14, 2016
    7
    7
    0
    Current package/registry of Vcruntime which is available on mega is corrupted don't integrate that package.....already reported by some user when toolkit 9.6 was released, wait for fix

    If you have a backup of old vcruntime packages then use that package(merge all splitted registry into one single file then rename them according to new files then integrate those)
     
  2. kuroda

    kuroda MDL Senior Member

    Aug 25, 2012
    445
    32
    10
    ...well, the problem was when integrating VCRuntime in 19041 causes a conflict, MSMG did you test VCRuntime in 19041?
    .....ok, sorry i didn't see the comments on VCRuntimes corruption, thanks!
     
  3. mstms

    mstms MDL Novice

    Sep 27, 2018
    11
    0
    0
    when?
     
  4. hildegard

    hildegard MDL Novice

    Nov 26, 2015
    25
    11
    0
    Please stop asking when an update is ready, it's done when it's done.

    MSMG does his best and improves his Toolkit by a lot. It's the number 1 solution for me to improve privacy for a Windows 10 installation.
     
  5. Feartamixg

    Feartamixg MDL Addicted

    May 15, 2016
    786
    631
    30
    Be patent, @MSMG will release when it is good and not before.
     
  6. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    #14646 MSMG, Apr 5, 2020
    Last edited: Apr 5, 2020
    (OP)
    Updated the Toolkit to v9.8

    Change-log:

    v9.8
    + Fixed a Bug in the Remove Windows Components-> Windows Apps-1 Menu items choice selection.
    + Fixed a Bug in the Feature "Remove Windows Components", where the Component Removal was not working with non en-US source images.

    Edit: Re-released the version.
     
  7. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    I do usually stick with the first released image service pack build like the v1809 (v10.0.17763.1) but since starting v1903 installing updates was restoring the removed components I had to keep updating the removal for latest CU and had to maintain the removal for v10.0.18362.1, v10.0.18362.30 and with the latest CU

    And when the v1909 was announced I replaced v1903 removal with the v1909 (v10.0.18363.418) as base image and even today it is base version required for v1909 removal and also works with the latest CU.

    For v2004 also this will repeat when it's officially released, the officially released image service pack build will become the new and permanent base image.

     
  8. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    Yes but v1809 support is reaching it's EOL and also it won't work properly with the latest AMD Ryzen processors.

     
  9. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    It seems Edge pack needs to be checked with each Windows 10 versions, if it requires any changes or not, but for W7 and W81 it's working properly.

    Same is the case for VC-Runtimes, do wait until it's fixed.

     
  10. wolive

    wolive MDL Novice

    Oct 24, 2009
    5
    6
    0
     
  11. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    Something went wrong while publishing the new version in the Toolkit's website and the download page in the website is not working, it will fixed later.

    Edit: It's working now.
     
  12. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    #14653 MSMG, Apr 5, 2020
    Last edited: Apr 5, 2020
    (OP)
    Wait will check the script again regarding the version.

    Edit: Ok the version was not updated in the script, will re-release the build in a while now.

    As far the integration it works with 1809/1903/1909 images with any service pack builds.

     
  13. wolive

    wolive MDL Novice

    Oct 24, 2009
    5
    6
    0
    @MSMG
    When selecting [3] Integrate / [3] Windows features, option [5] Windows Custom Features is presented instead:

    ===============================================================================
    MSMG ToolKit - Integrate Windows Custom Features Menu
    ===============================================================================



    W A R N I N G
    =============

    Integrating Windows Custom Features involves patching system files and so
    the SFC can report about Windows System Files corruption, This is normal.








    To turn off Warning Dialogs, Choose Disable Dialogs in Tools->Options Menu

    ===============================================================================

    Do You Want to Continue ? ['Y'es/'N'o] :

    Debug Information:
    ===============================================================================
    MSMG ToolKit - Debug Information
    ===============================================================================
    HostArchitecture=x64
    SelectedSourceOS=w10
    IsSourceSelected=Yes
    IsDialogsEnabled=Yes
    IsLogsEnabled=Yes

    ImageIndexNo=1
    ImageName=Windows 10 Enterprise
    ImageDescription=Windows 10 Enterprise
    ImageArchitecture=x64
    ImageBuild=18363
    ImageVersion=10.0.18363
    ImageServicePackBuild=753
    ImageServicePackLevel=0
    ImageEdition=Enterprise
    ImageFlag=Enterprise
    ImageInstallationType=Client
    ImageDefaultLanguage=en-US
    ImageCount=1
    ===============================================================================

    Any advice on what the problem could be?
     
  14. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    Yes modifying any system dll files will trigger SFC errors, if you are just adding custom user pictures then it won't have issues but adding custom skins for WMP, PhotoViewer, Calculator will have issues with SFC.

     
  15. nokialpha

    nokialpha MDL Novice

    Aug 14, 2016
    7
    7
    0
    #14660 nokialpha, Apr 5, 2020
    Last edited: Apr 5, 2020