[ARCHIVED] Windows Editions Reconstruction Project

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

Tags:
Thread Status:
Not open for further replies.
Page 279 of 898
  1. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    #5561 Ace2, Nov 20, 2021
    Updated to EnterpriseS 10.0.19044.1288 - All credit to huynhlam2, great work on "The Completely EnterpriseS 19041.1_Package" well done.:cool:
    Code:
    Microsoft Windows [Version 10.0.19041.1]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>dism /image:C:\work\mount /add-package /packagepath:C:\SSU-19041.1220-x64_046f0825.cab

Deployment Image Servicing and Management tool
Version: 10.0.19041.1

Image Version: 10.0.19041.1

Processing 1 of 1 - Adding package Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1220.1.0
[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>dism /image:C:\work\mount /add-package /packagepath:C:\Windows10.0-KB5006670-x64_1b240952.cab

Deployment Image Servicing and Management tool
Version: 10.0.19041.1

Image Version: 10.0.19041.1

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1288.1.7
[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>dism /image:C:\work\mount /add-package /packagepath:C:\Windows10.0-KB5003791-x64_73ea2c98.cab

Deployment Image Servicing and Management tool
Version: 10.0.19041.1

Image Version: 10.0.19041.1288

Processing 1 of 1 - Adding package Package_for_KB5003791~31bf3856ad364e35~amd64~~19041.1237.1.3
[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>dism /image:C:\work\mount /get-currentedition

Deployment Image Servicing and Management tool
Version: 10.0.19041.1

Image Version: 10.0.19044.1288

Current edition is:

Current Edition : EnterpriseS

The operation completed successfully..
     
  2. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    #5562 kibkalo, Nov 20, 2021
    Can you plz elaborate?
    I made LTSC arm64. PSFX updates apply fine, standard are failing after the first one.
     
  3. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #5563 xinso, Nov 20, 2021
    Last edited: Nov 20, 2021
    They are different, aren't they?

    19041.1288

    Pro
    Microsoft-Windows-Shell32-OEMDefaultAssociations-Package~31bf3856ad364e35~amd64~~10.0.19041.964
    oemdefaultassociations.dll 23 KB
    oemdefaultassociations.xml 21 KB


    LTSC
    Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package~31bf3856ad364e35~amd64~~10.0.19041.1151
    oemdefaultassociations.dll 8 KB
    oemdefaultassociations.xml 6KB
     
  4. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #5564 xinso, Nov 21, 2021
    Reserved
     
  5. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    #5565 kibkalo, Nov 21, 2021
    So I need to replace OEMDefaultAssociations
    But where to get arm64 LTSC file from?
    PSFX 10.0.19041.1151?
     
  6. dummekuehe

    dummekuehe MDL Addicted

    Jan 11, 2009
    506
    114
    30
    #5566 dummekuehe, Nov 21, 2021
    So i tried to do this as well and everything went fine for the first part.
    I set the edition to EnterpriseS, then tried the get-currentedition, and got the same readout as you did
    i didn't do the Cleanup&Save part that is in the readme.txt but instead ran the command to remove the provisioned app packages like you did
    it started like yours did but then i got an error:
    Code:
    Path          : mount
Online        : False
RestartNeeded : False

Path          : mount
Online        : False
RestartNeeded : False

Remove-AppxprovisionedPackage : Removal failed. Please contact your software vendor.
At line:1 char:42
+ ... sionedPackage -Path mount | Remove-AppxprovisionedPackage -Path mount
+                                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     + CategoryInfo             : NotSpecified: (:) [Remove-AppxProvisionedPackage], COMException
     + FullyQualifiedErrorId : Microsoft.Dism.Commands.RemoveAppxProvisionedPackageCommand
    Any Idea what i could've done wrong?
     
  7. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    #5567 Ace2, Nov 21, 2021
    I have no idea, i have never seen this error.:eek:
     
  8. dummekuehe

    dummekuehe MDL Addicted

    Jan 11, 2009
    506
    114
    30
    #5568 dummekuehe, Nov 21, 2021
    If i go to powershell and enter the full mount path i can remove them one by one via their package name
     
  9. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    #5569 Ace2, Nov 21, 2021
    What is the the full mount path ?
     
  10. dummekuehe

    dummekuehe MDL Addicted

    Jan 11, 2009
    506
    114
    30
    #5570 dummekuehe, Nov 21, 2021
    e:\work\mount

    and i'm running all commands from the e:\work folder so the relative path mount should suffice
     
  11. spanishfly

    spanishfly MDL Senior Member

    Dec 5, 2018
    365
    540
    10
    #5571 spanishfly, Nov 21, 2021
    Last edited: Nov 21, 2021
    Thanks for investigating!
    Code:
    Microsoft-OneCore-WindowsIoT-Package

Microsoft-Windows-20H2Enablement-Payload-Package
Microsoft-Windows-UpdateTargeting-ClientOS-EKB-Package
Microsoft-Windows-UpdateTargeting-ClientOS-EKB-Wrapper-Package

Microsoft-Windows-21H1Enablement-Payload-Package
Microsoft-Windows-Product-Data-21h1-EKB-Package
Microsoft-Windows-Product-Data-21h1-EKB-Wrapper-Package
Microsoft-Windows-UpdateTargeting-ClientOS-21h1-EKB-Package
Microsoft-Windows-UpdateTargeting-ClientOS-21h1-EKB-Wrapper-Package

Microsoft-Windows-21H2Enablement-Package
Microsoft-Windows-21H2Enablement-Payload-Package
Microsoft-Windows-Product-Data-21h2-EKB-Package
Microsoft-Windows-Product-Data-21h2-EKB-Wrapper-Package
Microsoft-Windows-UpdateTargeting-ClientOS-21h2-EKB-Package
Microsoft-Windows-UpdateTargeting-ClientOS-21h2-EKB-Wrapper-Package

Microsoft-Windows-Desktop-BCDTemplate-Client-Package

Microsoft-Windows-Embedded-DialogBlocking-Package
Microsoft-Windows-Embedded-DialogBlocking-WOW64-Package
Microsoft-Windows-Embedded-KeyboardFilter-Core-Package
Microsoft-Windows-Embedded-KeyboardFilter-Core-WOW64-Package

Microsoft-Windows-Internet-Browser-Package

Microsoft-Windows-Lxss-WithGraphics-merged-Package

Microsoft-Windows-Printing-PMCPPC-FoD-Package

Microsoft-Windows-Product-Data-EKB-Package
Microsoft-Windows-Product-Data-EKB-Wrapper-Package

Microsoft-Windows-Shell-CustomShellHost-Package


Windows-Defender-AM-Default-Definitions-Package

    The only difference that looks "interesting" is Microsoft-OneCore-WindowsIoT-Package
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    #5572 Ace2, Nov 21, 2021
    Code:
    Try

Powershell -Command "Get-AppXProvisionedPackage -Path e:\work\mount | Remove-AppxProvisionedPackage -Path e:\work\mount"

*

Open Powershell, try this command

Get-AppXProvisionedPackage -Path e:\work\mount | Remove-AppxProvisionedPackage -Path e:\work\mount
     
  13. spanishfly

    spanishfly MDL Senior Member

    Dec 5, 2018
    365
    540
    10
    #5573 spanishfly, Nov 21, 2021
    Probably will need to start over and clean up.
    Then ...
    Try running your command prompt terminal (legacy or PowerShell) and all code as TrustedInstaller
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    #5574 Ace2, Nov 21, 2021
    To keep Windows-Defender-AM-Default-Definitions-Package installed in EnterpriseS 10.0.19041.1 need to fix 1.xml
    Code:
    <?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <servicing>
        <package action="remove">
            <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" 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="Microsoft-Windows-EnterpriseSEdition-Package-amd64-10.0.19041.1.cab" />
        </package>
    </servicing>
</unattend>

TO

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <servicing>
        <package action="stage">
            <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" 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="Microsoft-Windows-EnterpriseSEdition-Package-amd64-10.0.19041.1.cab" />
        </package>
    </servicing>
</unattend>
    Make 4.xml to remove Microsoft-Windows-ProfessionalEdition
    Code:
    <?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <servicing>
        <package action="remove">
            <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
        </package>
    </servicing>
</unattend>
    Use 4.xml at the end of building EnterpriseS 10.0.19041.1
     
  15. dummekuehe

    dummekuehe MDL Addicted

    Jan 11, 2009
    506
    114
    30
    #5575 dummekuehe, Nov 21, 2021
    that's the first thing i tried
    didn't work though

    removed them manually
    it's a bit tedious but whatever ;)
     
  16. dummekuehe

    dummekuehe MDL Addicted

    Jan 11, 2009
    506
    114
    30
    #5576 dummekuehe, Nov 21, 2021
    omg stupid new notepad.
    when i tell a cfg file to "open with" notepad
    it says that that file can't be associated with this file type
    f**king microsoft
     
  17. spanishfly

    spanishfly MDL Senior Member

    Dec 5, 2018
    365
    540
    10
    #5577 spanishfly, Nov 21, 2021
    Last edited: Nov 21, 2021
    Will doing this improve other parts of the build?

    Just to be sure.
    Where would I put 4.xml code exactly?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    #5578 Ace2, Nov 21, 2021
    Code:
    5. Set-Edition:

del mount\windows\*.xml
dism /image:mount /set-edition:EnterpriseS /Channel=Volume
DISM /image:mount /apply-unattend:4.xml
     
  19. spanishfly

    spanishfly MDL Senior Member

    Dec 5, 2018
    365
    540
    10
    #5579 spanishfly, Nov 21, 2021
    Thank you!:cool:
    I'm glad I asked!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  20. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #5580 xinso, Nov 21, 2021
    Last edited: Nov 21, 2021
    Code:
    WIM Information:
---------------------
GUID:{898562A9-E1A9-47C0-98C7-5543E1D9E6BA}
Image Count:1
Compression:LZX
Part Number:1/1
Attributes:0x8
RP_FIX

Image Index: 1
-------------------
Name:Windows 10 Enterprise LTSC 2019
Description:Windows 10 Enterprise LTSC 2019
Flags:EnterpriseS
Files:106187
Folders:25096
Expanded Size:13397 MB


WIM XML Information:
---------------------------
<WIM>
  <TOTALBYTES>3498844979</TOTALBYTES>
  <IMAGE INDEX="1">
    <DIRCOUNT>25096</DIRCOUNT>
    <FILECOUNT>106187</FILECOUNT>
    <TOTALBYTES>14048005556</TOTALBYTES>
    <HARDLINKBYTES>6474564194</HARDLINKBYTES>
    <CREATIONTIME>
      <HIGHPART>0x01D44D10</HIGHPART>
      <LOWPART>0xCA2201AC</LOWPART>
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>
      <HIGHPART>0x01D7DEEC</HIGHPART>
      <LOWPART>0x384EBA85</LOWPART>
    </LASTMODIFICATIONTIME>
    <WIMBOOT>0</WIMBOOT>
    <WINDOWS>
      <ARCH>12</ARCH>
      <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
      <EDITIONID>EnterpriseS</EDITIONID>
      <INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
      <SERVICINGDATA>
        <GDRDUREVISION>0</GDRDUREVISION>
        <PKEYCONFIGVERSION>10.0.17763.719;2016-01-01T00:00:00Z</PKEYCONFIGVERSION>
        <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE>
      </SERVICINGDATA>
      <PRODUCTTYPE>WinNT</PRODUCTTYPE>
      <PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
      <LANGUAGES>
        <LANGUAGE>xx-XX</LANGUAGE>
        <FALLBACK LANGUAGE="xx-XX">en-US</FALLBACK>
        <DEFAULT>xx-XX</DEFAULT>
      </LANGUAGES>
      <VERSION>
        <MAJOR>10</MAJOR>
        <MINOR>0</MINOR>
        <BUILD>17763</BUILD>
        <SPBUILD>737</SPBUILD>
        <SPLEVEL>0</SPLEVEL>
        <BRANCH>rs5_release</BRANCH>
      </VERSION>
      <SYSTEMROOT>WINDOWS</SYSTEMROOT>
    </WINDOWS>
    <NAME>Windows 10 Enterprise LTSC 2019</NAME>
    <DESCRIPTION>Windows 10 Enterprise LTSC 2019</DESCRIPTION>
    <FLAGS>EnterpriseS</FLAGS>
    <DISPLAYNAME>Windows 10 Enterprise LTSC</DISPLAYNAME>
    <DISPLAYDESCRIPTION>Windows 10 Enterprise LTSC</DISPLAYDESCRIPTION>
  </IMAGE>
</WIM>
     
Page 279 of 898