[ARCHIVED] Windows Editions Reconstruction Project

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

Thread Status:
Not open for further replies.
  1. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,863
    1,524
    60
    .NET & Defender updates work, LCU failed.
     
  2. liliactr

    liliactr MDL Addicted

    Sep 3, 2009
    541
    191
    30
    #17282 liliactr, Aug 5, 2024
    Last edited: Aug 5, 2024
    Link removed
     
  3. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,863
    1,524
    60
    No
     
  4. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,699
    14,428
    340
  5. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,863
    1,524
    60
    #17285 Ace2, Aug 5, 2024
    Last edited: Aug 5, 2024
    Working on a version of my own, now i know a little more about desktop package's for Server Cor, thanks to winosr25 script & .mum
     
  6. kingsman2007

    kingsman2007 MDL Novice

    Mar 20, 2024
    7
    5
    0
    How to extract them in iso?
     
  7. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Does that mean, that if I modify the edition MUM, I won't be able to install updates without customizing?
    And if I simly add all the packages from modified MUM to image, leaving edition MUM untouched, - would LCU fail? Or uninstall?
    Speaking of AzureStackHCICor, we need
    Code:
    Microsoft-Win4-Feature.ESD
    Microsoft-Win4-WOW64-Feature.ESD
    Microsoft-Windows-Client-Desktop-Required-Package.ESD
    Microsoft-Windows-Client-Desktop-Required-WOW64-Package.ESD
    Microsoft-Windows-Required-ShellExperiences-Desktop-Package.ESD
    Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package.ESD
    from UUP and
    Code:
    Microsoft-Windows-EditionPack-Server-Package
    Microsoft-Windows-EditionPack-Server-WOW64-Package
    Microsoft-Windows-Server-DesktopUX-Package
    Microsoft-Windows-Server-DesktopUX-WOW64-Package
    Microsoft-Windows-WirelessNetworking-Package
    UserExperience-Desktop-Package
    might be first cut from Full OS via SxSv1, right?
     
  8. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,699
    14,428
    340
    Please ask other members. I have no more energy on repeated things.
     
  9. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,699
    14,428
    340
    #17290 xinso, Aug 5, 2024
    Last edited: Aug 5, 2024
    Ace2 said it worked for him\her.
    https://forums.mydigitallife.net/th...struction-project.80939/page-865#post-1846789
     
  10. liliactr

    liliactr MDL Addicted

    Sep 3, 2009
    541
    191
    30
    #17291 liliactr, Aug 5, 2024
    Last edited: Aug 5, 2024
    Client and server use same update msu?

    If yes updates will not be problem for any mixed edition

    If no server package added to client or client edition package added server will brake updates

    Client to client or server to server package / edition change will not affect updates

    Should be clear now.

    I have checked uupdump

    26100.1150 edition uses same msu Windows11.0-KB5040435-x64.msu. This is good thing that every option possible. But should use only updates when released same time for both client and server maybe. Because some updates released different number and only for server or client sku i think. Online update may not be work maybe! I do not know. Better to keep modifications in same group client to client or server to server
     
  11. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,863
    1,524
    60
    #17292 Ace2, Aug 5, 2024
    Last edited: Aug 5, 2024
    I didn't use most Package kibkalo has listed.

    P.s Testing "online" updates for "Server Azure Stack HCI Cor"
     
  12. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,699
    14,428
    340
    It's nice to hear your speech expressed in a way I can understand.
     
  13. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,699
    14,428
    340
  14. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,863
    1,524
    60
    "online" update "KB5040435" for "Server Azure Stack HCI Cor" Restart required

    Back in a few mins...
     
  15. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Have you manually added packages, or used the MUM provided by winosr25?
    Manually added packages might update normally.
    But if we modded a package, LCU fails
     
  16. winosr25

    winosr25 MDL Member

    May 14, 2024
    106
    51
    10
    Azure Stack HCI

    hello for my script I have an sxs sources folder (more than 10gb) with all the packages available on uup dump 26100.1 even the fod and en-us fr-fr included, I do not use the packages.esd all is in the folder sxs
     
  17. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    You did modify Microsoft-Windows-ServerAzureStackHCICorEdition~31bf3856ad364e35~amd64~~10.0.26100.1.mum - adding packages into it, insted of adding them directly to image with DISM.
    That makes LCU fail. When I added same packages manually (Thanks for the list), update works
     
  18. winosr25

    winosr25 MDL Member

    May 14, 2024
    106
    51
    10
    If you want normal updates, use the standard core versions instead.

    Microsoft-Windows-ServerStandardCorEdition.mum

    <?xml version="1.0" encoding="utf-8" standalone="yes"?>
    <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved.">
    <assemblyIdentity name="Microsoft-Windows-ServerStandardCorEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <package identifier="Windows ServerStandardCor Edition" releaseType="Product">
    <update name="Microsoft-Windows-Foundation-Package">
    <package contained="false" integrate="visible">
    <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-ServerCore-Package">
    <package contained="false" integrate="visible">
    <assemblyIdentity name="Microsoft-Windows-ServerCore-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="BCD-Template-Server-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="BCD-Template-Server-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Win4-Feature">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Win4-Feature" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Win4-WOW64-Feature">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Win4-WOW64-Feature" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-EditionPack-Server-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-EditionPack-Server-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="UserExperience-Desktop-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="UserExperience-Desktop-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Server-DesktopUX-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Server-DesktopUX-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Server-DesktopUX-WOW64-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Server-DesktopUX-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-EditionSpecific-ServerStandardCor-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-EditionSpecific-ServerStandardCor-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Desktop-Required-ClientOnly-SharedWithServer-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Desktop-Required-ClientOnly-SharedWithServer-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Desktop-Required-ClientOnly-SharedWithServer-WOW64-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Desktop-Required-ClientOnly-SharedWithServer-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    </package>
    </assembly>
     
  19. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,863
    1,524
    60
    Failed, because after update, booted to black screen.