1. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
  2. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    You need to prepare the add-ons to be integrated with necessary registry changes, then write the script to automate the tasks.

    I'm not sure if the add-ons your are using are in a format to directly integrate to the wim image mounted.

     
  3. sergey130270

    sergey130270 MDL Member

    May 15, 2014
    190
    76
    10
  4. sergey130270

    sergey130270 MDL Member

    May 15, 2014
    190
    76
    10
    #17584 sergey130270, Nov 22, 2020
    Last edited: Nov 22, 2020
    I cannot copy the addon vcredist_x64 SxS_Win810 to the mounted image

    all others are copied

    Отказано в доступе
    Не удается создать каталог: C:\Win\Integrator10\Mount\Windows\WinSxS

    Скопировано файлов: 16.
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Program Files\Common Files\microsoft shared\VC\msdia100.dll
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Program Files (x86)\Common Files\DESIGNER\mscdrun.dll
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Program Files (x86)\Common Files\DESIGNER\mshtmpgr.dll
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Program Files (x86)\Common Files\DESIGNER\mswcrun.dll
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Program Files (x86)\Common Files\microsoft shared\VC\msdia100.dll
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\466ee.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\466f8.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\46702.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\4670c.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\46716.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\46720.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\4672a.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\46734.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\4673e.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\46748.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_2013d_WinAll\Files\Windows\Installer\4674c.msi[
     
  5. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    If you open the addon vcredist_x64 SxS_Win810.WA with 7-zip program, there will be tasks.txt file.

    Open the tasks.txt with notepad to see which folder or file goes to which folder, then make the changes in the script to copy command.

    copy msdia90.dll to Program Files\Common Files\microsoft shared\VC folder
    copy VC to Program Files (x86)\Common Files\microsoft shared folder
    copy Installer to Windows folder
    copy WinSxS to Windows folder




     
  6. sergey130270

    sergey130270 MDL Member

    May 15, 2014
    190
    76
    10
    Access denied
    Failed to create directory: C: \ Win \ Integrator10 \ Mount \ Windows \ WinSxS
    all others are copied
     
  7. mhussain

    mhussain MDL Senior Member

    Oct 1, 2012
    352
    139
    10
    @MSMG
    thanks for another greate release!
    would it be possible for you to reduce time taken when removeing components?
    thank you for msmg toolkit, you are ausom :)
    how do you make the addon packs for the toolkit?
    could a script be released that will be able to create addon packs for other applications?
    just curious :)
    Majid
     
  8. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    Code:
    md "%MOUNT%\Program Files\Common Files\microsoft shared\VC"
    md "%MOUNT%\Program Files (x86)\Common Files\microsoft shared\VC"
    copy "%~dp0Addons\%HostArchitecture%\Temp\vcredist_x64_SxS_Win810\Files\msdia90.dll" "%MOUNT%\Program Files\Common Files\microsoft shared\VC"
    xcopy "%~dp0Addons\%HostArchitecture%\Temp\vcredist_x64_SxS_Win810\Files\VC\*" "%MOUNT%\Program Files (x86)\Common Files\microsoft shared\VC" /cherkyi
    xcopy "%~dp0Addons\%HostArchitecture%\Temp\vcredist_x64_SxS_Win810\Files\Installer\*" "%MOUNT%\Windows\Installer" /cherkyi
    xcopy "%~dp0Addons\%HostArchitecture%\Temp\vcredist_x64_SxS_Win810\Files\WinSxS\*" "%MOUNT%\Windows\WiSxS" /cherkyi
    
     
  9. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    #17589 MSMG, Nov 22, 2020
    Last edited: Nov 22, 2020
    (OP)
    1) To reduce the speed

    I need to automate the process of removal data at runtime so that the code will be reducded and gets loaded into memory faster.

    or

    Port the code to C++ to run in native mode.

    2) The Toolkit pack contains two things

    - A pack file .tpk which is a WIM image with ESD compression, contains the pack file or folders with original file or folder permissions.
    - A registry file which contains the registry entries for the pack.

    Will release a tutorial for How to create a pack for Toolkit.

     
  10. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    In NSudo did you choose user as TrustedInstaller and choose Enable All Privileges.

     
  11. ingviowarr

    ingviowarr MDL Senior Member

    Dec 14, 2009
    345
    362
    10
    @MSMG

    Proper integrating of .NET 4.8 into LTSC at the LAST STEP is impossible in present logic due to this:
    I.e. when I have CU (KB) for .NET in the WHD folder and proceeding within all needed WU, then MSMG scenario trying to apply all General updates (including .NET CU) while .NET is not yet integrated.
    Then there (logically) will be integrating error 0x800f081e for DotNetRollup
    See my question 2) here

    If I proceed with integrating .NET first and continue with applying all necessary WU (incl. .NET) at the next step, then none of broken logic.
    But .NET 4.8 will be integrated at the beginning, not at the LAST STEP of whole scenario during ISO prepearing.

    This is a logic collision I talking about.

    P.S. Though, in my previous experiments, when I proceeded with integrating .NET 4.8 at the beginning of scenario (the step before WU integration), there were no SFC or other errors in the OS.
    (Of course, I always have 2 cab files for .NET 4.8 in the Packs folder to integrate. The problem is only within .NET CU in WHD folder + steps sequence).
     
  12. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    Yes you need to integrate .NET 4.8 at first, that's what I have specified in the Readme.txt

    .NET FX 3.5/4.8 are feature packs not update, so you need to integrate it before the updates.

     
  13. windows builder

    windows builder MDL Guru

    Sep 13, 2017
    2,210
    1,539
    90
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. ingviowarr

    ingviowarr MDL Senior Member

    Dec 14, 2009
    345
    362
    10
    @MSMG

    Do I need integrate both [x64/x86] files or [x64] only for LTSC ?

    • DirectX9c
    • PowerShell7
     
  15. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    The Toolkit pack contains usually 3 indexes

    1 - 32 bit
    2 - 64 bit
    3 - ARM64

    For DirectX9c Index 2 is used for 64-bit OS.
    For PowerShell7 Index 2 is used for 64-bit OS.

    PS. The PowerShell7 w10 pack index 2 which is the x64 contains both the 32-bit and 64-bit PowerShell 7

     
  16. ingviowarr

    ingviowarr MDL Senior Member

    Dec 14, 2009
    345
    362
    10
    #17596 ingviowarr, Nov 22, 2020
    Last edited: Nov 22, 2020
    @MSMG - Got your post editions. Now I'm fine :)
    Thank you very much!

    (I unserstand things as I should skip [x86] *.reg files for DX9 and PS7 in my LTSC)
     
  17. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    Is this the ISO you are using?

    en_windows_10_consumer_editions_version_20h2_x64_dvd_ab0e3e0a.iso
    en_windows_10_business_editions_version_20h2_x64_dvd_4788fb7c.iso

     
  18. digitalized

    digitalized MDL Novice

    Nov 17, 2017
    30
    9
    0
    No, I am using this one:

    SW_DVD9_Win_Pro_10_20H2_64BIT_English_Pro_Ent_EDU_N_MLF_-2_X22-41520.ISO
     
  19. sergey130270

    sergey130270 MDL Member

    May 15, 2014
    190
    76
    10

    The specified file cannot be found.
    File not found: *
    Files copied: 0.
    File not found: *
    Files copied: 0.
    File not found: *
    Files copied: 0.
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Program Files\Common Files\microsoft shared\VC\msdia90.dll
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Program Files (x86)\Common Files\microsoft shared\VC\msdia80.dll
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Program Files (x86)\Common Files\microsoft shared\VC\msdia90.dll
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Program Files (x86)\Common Files\microsoft shared\VC\amd64\msdia80.dll
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\466c6.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\466d0.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\466da.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\466e4.msi
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\SourceHash{5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4}
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\SourceHash{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\SourceHash{9BE518E6-ECC6-35A9-88E4-87755C07200F}
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\SourceHash{ad8a2fa1-06e7-4b0d-927d-6e54b3d31028}
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\{5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4}\DisplayIcon
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}\DisplayIcon
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\{9BE518E6-ECC6-35A9-88E4-87755C07200F}\DisplayIcon
    C:\Win\Integrator10\Addons\amd64\Temp\vcredist_x64_SxS_Win810\Files\Windows\Installer\{ad8a2fa1-06e7-4b0d-927d-6e54b3d31028}\DisplayIcon
    Access denied
    Unable to create directory: C:\Win\Integrator10\Mount\Windows\WinSxS
     
  20. ingviowarr

    ingviowarr MDL Senior Member

    Dec 14, 2009
    345
    362
    10
    @MSMG

    What is always annoing for me and my feedback how to improve UI.

    1) Switch "Press any key..." to "Enter" only.
    Why? When I want to copy the output info (incl. for you to show / copy the errors) and want press Ctrl+A (to Select all text), it immediatly closed and I always loosing the screen.
    (Forget always about this thing, very unfriendly)

    2) Always back to PREVIOUS menu instead of MAIN.
    Why? To proceed faster. To do everything inside the chosen section, then just press [X] at the end and go to the next part.
    At the present logic I need walk around the same tree 10 times.