1. kiczkabog

    kiczkabog MDL Novice

    Jun 13, 2021
    9
    3
    0
    Why i can't remove components from win11. Error like not supported OS pop-up.
     
  2. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,770
    3,601
    60
    We have to wait for update that supports versions of Windows 11. This is provided by MSMG for the application "Toolkithelper.exe". For now only removal through DISM list. Template lists are available within the ".\Bin\Lists" folder. Take a look there, read the main post and readme, and make your "RemoveAppsList.txt". It is interesting to enter the remove menus and see the prerequisites to be able to set up an image without headaches.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. jinvidia

    jinvidia MDL Member

    Aug 7, 2016
    238
    36
    10
  4. graver.x

    graver.x MDL Senior Member

    Jan 18, 2020
    349
    486
    10
    #20245 graver.x, Aug 31, 2021
    Last edited: Aug 31, 2021
    I don't think that at this stage it is very important for you to integrate SSU + LCU into boot.wim and winre.wim. The updates will be integrated successfully, you can be sure of it.
    But now it is important to find out the reason for the previous error. Therefore, I suggested a shorter and simpler way - integration of only SSU + LCU, and only into install. wim:

    (2) Integrate -> (4) Windows Updates -> (2) Integrate WHD Update Pack -> (1) Integrate WHD General Updates -> (2) Integrate to Windows Setup Install Image

    The bottom line is to abandon the integration of the remaining updates for now (windows10. 0-kb5003714 - x64.cab - DU for sources & windows10.0-kb4506578 - x64.cab - for WinPE), and check the installation.
     
  5. balanadi

    balanadi MDL Senior Member

    Apr 24, 2014
    389
    696
    10
    I have a small problem when i try to Integrate Microsoft Visual C++ Runtime

    "===============================================================================
    MSMG ToolKit - Integrate Microsoft Visual C++ Runtime
    ===============================================================================

    Microsoft Visual C++ Runtime Pack file "VC_2019_x64.reg" not found...

    Please copy the above file to <Packs\VCRuntime\w10> folder...

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

    Press any key to continue . . . "

    this is happening after the august update of the component folder of Microsoft Visual C++ Runtime which include version 2022 and missing 2019...

    Can you advice me for a work around solution ?
     
  6. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,770
    3,601
    60
    #20247 inTerActionVRI, Aug 31, 2021
    Last edited: Sep 1, 2021
    @Bira informed me that the integration of WMP Metro Skin is breaking WMP in Windows 81. However my daily use machine (build 18363.1440 installed on 2021-04-11) is with the skin applied and I went to check, it also does not work . I have now tested for 17763.2114, it does not work as well.
    If someone else tests in some version above 18363.1734 and does not work, please leave feedback.

    I modified the script to take a test by applying the Skin Metro in an X64 image in both "Program Files" and "Program Files (X86) folders." Currently the script only applies in the "Program Files" folder. However the WMP of the "Program Files (x86)" folder that did not receive Metro Skin integration, works correctly. I believe I'm wasting time, but I'll make one more of this test on the Build 18363.1734. If there is a problem, I will allow the recommendation to avoid the integration of WMP Metro Skin for now.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,770
    3,601
    60
    Download the new Pack and new Toolkit.cmd.
    VC 2022 replaces VC 2019.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,770
    3,601
    60
    Tested on Build 18363.1734 x64. It was integrated "Windows Media Player Metro Skin" in both folders "Program Files" and WMP works OK.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. jinvidia

    jinvidia MDL Member

    Aug 7, 2016
    238
    36
    10
    @MSMG - Sir is it possible to create a WIM based ISO, exit the toolkit and if needed I can create a ESD based ISO directly by using the convert option ?. This works fine right ?. I mean i can create a compressed ESD based ISO in this case without doing everything from scratch, right ?
     
  10. jinvidia

    jinvidia MDL Member

    Aug 7, 2016
    238
    36
    10
    Did as per your suggestions, but this time i am able to install windows however none of the dot net components were integrated. And I hope skipping the component storage cleanup is not the cause for this.

    Also tried 17763.1999 obtained from uupdump and after servicing with 11.6 (which is the appropriate version for FU 1999), the installed o/s has no dotnet. Any ideas ?
     
  11. balanadi

    balanadi MDL Senior Member

    Apr 24, 2014
    389
    696
    10
    THANKS ... i managed to integrate in 17763.2145 LTSC and 19041.1202 CORE

    My question now is if this skin is possible to be integrated also in 14393.4583 LTSB , taking in consideration that the icons are situated in imageres.dll ?

    Thanks for advice ...
     
  12. Bira

    Bira MDL Senior Member

    Oct 4, 2017
    364
    210
    10
    #20253 Bira, Sep 2, 2021
    Last edited: Sep 2, 2021
    Capturar_2021_09_01_22_09_07_301.png Capturar_2021_09_01_22_09_24_944.png Capturar_2021_09_01_22_10_00_680.png Capturar_2021_09_01_22_10_23_886.png
     
  13. balanadi

    balanadi MDL Senior Member

    Apr 24, 2014
    389
    696
    10
    #20254 balanadi, Sep 2, 2021
    Last edited: Sep 2, 2021
  14. 1kari

    1kari MDL Novice

    Oct 14, 2018
    19
    9
    0
    Good afternoon. How do I disable the automatic installation of Microsoft Edge when I upgrade Windows? The solutions I found don't work... Has anyone found a solution?
     
  15. jinvidia

    jinvidia MDL Member

    Aug 7, 2016
    238
    36
    10
    I have created a 17763.1577 iso downloaded from uupdump, serviced with with v10.9 and after installation i see there is no dotnet in the o/s. Moreover applications like kaspersky internet security fail to install like i experienced before. Can you please give me the source of the 17763.1577 (is it from uupdump ?) you obtained and enumerate the steps you followed to make the ISO with integration of dotnet 3.5 & 4.8 ?. Thanks
     
  16. jinvidia

    jinvidia MDL Member

    Aug 7, 2016
    238
    36
    10
    Have you successfully integrated dotnet 3.5 & 4.8 without sfc errors ? If so..
    Kindly provide the link to the source ISO or the ISO filename and the steps you performed to create 17763.2145 ltsc and the version of toolkit used. Thanks
     
  17. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,770
    3,601
    60
    #20258 inTerActionVRI, Sep 3, 2021
    Last edited: Sep 3, 2021
    @MSMG,

    replace all
    from
    Code:
     /t REG_SZ /d " " >nul 2>&1
    
    to
    Code:
     /t REG_SZ /d " " /f >nul 2>&1
    

    and...
    from
    Code:
                   Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersion" /t REG_DWORD /d "1" >nul 2>&1
                   if "%ImageBuild%" equ "17134" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "1803" >nul 2>&1
                   if "%ImageBuild%" equ "17763" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "1809" >nul 2>&1
                   if "%ImageBuild%" equ "18362" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "1903" >nul 2>&1
                   if "%ImageBuild%" equ "18363" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "1909" >nul 2>&1
                   if "%ImageBuild%" equ "19041" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "2004" >nul 2>&1
                   if "%ImageBuild%" equ "19042" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "2009" >nul 2>&1
                   if "%ImageBuild%" equ "19043" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "21H1" >nul 2>&1
                   if "%ImageBuild%" equ "19044" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "21H2" >nul 2>&1
                   if "%ImageBuild%" equ "20348" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "21H2" >nul 2>&1
                   if "%ImageBuild%" equ "22000" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "21H2" >nul 2>&1
    
    
    to
    Code:
                   Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersion" /t REG_DWORD /d "1" /f >nul 2>&1
                   if "%ImageBuild%" equ "17134" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "1803" /f >nul 2>&1
                   if "%ImageBuild%" equ "17763" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "1809" /f >nul 2>&1
                   if "%ImageBuild%" equ "18362" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "1903" /f >nul 2>&1
                   if "%ImageBuild%" equ "18363" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "1909" /f >nul 2>&1
                   if "%ImageBuild%" equ "19041" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "2004" /f >nul 2>&1
                   if "%ImageBuild%" equ "19042" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "2009" /f >nul 2>&1
                   if "%ImageBuild%" equ "19043" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "21H1" /f >nul 2>&1
                   if "%ImageBuild%" equ "19044" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "21H2" /f >nul 2>&1
                   if "%ImageBuild%" equ "20348" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "21H2" /f >nul 2>&1
                   if "%ImageBuild%" equ "22000" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "21H2" /f >nul 2>&1
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. balanadi

    balanadi MDL Senior Member

    Apr 24, 2014
    389
    696
    10
    1. i use as a base 17763.1_Windows_10_Enterprise_LTSC_LiteR_amd64_en-US.install.wim made without many of the crap
    2. i integrate Windows10.0-KB4486153-x64 and microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~
    3. i am using the NTLITE program to integrate and remove the unnecessary components
    4. i use Toolkit_v11.7 to add VC ++ and skins
    i never used Toolkit_v11.7 to integrate updates or remove components cause i have my own scripts to do that using the Dism .
    all my updated iso images are quite lite and very good for day to day use ...