Windows 11 ESD Repository

Discussion in 'Windows 11' started by Enthousiast, Jul 1, 2021.

  1. Pikylusk

    Pikylusk MDL Novice

    Apr 21, 2020
    2
    0
    0
    #181 Pikylusk, Jan 3, 2023
    Last edited: Jan 3, 2023
    Hi, I have downloaded this file:
    22621.525.220925-0207.ni_release_svc_refresh_CLIENTCONSUMER_RET_A64FRE_it-it.esd
    and then converted with esd-decrypter script but I don't understand why after conversion the ISO file name is different:
    22621.525.220924-1919.NI_RELEASE_SVC_IM_CLIENTCONSUMER_OEMRET_A64FRE_IT-IT.iso

    Where I'm wrong?
     
  2. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    14,365
    73,919
    340
    @Pikylusk
    Nothing wrong, it's cosmetic
    ESD name (label) is set manually by Microsoft, it cannot be detected from ESD contents itself

    just edit decrypt.cmd and change 0 to 1
    Code:
    set ISOnameESD=0
     
  3. Pikylusk

    Pikylusk MDL Novice

    Apr 21, 2020
    2
    0
    0
    Thanks <3
     
  4. lnxusr

    lnxusr MDL Novice

    Feb 15, 2018
    3
    1
    0
    How am I supposed to verify the hash of the refresh releases?

    I see a hash value at the end of the filename of the 22h2 base release. but all the refresh releases lack the hash value in the filename. give me a hint.
     
  5. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    14,365
    73,919
    340
  6. lnxusr

    lnxusr MDL Novice

    Feb 15, 2018
    3
    1
    0
  7. Paul Mercer

    Paul Mercer MDL Senior Member

    Apr 6, 2018
    480
    898
    10
    22621.525 and 22621.382 links has clientconsumer arm64 ESD builds with Home edition
    is there any way to get the same clientconsumer arm64 builds for the base 22621.1 build?
     
  8. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    14,365
    73,919
    340
    No
    Code:
    WSUS releases:
    
    1803+1809 : only clientconsumer arm64
    1903+1909 : both
    2004+later: only clientbusiness arm64
    
    19042.631 accidentally got both