Windows Editions Reconstruction Project

Discussion in 'Windows 10' started by whatever127, Jan 10, 2020.

  1. xinso

    xinso MDL Guru

    Mar 5, 2009
    8,896
    10,568
    270
    #6221 xinso, Jan 15, 2022
    Last edited: Jan 15, 2022
    I tested Abbody's 19041.1 EnterpriseS amd64 with 19041.1149 LCU, failed. 19041.1200 OK. (No worries if It is OK with latest LCUs.)

    19041.1149 Error: 0x800f0984
    Code:
    
    ===============================================================================
    Converting 19041.1 Windows 10 Professional to EnterpriseS amd64 en-US
    ===============================================================================
    
    Mounting Professional image
    
    Creating EnterpriseS
    
    Adding en-US language pack
    
    Adding SSU
    
    Adding 21H2Enablement
    
    Adding LCU
    
    Error: 0x800f0984
    
    DISM failed. No operation was performed.
    For more information, review the log file.
    
    Mounting winre image
    
    19041.1200 OK
    Code:
    
    ===============================================================================
    Converting 19041.1 Windows 10 Professional to EnterpriseS amd64 en-US
    ===============================================================================
    
    Mounting Professional image
    
    Creating EnterpriseS
    
    Adding en-US language pack
    
    Adding SSU
    
    Adding 21H2Enablement
    
    Adding LCU
    
    Mounting winre image
    
    Adding SSU
    
    Adding LCU
    
    Resetting winre base
    
    Unmounting winre image
    
    Optimizing winre image
    
    Current Edition : EnterpriseS (Volume)
    
    Resetting EnterpriseS base
    
    Unmounting EnterpriseS image
    
    Optimizing EnterpriseS image
    
    19044.1200 Windows 10 Enterprise LTSC amd64 en-US has been successfully created on 2022/1/15
    
    Press any key to continue . . .
    
     
  2. xinso

    xinso MDL Guru

    Mar 5, 2009
    8,896
    10,568
    270
  3. xinso

    xinso MDL Guru

    Mar 5, 2009
    8,896
    10,568
    270
    The 14393.0 is official SPP. I hope not.

    01/15/2022
     
  4. xinso

    xinso MDL Guru

    Mar 5, 2009
    8,896
    10,568
    270
    #6226 xinso, Jan 15, 2022
    Last edited: Jan 15, 2022
    OK.
     
  5. Applegame12345

    Applegame12345 MDL Member

    Mar 13, 2016
    163
    127
    10
    Oh. What does the watermark (which is at the bottom right corner) say? "For testing purposes only" or "Evaluation copy"?
     
  6. xinso

    xinso MDL Guru

    Mar 5, 2009
    8,896
    10,568
    270
    #6228 xinso, Jan 15, 2022
    Last edited: Jan 15, 2022
    "Evaluation copy" = Restart every few hours when expired (It is on official 14393.0, so it won't get BSOD.)
     
  7. Applegame12345

    Applegame12345 MDL Member

    Mar 13, 2016
    163
    127
    10
    Mind showing winver?
     
  8. example12345678912345678

    example12345678912345678 MDL Senior Member

    Dec 29, 2019
    338
    101
    10
    #6230 example12345678912345678, Jan 15, 2022
    Last edited: Jan 15, 2022
    "An error occurred while configuring the Windows foundation image."
    This is the error when I try to convert a staged ISO to unstaged.
    Edit: I forgot to add Starter.cat and Starter.mum files. Now trying once more.
     
  9. xinso

    xinso MDL Guru

    Mar 5, 2009
    8,896
    10,568
    270
  10. xinso

    xinso MDL Guru

    Mar 5, 2009
    8,896
    10,568
    270
    Servicing Stack build mismatched.

    What's your target build, 15063? What's the source build?
     
  11. example12345678912345678

    example12345678912345678 MDL Senior Member

    Dec 29, 2019
    338
    101
    10
    #6234 example12345678912345678, Jan 15, 2022
    Last edited: Jan 15, 2022
    Yes. It is. I don't think this is a good idea. That's what I tried to do.
    1. Extract the "Packages" folder from 14357.1000 to drive root.
    2. Create the folders "Users" and "Windows"
    3. Add needed files from staged 15063.0 ISO.
    4. Replace all "14357.1000" mentions with "15063.0" via any third party software. This includes the filenames.
    5. Extract the full .cab files (cab+psf merged) and overwrite if asks.
    6. Add license.rtf files to system32 folder.
    7. DISM /capture-image and give these properties. Name: "Windows Longhorn Client", Description: "Windows Longhorn Client (15063.0.amd64fre.rs2_release.170317-1834) EDITIONS:<any edition name goes here, separate the SKU names via comma.>" Flag: "Windows Foundation"
    8. Edit the ISO; Add lp.cab file for any language to this folder: <ISO root>\langpacks\xx-XX\lp.cab and replace the install.wim file. Save the ISO and test.
    That was just mixing files from 14357.1000. And I don't know why, but I expected it to work. Obviously it didn't work.
     
  12. xinso

    xinso MDL Guru

    Mar 5, 2009
    8,896
    10,568
    270
    14357 is same as 14393. Why you use 15063 (although compatible).
     
  13. example12345678912345678

    example12345678912345678 MDL Senior Member

    Dec 29, 2019
    338
    101
    10
    I thought I need the full .cab files, since 14393's cab+psf files can not be found on UUP Dump. 15063 is the earliest available build that you can find the cab+psf files.
     
  14. Applegame12345

    Applegame12345 MDL Member

    Mar 13, 2016
    163
    127
    10
    I essentially recreated the entire unstaged wim layout for 10537 by using 10586.1000 Server arm64 and 14357.1000 amd64 as reference.
     
  15. xinso

    xinso MDL Guru

    Mar 5, 2009
    8,896
    10,568
    270
    #6240 xinso, Jan 15, 2022
    Last edited: Jan 15, 2022
    They don't have cab+psf. You must have meant UUP packages.

    Available cab+psf:
    17763
    19041
    20348

    Good night.