1. Magmarock

    Magmarock MDL Member

    Oct 12, 2016
    117
    17
    10
    Nice trick, usually when I'd go to catalog I'd just type "windows 10 version 1809 for x64" which would show a little too much information. But typing "yyyy-mm build number" is better and I just didn't think of it. As for the update post, at the risk of sounding like a noob I just have trouble understanding what I'm looking at. It's too nosy with too much information. Don't worry about simplifying it I'll figure it out.

    Before typing this response I just realized that you're right about NDP48. The update does not actually install dot net. What a stupid system, I was sure MS updates used to put it in. Should I still it from the msu file or the offline installer?
     
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    40,945
    73,235
    450
    What's stupid about installing a feature and next frequently update it? Some want to stay on 4.7.2 (arm64 has no 4.8).

    The info is correct, informative and complete you mean?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Magmarock

    Magmarock MDL Member

    Oct 12, 2016
    117
    17
    10
    Why would anyone want to stay on 4.7.2? 4,8 can do everything it can do right?


    Pretty much. As I said I'll look at it later. At the moment I'm running some tests in virtual machine. I want to see if the dot net updates change anything after 4.8 has already been installed. Then I'll install the updates prior to installing 4.8 and see if that makes a difference.
     
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    40,945
    73,235
    450
    A. is not by dism but a standalone installer.
    B. is the actual one mentioned in the overview.
    I have no idea, i already mentioned arm64 never got .NDP48 on 1809.
    Not according to @abbodi1406 but it doesn't hurt to have it integrated.
    Win 10 can't handle the bundled ssu, win 11 should be able to handle the combined update.
    This was already mentioned here.
    Whatever you desire and fits your situation.
    UUP only provides updates you can use for updating the LTSC ISO.
    Atcually it doesn't use OSCDIMG for updating the ISO, as you were explained a couple of times before, OSCDIMG is for ISO creation. W10UI uses DISM to install/integrate the updates.
    :hangloose:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Magmarock

    Magmarock MDL Member

    Oct 12, 2016
    117
    17
    10
    Yes I know, but why though. Wouldn't 17763.316/19044.1288 save you time because the cab files are already there?
    Whatever you desire and fits your situation.

    I didn't see LTSC listed anywhere on the UUP website, only standard enterprise and home versions.
    My bad
     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    40,945
    73,235
    450
    All three released Enterprise 2019 LTSC ISOs (17763.1/17763.107/17763.316) will get the same updates offered on WU/need the same updates to get uptodate.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. Magmarock

    Magmarock MDL Member

    Oct 12, 2016
    117
    17
    10
    That makes no sense, the high build numbers means already containing the lcu right?

    UUP or MS Catalog?
     
  8. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    5,329
    5,692
    180
    They contain an old LCU and that won't give you any advantage. For integration it's best using a .1 base image, as this will be the leanest at the end.
     
  9. Magmarock

    Magmarock MDL Member

    Oct 12, 2016
    117
    17
    10
    oh, won't the latest lcu still go into them though? Or is it just cleaner way of doing things?
     
  10. AveYo

    AveYo MDL Expert

    Feb 10, 2009
    1,693
    4,937
    60
    There's actually no proof a .1 base is always better. On the contrary, there are counter-examples where the base needs to be a minimal .xxxx so that every feature works correctly.
    Does not matter much what version the superseded components are or how many of them. In the end, the outcome is just as "clean". Plus Windows Update itself expects certain builds, and is actually tuned for the latest esd distribution (and when doing repairs, using the esd build is preferred over using the latest LCU-integrated one) .
    That said, most scripts around MDL, including uupdump stuff are tested more, hence optimized, for the naked .1 builds. So if you use MDL scripts, just follow the instructions to use .1 builds, don't experiment yourself.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    40,945
    73,235
    450
    #72 Enthousiast, Jun 24, 2022 at 21:46
    Last edited: Jun 24, 2022 at 21:52
    Yes, and in the past (and when offline updating) it always was best to start with the baseline wim to integrate updates, specially for when FODs/LPs were integrated too, when done manually one would need to re-integrate the LCU after LPs were integrated but with W10UI that's automated anyway, hence the advise to use it.
    Can you give us an example of this scenario? I only know of (IoT) Enterprise 2021 LTSC, it's officially starting from 19044.1288 (not mentioning the stuff from the, what now has become, the "frankenbuild" thread).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. AveYo

    AveYo MDL Expert

    Feb 10, 2009
    1,693
    4,937
    60
    Yes, it happens more on ltsc-and-above frankenbuilds since product policies gets involved and whatnot. Some editions get supported later on, as an afterthought ;)
    Hit a brick couple times migrating features like refs, deduplication, even store and apps, that went trough when having the older (intermediary?) mums preset as well.
    It's less relevant now with modern versions, but you can still see warnings logged with package versions that happens to be precisely the ones from the esd release (neither .1, nor the integrated latest).
    And does not microsoft themselves author the MVS releases not from the .1 builds, looking at multiple session traces they leave behind? At least, not always. I might be wrong on this one, I have to admin I don't use MVS iso's much, I prefer to always start from the latest esd, then update via WU - it's a safeguard as well, since if WU fails, then the system is not in a good shape.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    40,945
    73,235
    450
    Aren't those traces left behind because they didn't properly cleanup their sysprepped ISOs? But afaik all are still once based on the initial .1 build.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. AveYo

    AveYo MDL Expert

    Feb 10, 2009
    1,693
    4,937
    60
    Not just logs, WinSxS always felt more bloated with more past-versions in their refresh than the equivalent uupdump made for example.
    Did not do a hard-compare tough - I tend to bork those, remember the IoT vs. non-IoT LTSC I made - it was epic fail ;)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...