1. LostED

    LostED SVF Patch Lover

    Jul 30, 2009
    7,155
    21,099
    240
    @mhussain

    mirrors updated
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. mhussain

    mhussain MDL Senior Member

    Oct 1, 2012
    352
    139
    10
    thanks so much!
     
  3. Dusktilldawn

    Dusktilldawn MDL Junior Member

    Oct 24, 2009
    51
    10
    0
    hi there is no `PowerShell7_w7.tpk file in the packs
    is it done for any purpose
    or missed
    thanks


    ok I saw the releated other message///
     
  4. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,488
    210
    I'm uploading the missing pack files now, do check later.

     
  5. Dusktilldawn

    Dusktilldawn MDL Junior Member

    Oct 24, 2009
    51
    10
    0
    Hello friends:
    I am trying to integrate "Windows 10 v1809"
    my question is about to "update files places'
    I read the introductions
    but still straggling to put files
    introduction says:
    If using WHD Update Pack Menu, then Copy the Windows 10 WHD Update Pack files to Toolkit's <WHD\w10\<Architecture> folder (E.g. <WHD\w10\x64>).
    Copy Windows Cumulative Update file to <WHD\w10\<Architecture>\Cumulative> folder (E.g. <WHD\w10\x64\Cumulative>).
    Copy Windows Dynamic Update files to <WHD\w10\<Architecture>\Dynamic> folder (E.g. <WHD\w10\x64\Dynamic>).
    Copy Windows Flash Player Update file to <WHD\w10\<Architecture>\FlashPlayer> folder (E.g. <WHD\w10\x64\FlashPlayer>).
    Copy Windows .Net Cumulative Update file to <WHD\w10\<Architecture>\NetCumulative> folder (E.g. <WHD\w10\x64\NetCumulative>).
    Copy Windows Servicing Stack Update file to <WHD\w10\<Architecture>\ServicingStack> folder (E.g. <WHD\w10\x64\ServicingStack>).
    Copy Windows Setup Media Update files to <WHD\w10\<Architecture>\SetupMedia> folder (E.g. <WHD\w10\x64\SetupMedia>).
    Copy Windows WinPE Update files to <WHD\w10\<Architecture>\WinPE> folder (E.g. <WHD\w10\x64\WinPE>).
    but I dont know which files are which categories:
    here is the my update files:
    Windows10.0-KB4486153-x64-NDP48.msu (???????)
    windows10.0-kb4494174-v3-x64 intel microcode update (???????)
    Windows10.0-KB4558997-x64 (servicing stack)
    Windows10.0-KB4558998-x64 (Cumulative Update)
    Windows10.0-KB4559003-x64 (I thing to cumulative too)
    windows10.0-kb4561600-x64 (Adobe Flash Player Update)
    Windows10.0-KB4562901-x64-NDP48 (???????)
    Windows10.0-KB4565632-x64-NDP48 (???????)

    thanks in advance
     
  6. windows builder

    windows builder MDL Guru

    Sep 13, 2017
    2,210
    1,539
    90
    put all updates to Toolkit_v10.2\Updates\w10\x64 folder.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. simple-hormiga

    simple-hormiga MDL Novice

    Apr 18, 2012
    22
    12
    0
    what am I doing wrong? I use 19042.421, i integrate win32 calculator and remove Windows apps and components


    Code:
    ===============================================================================
       MSMG ToolKit - Cleanup Source Images with Component Cleanup & ResetBase
    ===============================================================================
    
    -------------------------------------------------------------------------------
    ####Starting Cleaning Up Source Images with Component Cleanup & ResetBase######
    -------------------------------------------------------------------------------
    
    -------------------------------------------------------------------------------
    Performing [Install.wim, Index : 1] Image Component Cleanup...
    -------------------------------------------------------------------------------
    
    Cannot Perform Image Component Cleanup when Pending.xml is present...
    
    -------------------------------------------------------------------------------
    ####Finished Cleaning Up Source Images with Component Cleanup & ResetBase######
    -------------------------------------------------------------------------------
    
    ===============================================================================
    
    Presione una tecla para continuar . . .

    Code:
    ===============================================================================
                           MSMG ToolKit - Debug Information
    ===============================================================================
     HostArchitecture=x64
     SelectedSourceOS=w10
     IsSourceSelected=Yes
     IsDialogsEnabled=Yes
     IsLogsEnabled=Yes
    
     ImageIndexNo=1
     ImageName=Windows 10 Home
     ImageDescription=Windows 10 Home
     ImageArchitecture=x64
     ImageBuild=19042
     ImageVersion=10.0.19042
     ImageServicePackBuild=421
     ImageServicePackLevel=0
     ImageEdition=Core
     ImageFlag=Core
     ImageInstallationType=Client
     ImageDefaultLanguage=es-ES
     ImageCount=3
    ===============================================================================
    Presione una tecla para continuar . . .
     
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,292
    94,825
    450
    Asked the staff for cleanup/removal of the post above.
     
  9. tefor

    tefor MDL Senior Member

    Apr 5, 2017
    307
    235
    10
    There is no double menus problem with newer Toolkit.cmd :thumbsup:
    Thank you MSMG
     
  10. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,488
    210
    For integrating .NET 3.5 or .NET 4.8 use the Toolkit's Integrate Windows Features->Integrate Microsoft .NET 3.5/4.8 Framework menu.

    For integrating updates use the WHD update pack menu and copy the updates as per the following path.

    Code:
    ToolKit\WHD\w10\x64\Cumulative\windows10.0-kb4559003-x64_00929084421dfd5298fe475f80d38308783dd376.msu
    ToolKit\WHD\w10\x64\Dynamic\windows10.0-kb4494174-v3-x64_9c36175029e926f7d98c38765707f976aac882a9.msu
    ToolKit\WHD\w10\x64\FlashPlayer\windows10.0-kb4561600-x64_00504a2c48850e3897caa5f9f9527881e87af0dd.msu
    ToolKit\WHD\w10\x64\NetCumulative\windows10.0-kb4562901-x64-ndp48_632aad037dc2ed46feb650d0b5c9a613da469220.msu
    ToolKit\WHD\w10\x64\ServicingStack\windows10.0-kb4558997-x64_9c9a7137d609ef46898bba95e204e6c867a9aa12.msu
    ToolKit\WHD\w10\x64\SetupMedia\windows10.0-kb4538460-x64_caa049311a96840f81a2b0efff5c35a7986d75a3.cab
    
     
  11. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,488
    210
    with 19042 enablement package the Edge Chromium triggers the pending.xml flag and so you can't perform the cleanup.

     
  12. tungtien

    tungtien MDL Novice

    Aug 8, 2009
    21
    5
    0
    Tested v10.2
    can't remove Cortana 19041/2.421

    source uupdump 10 iot ent
    remove windows components > all systems + windows apps
    Cleanup > Apply changes to image > Rebuild
     
  13. Creater Cyfire

    Creater Cyfire MDL Novice

    Aug 31, 2017
    18
    7
    0
    I've got another question related to the driver integration. Is it generally a good practice to be adding lots of drivers to an image?
    More specifically, does the integration add all the drivers into some sort of repository within the system only to be active if a relevant piece of hardware is detected, or will it bloat up the system if you add too many drivers?
     
  14. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,651
    3,398
    60
    @MSMG,
    Error 87 when we select a specific range, in this case from 3 to 4 (3-4). I hadn't used that function yet. Only used "*".
    Dism Log attached.

    Image : Install.wim
    Image Indexes No : 1-5
    Image Architecture : x86
    Image Version : 10.0.18362
    Image Service Pack Build : 959

    ===============================================================================
    MSMG ToolKit - Select Source from <DVD> folder
    ===============================================================================

    -------------------------------------------------------------------------------
    ####Selecting Source Images####################################################
    -------------------------------------------------------------------------------

    Reading Image Information...

    ===============================================================================
    | Index | Arch | Name
    ===============================================================================
    | 1 | x86 | Windows 10 Home
    | 2 | x86 | Windows 10 Education
    | 3 | x86 | Windows 10 Pro
    | 4 | x86 | Windows 10 Pro Education
    | 5 | x86 | Windows 10 Pro for Workstations
    ===============================================================================

    Enter the Image Index's # [Range : 1-5, * - All] : 3-4

    Do you want to mount Windows Setup Boot Image ? ['Y'es/'N'o] : N

    Do you want to mount Windows Recovery Image ? ['Y'es/'N'o] : N

    -------------------------------------------------------------------------------
    ####Source Image Information###################################################
    -------------------------------------------------------------------------------

    Image : Install.wim
    Image Index No : 3-4
    Image Name : ~1
    Image Description : ~1
    Image Architecture :
    Image Version : 10.0.20175.1000
    Image Service Pack Build : ~1
    Image Service Pack Level : ~1
    Image Build : .201
    Image Edition :
    Image Flag :
    Image Installation Type : ~1
    Image Default Language : ~1,-10

    -------------------------------------------------------------------------------
    ####Mounting Source Images#####################################################
    -------------------------------------------------------------------------------

    -------------------------------------------------------------------------------
    Mounting [Install.wim, Index : 3-4] Image at <\Mount\Install>...
    -------------------------------------------------------------------------------

    Deployment Image Servicing and Management tool
    Version: 10.0.20175.1000


    Error: 87

    An error occurred while processing the command.
    Ensure that the command-line arguments are valid. For more information, review the log file.

    The DISM log file can be found at C:\ToolKit\Logs\Dism.txt

    -------------------------------------------------------------------------------
    ####Finished Selecting & Mounting Source Images################################
    -------------------------------------------------------------------------------

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

    ===============================================================================
    MSMG ToolKit - Discard Changes & Unmount Source Images
    ===============================================================================

    -------------------------------------------------------------------------------
    ####Starting Discarding Changes & Un-Mounting Source Images####################
    -------------------------------------------------------------------------------

    -------------------------------------------------------------------------------
    Un-Mounting Source [Install.wim, Index : 3-4] Image...
    -------------------------------------------------------------------------------

    Deployment Image Servicing and Management tool
    Version: 10.0.20175.1000


    Error: 50

    DISM failed. No operation was performed.
    For more information, review the log file.

    The DISM log file can be found at C:\ToolKit\Logs\Dism.txt

    -------------------------------------------------------------------------------
    ####Finished Discarding Changes & Un-Mounting Source Images####################
    -------------------------------------------------------------------------------

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

    Attached Files:

  15. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,488
    210
    Will check with that image.

     
  16. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,488
    210
    The Toolkit uses the standard DISM tool to perform image operations and for driver integration also it uses the same tool, Adding too many drivers can increase the image size.