Windows Editions Reconstruction Project

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

  1. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,340
    9,711
    240
    #5661 xinso, Nov 25, 2021
    Last edited: Nov 25, 2021
    Windows package installation, Neutral package ahead of Language pack, always.
     
  2. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    5,881
    12,534
    180
    Use the updated 1,2,3 XML to create the image, tested the SFC and DISM /ScanHealth with or without updates it works.
     
  3. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,340
    9,711
    240
    It can be 19041 and 19042. Then you disable Windows Update?
     
  4. acer-5100

    acer-5100 MDL Senior Member

    Dec 8, 2018
    489
    342
    10
    #5665 acer-5100, Nov 25, 2021
    Last edited: Nov 25, 2021
    I have also a 19043.868 but given it's mostly esthetics i don't care (I can go back and forth installing/removing the enablement packages, because the base is Enterprise not Enterprise S)

    Yes I usually update any of my installs to march 2020, then I disable WU.
    Hence my question is "academical" about installing an LCU on an unsupported release, (or improving the xml method to work on updated wims)
     
  5. Nack11

    Nack11 MDL Novice

    Oct 30, 2021
    5
    0
    0
    They add recreation for windows 8.1 pro for education SKU
     
  6. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,340
    9,711
    240
    #5667 xinso, Nov 25, 2021
    Last edited: Nov 25, 2021
    I see. But it needs Custom Update. And I'm retired from such things lately. Sorry.
     
  7. acer-5100

    acer-5100 MDL Senior Member

    Dec 8, 2018
    489
    342
    10

    Thanks
     
  8. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,340
    9,711
    240
    #5669 xinso, Nov 25, 2021
    Last edited: Nov 26, 2021
    Yeah, 19043 too.
     
  9. adric

    adric MDL Addicted

    Jul 30, 2009
    936
    701
    30
    It seems there are different options as to what XML files need updating. Can you post the 1,2,3 XML files that you applied to get your clean image?

    I'd like to give it a try, but never messed with this stuff before..
     
  10. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,340
    9,711
    240
    #5671 xinso, Nov 26, 2021
    Last edited: Nov 26, 2021
    I see you post rarely seen SKUs, but the OP owner is not here to help.
     
  11. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,340
    9,711
    240
  12. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    5,881
    12,534
    180
    After each DISM operation I did checked for SFC /SCANNOW and DISM /CLEANUP-Image /SCANHEALTH, it comes clean and also did the test after updates integration too there are no errors.

    Change the Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.cab to the one present in the archive.

    1.xml

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <servicing>
            <package action="install">
                <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
                <source location="Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.cab" />
            </package>
            <package action="remove">
                <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
            </package>
        </servicing>
    </unattend>
    
    2.xml

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <servicing>
            <package action="remove">
                <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
            </package>
        </servicing>
    </unattend>
    
    3.xml

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <servicing>
            <package action="stage">
                <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.21" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
            </package>
            <package action="install">
                <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
            <source location="1\Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.mum" />
            </package>
        </servicing>
    </unattend>
    
     
  13. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,340
    9,711
    240
  14. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,340
    9,711
    240
    #5676 xinso, Nov 26, 2021
    Last edited: Nov 26, 2021
    Maybe different Architectures.

    Yeah, you are right, it is Dism build.
     
  15. j0912hq7

    j0912hq7 MDL Novice

    Jul 10, 2021
    5
    2
    0
    #5677 j0912hq7, Nov 26, 2021
    Last edited: Nov 26, 2021
    Dear teacher, I rebuilt 20348.1 according to the method you gave. I found that after removing serverdatacenter edition and adding professional edition, there would be an error in adding the language package 20279.1. Later, I changed the language package mum to 20348.1 and some internal positions of mum to 20348. There are still problems and errors in adding. I hope the you can give me some guidance.

    There is no problem rebuilding the version. There is an error adding the language pack.After the version was rebuilt, I saw that the image seemed to be a professional version without language pack。

    F:\work>DISM\dism.exe /image:mount /add-package /packagepath:lp\Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~zh-CN~10.0.20279.1.mum

    部署映像服务和管理工具
    版本: 10.0.20348.1

    映像版本: 10.0.20348.1

    Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~zh-CN~10.0.20279.1
    [==========================100.0%==========================]

    错误: 0x800f081e

    The specified package is not applicable to this image.
     
  16. xinso

    xinso MDL Guru

    Mar 5, 2009
    7,340
    9,711
    240
    #5678 xinso, Nov 26, 2021
    Last edited: Nov 26, 2021
    1.
    To my best knowledge, 20279.1 and 20348.1 are in same package structure. You have to be more cautious, because a bit wrong, all go wrong.

    e.g.

    20279.1 --> 20348.11
    20279.1 --> 20248.1

    2.
    Test individual package with log. And trouble-shoot with the log. Guessing is useless.

    I had elaborated workarouds about package porting. And I don't post twice. Sorry. Please wait for someone who is good at it.
     
  17. j0912hq7

    j0912hq7 MDL Novice

    Jul 10, 2021
    5
    2
    0
    非常感谢您的回答。我会再尝试。谢谢!
     
  18. huynhlam2

    huynhlam2 MDL Junior Member

    Nov 8, 2020
    59
    119
    0