[DISCUSSION] Windows 11 Enterprise/IoT Enterprise (N) LTSC 2024 (24H2 / 26100.x)

Discussion in 'Windows 11' started by Enthousiast, Apr 26, 2024.

  1. petersonic

    petersonic MDL Novice

    Jan 4, 2011
    3
    1
    0
  2. Errepublika

    Errepublika MDL Senior Member

    Aug 18, 2021
    453
    317
    10
    The full package does not at the end leave you an ISO 26100.1742 now I am trying if it supports only the Windows11.0-KB5043080-x64.
     
  3. Errepublika

    Errepublika MDL Senior Member

    Aug 18, 2021
    453
    317
    10
    #1743 Errepublika, Sep 28, 2024
    Last edited: Sep 28, 2024
    Delete
     
  4. egyptian hak

    egyptian hak MDL Senior Member

    Aug 21, 2009
    304
    79
    10
    after installing win 11 iot ltsc 2024 26100.1742
    why there is no windows explorer new tab ? how can i activate?

    upload_2024-9-28_17-21-12.png
     
  5. Errepublika

    Errepublika MDL Senior Member

    Aug 18, 2021
    453
    317
    10
    I think what you have is the old explorer of Windows 10 that's why you have no tabs.
     
  6. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,035
    378
    60
    Two questions please:
    1) Is there a ru-ru LTSC image, or I have to create one myself with W10MUI?
    2) Can I add Windows11.0-KB5043178-x64.msu to image? I tried with W10UI and it fails:
    Code:
    An error occurred applying the Unattend.xml file from the .msu package.
    For more information, review the log file.
     Error: 0x800f0825
     
  7. Paul Mercer

    Paul Mercer MDL Guru

    Apr 6, 2018
    2,084
    4,363
    90
    1. localized non-eval ISO are not yet released
    2. you should put all LCU MSU in one folder (checkpoint + LCU) and integrate only the highest one with dism
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. Errepublika

    Errepublika MDL Senior Member

    Aug 18, 2021
    453
    317
    10
    There is no ru-ru LTSC image and if you have to create it with W10MUI if you had read above that Windows11.0-KB5043178-x64.msu bug was already commented it does not let you add with W10UI the update to 26100.1876 gives error.
     
  9. Paul Mercer

    Paul Mercer MDL Guru

    Apr 6, 2018
    2,084
    4,363
    90
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Paul Mercer

    Paul Mercer MDL Guru

    Apr 6, 2018
    2,084
    4,363
    90
    no, you can't integrate KB5043178, you should integrate KB5043080 and KB5043178, but not one by one
    also don't forget to integrate the latest SSU before that

    after SSU integration you should create new empty folder, put Windows11.0-KB5043080-x64.msu and Windows11.0-KB5043178-x64.msu there and nothing else
    then use dism like usual
    Code:
    dism /Image:F:\mount /Add-Package /PackagePath:"F:\UUPs\Windows11.0-KB5043178-x64.msu"
    in this example only the highest one is being integrated, and it works

    111.jpg

    I literally just tested this with X23-81951_26100.1742.240906-0331.ge_release_svc_refresh_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,035
    378
    60
    Thanks!
    "Not one by one" means in one session?
    My problem is that I am adding ru-ru language pack to 26100.1742 image.
    LP is 26100.1, so after adding I reapply KB5043080 (26100.1742) and want to add KB5043178 (26100.1876)
    What do I need to achieve that?
     
  12. Paul Mercer

    Paul Mercer MDL Guru

    Apr 6, 2018
    2,084
    4,363
    90
    one by one:
    Code:
    dism /Image:F:\mount /Add-Package /PackagePath:"F:\UUPs"
    and it's the same as
    Code:
    dism /Image:F:\mount /Add-Package /PackagePath:"F:\UUPs\Windows11.0-KB5043080-x64.msu" /PackagePath:"F:\UUPs\Windows11.0-KB5043178-x64.msu"

    correct way (not one by one):
    Code:
    dism /Image:F:\mount /Add-Package /PackagePath:"F:\UUPs\Windows11.0-KB5043178-x64.msu"
    integrating only KB5043178 doesn't mean you can integrate it alone, it wouldn't work, you always need checkpoint update in the same folder

    will try to test it too, but only with the LP (too much hassle for FoDs)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,035
    378
    60
    Thank you for help!
     
  14. Giacomino1968

    Giacomino1968 MDL Senior Member

    Feb 23, 2023
    252
    131
    10
    Maybe someone can explain me why everybody wants to integrate KB5043178 to 26100.1742 ISO.
    For what purpose?
     
  15. Paul Mercer

    Paul Mercer MDL Guru

    Apr 6, 2018
    2,084
    4,363
    90
    to test MSFT's mess
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,035
    378
    60
    Exactly.
    Un my case, to test image.
    I prefer .1 images, and found that I can update 26100.1 to .1876, while if I get new ISO, I can't
     
  17. Giacomino1968

    Giacomino1968 MDL Senior Member

    Feb 23, 2023
    252
    131
    10
    #1760 Giacomino1968, Sep 28, 2024
    Last edited: Sep 28, 2024
    Ok, but in this case it wouldn"t be easier to install 26100.1742 ISO then try to install KB5043178 manually?
    Or install 26100.1 ISO, update it (during installation process and via WU) then try to install KB5043178 manually?
    Anyway better to wait for new update from WU...