[GUIDE] [DISCUSSION] Windows Editions Reconstructions

Different CU updates between 17763.5820 x86 EnterpriseS and EnterpriseSN:

[EnterpriseS]

Code:

Language-B802101B313385C8B8BBEA078A0E29F6405F25519D34136AF51483CEEDD1F6FB~31bf3856ad364e35~x86~en-US~10.0.17763.5820.mum
Language-E20AD3833D0607FB07E08D51D56182ED01BD2AA1E8884CBEDBBFBC9B5B1F5CD2~31bf3856ad364e35~x86~en-US~10.0.17763.5820.mum
Package-6FA354FD5000155DB0361C49B7FA4EBF88F769900041B8BDA2812721E0A6221C~31bf3856ad364e35~x86~~10.0.17763.5820.mum
Package-CEEAFB5916262D93B34FC85B53E388272275587E598B37D80C5755BB399D29E5~31bf3856ad364e35~x86~~10.0.17763.5820.mum
Shared-EE163410907790B351CDA9511A1633155E0EBF38C6412ECB4560314601E1048D~31bf3856ad364e35~x86~~10.0.17763.5820.mum
Wrapper-96A4AA5696B60CD67DBAA00816BA54001EFCAFC04FEE7A7D46F0C53CB717808D~31bf3856ad364e35~x86~~10.0.17763.5820.mum
Wrapper-A5319A2561D8A09F16F94A87190032BE94322EEBB1D230D3186AAEB9899528FE~31bf3856ad364e35~x86~~10.0.17763.5695.mum

Wrapper-C22E75D95C3FF5FF39AABBE435A8D47BCE133F590AC57DEFB04A0DCBBFF7742B~31bf3856ad364e35~x86~~10.0.17763.5820.mum

[EnterpriseSN]

Code:

Language-EE5D5C922BC36E3DDDB6F509265FFC0600F687746034B3DEDC6DBE2526946216~31bf3856ad364e35~x86~en-US~10.0.17763.5820.mum
Shared-8C6B0C742093A96B188B391673540AA5CFD3D82175A5A12E0690FB299223C0CE~31bf3856ad364e35~x86~~10.0.17763.5820.mum
Wrapper-F1247F16C85CDE01AB9DD72F41D640A0DBDBDA4ACC6A4483EDA549AC3C43D529~31bf3856ad364e35~x86~~10.0.17763.5695.mum

Wrapper-B0BE3D41AF9D27C032C3DC5898A37CD053F6934DAC30F187D9CBB84F6BA39E00~31bf3856ad364e35~x86~~10.0.17763.5820.mum

 

Try baseless CU.

 

[Feedback]
It works. Thanks.

 

On both official and reconstructed images, the latest CU, e.g. 26100.3746, the "zh-TW" language shows wrong display for "Windows Admin Center Setup" and "Network ATC" features.

Q: What about you, 26100.3321?
A: Me too.

 

You need to login to view this posts content.

 

@gailium119, I wonder if conflicts could not be detected at design time.
Are you editing manually each servicing files like manifest?
It is perhaps possible to create a tool for create, edit and check servicing artefacts.
Any ideas/comments about this?

 

is there a method to create 25398 EnterpriseG?
also for updating 19041 EnterpriseG should convert the 19041.1 pro ISO to EnterpriseG then integrate updates or update the 19041.1 pro ISO to 19045.5608 and then convert to EnterpriseG?

 

afaik bedi tool can do that.
and yes - you should convert 19041.1 pro to entg first, then integrate updates

 

the link for bedi tool is removed so was wondering if there was another method
also when I integrated the updates (19045.5608) and then tried installing it gave a "licenses not found" error and I had to manually flash the install.wim file, it worked fine when I used the converted ISO before updating (19041.1)

 

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.

 

Detecting the manifest is feasible, but implementing it is a hard work.

 

You need to login to view this posts content.

 

https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-69#post-1868095

 

for EnterpriseG should I download the EnterpriseG package instead of the Professional package? never mind

 

unpack to root of partition!

 

Still getting same error.
To be extra sure, I even created a seperate partition exclusively for the script and copied the files there, however it still gives the same error

 

Install.wim should be ONLY one index and that only one index should be professional edition. (Delete if it has home edition index 1) Also it should be xxxxx.1 version

It can be different edition/version install.wim.

It can be install.esd renamed to install.wim. (It should not be)

 

Textaar
Try to edit Bedi.cmd, insert this command at line 3
pushd "%~dp0"

so it would look likes:

Code:

@MODE CON:cols=110 lines=33
@Echo Off
pushd "%~dp0"
set "_iw=install.wim"
if not exist %_iw% (call :_Warn "There is no %_iw% in the directory")
...
...