[ARCHIVED] Windows Editions Reconstruction Project

What? I don't understand.

The Pro of Pro to LTSC reconstruction?

 

right

 

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.mum" />
        </package>
        <package action="remove">
            <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
        </package>
    </servicing>
</unattend>

Code:

dism /english /scratchdir:temp /image:%MT% /apply-unattend:files\sxs\1.xml

For the path in 1.xml, I have to put it in the same folder of sxs which has LTSC packages.

 

So how to install it?

 

The 1.xml will install LTSC and then remove Pro automatically. i.e. one xml for two jobs.

 

why cann't i use dism /image:\mount /remove-package /packagename:
Microsoft-Windows-ProfessionalEdition~xxxxxx
it refuses to do it

 

Please do as huynhlam2's instructions.

 

@xinso
Okay THE trick was to reinject LP (EN-US or localized one) before trying to apply any updates (SSU/enablement package/CU)

 

No. It is the tiny baseless LCU in proper dosage. Remember to thank huynhlam2.

Congrats.

 

Weird. My 19044.1149 LTSC, with 2018 License Agreememt.

It seems to be setting something up and reboot during OOBE. Then it shows 2021 License Agreement. But still 19044.1149 upon login in.

 

You need to login to view this posts content.

 

- Hi Xinso! I want to say thank you! For all your work, that's help me and others for sure. Especially for 19044 EnterpriseS work with WU, No One shared or told about it. Only you have shared "the keys" for it works (use the source as 17763 and more things). Without your share, it can't be done!
- Thank to Zhanglin! For the way make it easy for update:

 

19044 Windows 10 LTSC N x86 Reconstruction Test

[EnterpriseSN]

Code:

Converting 19041.1 Windows 10 Professional to EnterpriseSN x86 en-US

Mounting install image

Creating EnterpriseSN

Adding en-US language pack

Removing Store

Adding SSU

Adding 21H2Enablement

Adding LCU

Mounting winre image

Adding SSU

Adding 21H2Enablement

Adding LCU

Resetting winre base

Unmounting winre image

Current Edition : EnterpriseSN (Volume)

Resetting install base

Unmounting install image

19044.1288 Windows 10 Enterprise N LTSC x86 en-US has been successfully created

Press any key to continue . . .

 

You need to login to view this posts content.

 

Q: Any 19044.xxxx AC SKU to 19044.xxxx Enterprise LTSC. And Vice Versa. Possible?

Long in short, from any SKU to any other SKU.

This is another way of Reconstruction, and, In-Place Swttch, 2in1.

Done by LCU.

e.g. How to convert my running 19044 Pro to LTSC?

 

You need to login to view this posts content.

 

@xinso when converting server2022 to pro ,there are two problems:
1: the logo and edition name won't show in winver.
2: oobe needs to use a strong password.
How can I solve these problems?

 

You need to login to view this posts content.

 

Hello @xinso my old friend

I have a challenge for you, create a Windows IoT Enterprise LTSC for French on ARM64,
If you have a create for create my own homebrew i'm so interested,

Thanks in advance,
Regards

 

The offer I provided last night had expired. Sorry.