[ARCHIVED] Windows Editions Reconstruction Project

Test 19044.4291 Windows 10 Enterprise N LTSC arm64 en-US

Code:

WIM XML Information:
---------------------------
<WIM>
  <TOTALBYTES>4164296713</TOTALBYTES>
  <IMAGE INDEX="1">
    <DIRCOUNT>29224</DIRCOUNT>
    <FILECOUNT>92542</FILECOUNT>
    <TOTALBYTES>14357143839</TOTALBYTES>
    <HARDLINKBYTES>6086696327</HARDLINKBYTES>
    <CREATIONTIME>
      <HIGHPART>0x01DA8F1D</HIGHPART>
      <LOWPART>0xBC62B750</LOWPART>
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>
      <HIGHPART>0x01DA8F1D</HIGHPART>
      <LOWPART>0xD4EA04CE</LOWPART>
    </LASTMODIFICATIONTIME>
    <WIMBOOT>0</WIMBOOT>
    <WINDOWS>
      <ARCH>12</ARCH>
      <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
      <EDITIONID>EnterpriseSN</EDITIONID>
      <INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
      <SERVICINGDATA>
        <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE>
        <GDRDUREVISION>0</GDRDUREVISION>
        <PKEYCONFIGVERSION>10.0.19041.4170;2016-01-01T00:00:00Z</PKEYCONFIGVERSION>
      </SERVICINGDATA>
      <PRODUCTTYPE>WinNT</PRODUCTTYPE>
      <PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
      <LANGUAGES>
        <LANGUAGE>en-US</LANGUAGE>
        <DEFAULT>en-US</DEFAULT>
      </LANGUAGES>
      <VERSION>
        <MAJOR>10</MAJOR>
        <MINOR>0</MINOR>
        <BUILD>19044</BUILD>
        <SPBUILD>4291</SPBUILD>
        <SPLEVEL>0</SPLEVEL>
        <BRANCH>vb_release</BRANCH>
      </VERSION>
      <SYSTEMROOT>WINDOWS</SYSTEMROOT>
    </WINDOWS>
    <NAME>Windows 10 Enterprise N LTSC 2021</NAME>
    <DESCRIPTION>Windows 10 Enterprise N LTSC 2021</DESCRIPTION>
    <FLAGS>EnterpriseSN</FLAGS>
    <DISPLAYNAME>Windows 10 Enterprise N LTSC</DISPLAYNAME>
    <DISPLAYDESCRIPTION>19044.4291 Windows 10 Enterprise N LTSC</DISPLAYDESCRIPTION>
  </IMAGE>
</WIM>

 

@xinso Do the settings open when you have Turkish or another language in version 25398.830?

 

https://forums.mydigitallife.net/th...struction-project.80939/page-769#post-1831678

The settings needs any updated build of this language pack. e.g.
Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~tr-TR~10.0.25398.709.mum
Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~tr-TR~10.0.25398.763.mum

Wait for zwl29107's 830 CU.

Two common issues for CU on 25398 Client:
2-1. Settings (lacking aforementioned language pack)
2-2. WinX menu (lacking WinX item in product policy)

[Workaround for WinX menu]
Repack Microsoft-Windows-EnterpriseS-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.25398.1.mum with 26100.1 LTSC licenses.
You may need gailium119 or zwl29107's help.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Versions 22000 and 22621 are already working without any problems. I only asked you for version 25398. I thought it was a simple question, but you find it appropriate to answer this way, it's very strange.

I am creating ltsc in version 25398.1, my only problem is that the settings cannot be opened, I just wanted you to guide me on this issue, you are the one who is making things worse.

 

You keep saying OP, how do you expect me to do these things on a subject where no detailed information is given? That's a separate problem.

 

You need to login to view this posts content.

 

Microsoft does not post Baseless CU for the latest builds.

Times changed... Windows changed...

 

@zwl29107 Last time I applied the method you mentioned, that is, I installed a modded .830 cu on your .763 cu file, this time it gave an error while on the installation screen, should I send a screenshot?

 

What is the error?

 

It gives the error in the attached picture

 

Do you have any idea why it gives this error, what could be the solution?
@zwl29107

 

Install .830 CU after OOBE.

 

Can you briefly explain how to do this?

 

I'm a bit idiot in these matters, I'm sorry, that's why I'm asking

 

please look attached dism++ log given this error.