Windows Editions Reconstruction Project

Done.

 

It tells that it is EnterprseG, isn't it?

We don't need following CMGE systems, but we'd want its CMGE Group policy and Telemetry Group policy.

Code:

\Program Files\
CMITActivation
CMITControlCenter
CMITOfflineUpdateInstaller
CmitUpdateAgent

 

Of course but in the en-US.

I need to translate the zh-CN to en-US first one to play with step 2.
Is'nt right?

 

EnterpriseG is almost like Pro -- but without Onedrive, Windows Defender, Edge -- less Telemetry
CMGE removed more bloat and telemetry

 

You need to login to view this posts content.

 

Nothing but language changed, IMHO.

 

Agreed.Once it's done we can make a de-microsofted windows.

 

install.wim\Windows\Temp, Panther, Setup, Wallpapers, and some files in System App related folders are all about OEM CMGE.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

There are CompositionEditionID and EditionID in registry.

e.g. In EnterpriseSEdition image, CompositionEditionID is Parent Edition, i.e. EnterpriseS. And EditionID can be Parent or Virtual Edition. i.e. either EnterpriseS or IoTEnterpriseS, depending on the key being used.

Q: What is the target of LCU?
A: Parent Editon. i.e. EnterpriseSEdition.

Q: What s the target of Windows Update?
A: EditionID.

 

Test 19044.1503 Windows 10 IoT Enterprise LTSC amd64 fi-FI Reconstruction

Code:

WIM Information:
---------------------
GUID:{AA2064FE-9928-4AFD-A159-14DC1A983227}
Image Count:1
Compression:LZX
Part Number:1/1
Attributes:0x8
RP_FIX

Image Index: 1
-------------------
Name:Windows 10 IoT Enterprise LTSC 2021
Description:Windows 10 IoT Enterprise LTSC 2021
Flags:IoTEnterpriseS
Files:87609
Folders:26088
Expanded Size:12268 MB


WIM XML Information:
---------------------------
<WIM>
  <IMAGE INDEX="1">
    <DIRCOUNT>26088</DIRCOUNT>
    <FILECOUNT>87609</FILECOUNT>
    <TOTALBYTES>12864728533</TOTALBYTES>
    <HARDLINKBYTES>5622849749</HARDLINKBYTES>
    <CREATIONTIME>
      <HIGHPART>0x01D81CB9</HIGHPART>
      <LOWPART>0x7D17EB9A</LOWPART>
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>
      <HIGHPART>0x01D81CB9</HIGHPART>
      <LOWPART>0x7D17EB9A</LOWPART>
    </LASTMODIFICATIONTIME>
    <WIMBOOT>0</WIMBOOT>
    <WINDOWS>
      <ARCH>9</ARCH>
      <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
      <EDITIONID>IoTEnterpriseS</EDITIONID>
      <INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
      <SERVICINGDATA>
        <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE>
        <GDRDUREVISION>0</GDRDUREVISION>
        <PKEYCONFIGVERSION>10.0.19041.1202;2016-01-01T00:00:00Z</PKEYCONFIGVERSION>
      </SERVICINGDATA>
      <PRODUCTTYPE>WinNT</PRODUCTTYPE>
      <PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
      <LANGUAGES>
        <LANGUAGE>fi-FI</LANGUAGE>
        <FALLBACK LANGUAGE="fi-FI">en-US</FALLBACK>
        <DEFAULT>fi-FI</DEFAULT>
      </LANGUAGES>
      <VERSION>
        <MAJOR>10</MAJOR>
        <MINOR>0</MINOR>
        <BUILD>19044</BUILD>
        <SPBUILD>1503</SPBUILD>
        <SPLEVEL>0</SPLEVEL>
        <BRANCH>vb_release</BRANCH>
      </VERSION>
      <SYSTEMROOT>WINDOWS</SYSTEMROOT>
    </WINDOWS>
    <NAME>Windows 10 IoT Enterprise LTSC 2021</NAME>
    <DESCRIPTION>Windows 10 IoT Enterprise LTSC 2021</DESCRIPTION>
    <FLAGS>IoTEnterpriseS</FLAGS>
    <DISPLAYNAME>Windows 10 IoT Enterprise LTSC</DISPLAYNAME>
    <DISPLAYDESCRIPTION>Windows 10 IoT Enterprise LTSC</DISPLAYDESCRIPTION>
  </IMAGE>
  <TOTALBYTES>3579402246</TOTALBYTES>
</WIM>

Still 10.0.19041.1202;2016-01-01T00:00:00Z.

Q: How to tell the Architecture from WIM Information?
A:

<ARCH>0</ARCH> = x86
<ARCH>9</ARCH> = x64 (amd64)
<ARCH>12</ARCH> = a64 (arm64)

 

Q: What is new Embedded feature(s)?
A:

Code:

<mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" />

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Searching. e.g.
https://forums.mydigitallife.net/th...struction-project.80939/page-319#post-1718849

Or ask
owouwu
Applegame12345
example12345678912345678

Or BetaArchive

 

After System creation, the image still needs Store addition for not-LTSC Editions, then it can be installed through cd\usb boot.

Here comes the question:
To make the image capable of being apppied to a partition and boot to OOBE, does Microsoft have to install\sysprep\capture, or configure registry?

If the answer is the latter, what?

Where? SOFTWARE and SYSTEM?
Which? OOBE and Setup?

I use the 19041.1 SOFTWARE and SYSTEM from regular image, it works 'till 19044.1526. Why?

PS:
The unstaged image has this registry. But it does not have \Windows\Setup folder. And it can be installed normally through cd\usb boot only.

Code:

[State]
ImageState=IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE

The \Windows\Setup folder shows up after sysprep. And it turns to be a regular image. But I don't believe that Microsoft has to install\sysprep\capture.

 

1. When will Microsoft duly approve the new version of CMGE_V2022-L.1345 and establish the official support period? As of today, CMGE_V2022-L.1345 has the status of TBD(i.e. To be decided )
2. If CMGE_V2022-L.1345 is not approved in due course, then it is an insider version, i.e. will the final release be different?
3. How to enable update CMGE_V2022-L.1345
- from the Chinese CMGE (support.cmgos.com) server?
- from Microsoft servers?

 

You need to login to view this posts content.

 

You need to login to view this posts content.