[GUIDE] [DISCUSSION] Windows Editions Reconstructions

Q1: How does Windows detect and install LTSC FoDs for LTSC?

 

Rebuilding WinPE 28000.1 to WinPE 28000.1340
then rebuilding WinPE 28000.1340 to Windows Pro 28000.1340

Code:

Deployment Image Servicing and Management tool
Version: 10.0.26501.1000

Image Version: 10.0.28000.1340

Removing package Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.28000.1340
[==========================100.0%==========================]
The operation completed successfully.

 

For those new to rebuilding, you need a "sources sxs" folder. Without this folder, you are dependent on us; we cannot share our sources 24/7, so you must create it yourself.

To create an SXS source, go to uupdump and create your OS version using the four possible client OSs: Core, Coren, Pro, and Pron without update. Once the ISO is created by uupdump, open the ISO with 7-Zip and open install.wim in the source folder. Extract the following folders into your SXS source folder:
Windows\WinSxS\Manifests\

Windows\servicing\Packages\

Windows\WinSxS\
Note: This folder includes the folders Backup, FileMaps, Fusion, FusionDiff, InstallTemp, and Manifests, which you should not extract.

Next, we extract the language packs, FODs, additional versions, and other files into the source SXS folder.

For versions with updates, we use the same principle: uupdump your version with the updates and extract the folders to the SXS.

 

Knowing is one thing, doing is better.

 

Could this be done by a script ?

 

You need to login to view this posts content.

 

There's no code. The best way is manual; like anything else, you get your hands dirty. The code comes later.

With all the updates for Lab 24h2 client server validation and WinPE, we exceed 16GB of up-to-date SXS source code. Therefore, we only share scripts without SXS source code.

And personally, 24h2 or 25h2 is a bloated system; the update package is twice the size of the OS.

 

Q: What's the difference between ServerStandardNano and ServerDatacenterNano?

 

ServerDatacenterNano additional network services

 

trying 22621 with winpe as winosr25 suggested

error when adding languagepack

Spoiler: 22621 winosr25 winpe

C:\Users\LocalAdmin\Downloads\22621>dism /logpath:logs\1.log /scratchdir:"C:\Users\LocalAdmin\Downloads\22621\temp" /image:mount /apply-unattend:1.xml || exit /b 1

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22621.1

Removing package Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.22621.1
Removing package Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.22621.1
[==========================100.0%==========================]

The operation completed successfully.

C:\Users\LocalAdmin\Downloads\22621>dism /logpath:logs\2.log /scratchdir:"C:\Users\LocalAdmin\Downloads\22621\temp" /image:mount /add-package /packagepath:lp\Microsoft-Windows-Client-LanguagePack-Package_pl-pl-amd64-pl-pl.esd || exit /b 1

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22621.1

Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~pl-PL~10.0.22621.1
[==========================100.0%==========================]
An error occurred - Microsoft-Windows-Client-LanguagePack-Package Error: 0x800700a1

Error: 161

Określona ścieżka jest nieprawidłowa.

 

The specified path is invalid. (So Google told me.)

 

error shows up at 90%

 

Does this applies for LCU too? or something is different?

 

I usually compare initial mum (e.g. 22621.1) and modify it with CU build.

 

no

just trying to reconstruct

 

Yes

 

You also need to retrieve your MSU file and extract it to your SXS source folder using `repack msu`. Your KB file will become an ESD file, not an MSU file. Extract your ESD file into the SXS folder. You're probably missing about ten files, hence the error.

 

trying to make 22621.1 without updates

 

the language pack with ESD or SXS source

 

The language pack with ESD or source SXS is better; with the SXS pack, all the files are up-to-date and it avoids duplicates in the SXS folder. This is also the principle of rebuilding: avoid having an SXS file that exceeds 7 GB.