abbodi1406's Batch Scripts Repo

Discussion in 'Scripting' started by abbodi1406, May 4, 2017.

  1. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    55,796
    129,794
    450
    I go for the default settings;):p:D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. Paul Mercer

    Paul Mercer MDL Guru

    Apr 6, 2018
    2,147
    4,493
    90
    too much complexity for something simple: LCUmsuExpand=3 for boot.wim 26100+ builds works in every scenario
     
  3. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,818
    101,326
    340
    Where is the fun in following Microsoft wrong steps
     
  4. Paul Mercer

    Paul Mercer MDL Guru

    Apr 6, 2018
    2,147
    4,493
    90
    #4264 Paul Mercer, Sep 24, 2026 at 22:25
    Last edited: Sep 24, 2026 at 22:31
    what is the point of adding this for W10MUI only if it's impossible to integrate 1742 LCU into boot.wim if the latest SSU was integrated first?

    1742 LCU can't be integrated even into 26100.1 boot.wim

    the real question is if you should skip the latest SSU or not (I think the latest SSU is fine, and LCUmsuExpand=3 is fine, it just works just like msft intended)
     
  5. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,818
    101,326
    340
    "intended" is a exaggerated word to describe msft chaos changes with 26100

    if or when they backport 26340 changes (where LCU update.cat is used to verify most sub-packages, instead .cat file for each .mum, and mumx.esd is required), then LCUmsuExpand will be dead for 26100, and "intended" msu installation will be the only choice

    unless we find a way to extract collection.mumx :rolleyes: