1. LordVardus

    LordVardus MDL Novice

    Apr 4, 2018
    36
    6
    0
    #7681 LordVardus, Sep 3, 2018
    Last edited: Sep 3, 2018
  2. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    Usually I don't recommend MS refreshed source images because

    - Previously the DISM had issues in removing Apps, But now I don't know whether that issue still exists or not.
    - By the time the MS releases a refreshed ISO, the updates contained in the image are outdated.

    With the latest Windows 10 RS4 LCU, removing WMP breaks the windows setup, so I do not recommend removing it or use the original image remove the components and then integrate the updates/install updates through WU.



     
  3. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    #7685 MSMG, Sep 4, 2018
    Last edited: Sep 4, 2018
    (OP)
    Yes, I think, I did removed it since it didn't work on Windows 8.1, anyway will checkout again.

     
  4. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    As earlier said, the Microsoft has made it more difficult to remove components by merging several removable components into main packages and so the usual method of using DISM to remove a component wont work anymore.

    Starting from next version of Toolkit (command-line), As a starting point the Toolkit will start the process of using the manual method (ToolKitHelper.exe) to remove all components for Windows 10 RS3 (MUI), RS4 (MUI) Source OS's.

    If there is no new W10 RS5 build until next week then support for W10 RS5 Build 17751.1 (en-GB/en-US) Source OS will also be added for testing.

    The component removal for other Source OS's will be removed temporarily and will be added back when it's ready to use the manual method (ToolKitHelper.exe).

    People using the ToolKit to remove components for other Source OS's do stick with the current version.
     
  5. Tiger-1

    Tiger-1 MDL Guru

    Oct 18, 2014
    8,326
    11,613
    270
    Hello MSMG, out of pure curiosity my programming language uses the ToolkitHelper.exe or manual method since from now on we will not be able to use Dism anymore because of its limitations maybe from now on would be the Powershell? or something similar to the Chocolatey staff ...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    It's not that DISM can't remove any packages but only the packages that are merged can't be removed properly.

    I don't know Powershell programming and also it's bit slow in execution.

    The current Toolkit script needs to be cleaned up and refactored, I'm thinking of using the C# instead of batch for Toolkit command-line and so both the CMD and GUI will be using the same programming language.

     
  7. roedel

    roedel MDL Junior Member

    Jun 3, 2010
    82
    58
    0
    Hi MSMG,

    if you need any help ( sadly I´m not a programmer :( ) or beta tester, please let us know :)
     
  8. LordVardus

    LordVardus MDL Novice

    Apr 4, 2018
    36
    6
    0
    no, there are no updates integrated and no removed WMP
    So as I understand it, I may not remove components because otherwise the abild breaks
    Is there no solution that could handle it?
     
  9. rayleigh_otter

    rayleigh_otter MDL Expert

    Aug 8, 2018
    1,120
    933
    60
    Whats the bet that will be cortana store and anything telemetry related.
     
  10. Tiger-1

    Tiger-1 MDL Guru

    Oct 18, 2014
    8,326
    11,613
    270
    ok yep good luck with C# I'm here for make test when necessary
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    54,966
    125,941
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. ctrbuddy

    ctrbuddy MDL Novice

    May 16, 2017
    3
    0
    0
    OK, so I am not finding this anywhere so maybe someone can help. I am attempting to make a stripped down version for a Mac Boot Camp version. After all I would like to not have as much bloat. So I am using Win 10 1803 and when I am finished the size of the file is over 6 gigs. I need to get this file less than 4 gigs to boot camp. What am I doing wrong?
     
  13. tefor

    tefor MDL Senior Member

    Apr 5, 2017
    317
    240
    10
    You have to rebuild the image at final stage (6-1) for a smaller size of the wim
     
  14. biatche

    biatche MDL Addicted

    Nov 14, 2009
    573
    144
    30
    msmg with rs5 being out soon, will transition to new version be easier than before for you? (since you probably have tested latest rs5 builds)
     
  15. ctrbuddy

    ctrbuddy MDL Novice

    May 16, 2017
    3
    0
    0
    That is what I am doing but it still ends up at 6+ gigs. I am just removing, not adding anything. How do I have it just be the Pro x64 version? I won't need the rest.
     
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    54,966
    125,941
    450
    Removing stuff doesn't always end in a decrease of the size of the wim.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. aquarius84

    aquarius84 MDL Member

    Oct 3, 2012
    205
    61
    10
    Hi, I integrated ahci drivers (for Windows 7 x64), putting drivers into "Drivers\WinPE\w7\x64" folder, to have integrated into boot.wim (as I understood), but when I start Windows setup from boot I got error:

    Windows failed to start.....
    file: iaStorAC.sys
    Status: 0x0000098

    what did I done wrong? (i just checked the file "iaStorAC.sys" was in the folder)