x86 ltsc 2038 build - help needed to complete (W10 22H2)

Status
Not open for further replies.
NetworkPro

NetworkPro

New Member
Messages
23
Reaction score
0
Source:
en-us_windows_10_business_editions_version_22h2_updated_july_2024_x86_dvd_d04451d9.iso

Single WIM with edition conversion: theoretically by adding skus files the edition can be converted to all editions dont touch it.

Removing: Everything without breaking the OS and keep Windows Updates working

Target ISO size: 2GB or less

Target installation space: 5GB or less

As you can imagine i've hit every bug trying to reach this goal.

Any help will be highly appreciated.
 
Last edited:
NetworkPro said:
Single WIM with edition conversion: by adding skus files the edition can be converted to all editions
Click to expand...
What does this mean? Are you converting to a different SKU by changing product keys? Or adding new files not original to the image?
 
and what is this "2038 build" business? that smells like an activator to me.
 
TEOTWAWKI happens in 2038. Everyone knows about global warming, but the Earth will run out of 32-bit seconds before then.
 
So we need the CLEAN WIM everything else is up to the user to decide how to proceed from there. I forbid you especially you two adding any sku files. Dont touch the sku.
 
Last edited:
I have seen many projects (or attempts) to build a "lite" image but most of them fail because you're trying to hit arbitrary targets (size of ISO or the Windows install) without asking is your final image really usable?

1. You're using W10 x86, because it's the last 32-bit Windows released. This guarantees you a smaller image, but most users don't want a 32-bit system any more because you have a 4GB limit on memory and file length. I have video files larger than 4 GB!

2 You selected Enterprise N, but removed almost everything from the image. If you want users to change SKU's by using a product key, then it's pointless. Switching to Home or Pro SKU doesn't make a difference, if all the Home or Pro features got removed.

This install probably fails because you removed Client.CBS:
Code: 
                <c>microsoftwindows.client.cbs 'Windows Feature Experience Pack'</c>
 
I didnt intend to remove that because I know it breaks things on this OS build.

x86 because I have 4x bay trail tablets with 32bit UEFI

If its stable it will be useful for others to save time and effort.

I am on this project since months already.
 
Last edited:
It runs well ive tested the machine with windowsxlite micro se 32bit its totally usable the platform is sufficiently stable. The Intel bay trail platform was used by Lenovo, HP, Dell, and others. Because the device is not broken yet, it is still a preferred mobile device by the specific enduser.

Other usecases indeed may be adapting the profile to x64 later because I have a machine for it as well.

And of course the industrials VDI ThinPC POS Embedded Kiosk the profile will be usable if someone needs that.

+ not to forget developers who can still maintain 32bit compatibility to test their stuff on this slimmed OS
 
Last edited:
This Third Attempt xml + the last autounattend, fixes the OOBE setup issue and logs directly into the user.

Now I will try to slim it down further by selecting more stuff with the NTlite and sniffing the large stuff with a wiztree.

Any ideas how to slim it, are very welcome.
 

Attachments

OK suspiciously goal reached too easily thanks your moral support?

in the screenshot I was able to add Keyboard layout after setup was done and after Network was Connected.

View attachment 12404

The Try not to break 1.xml is the Second pass after the Third Attempt.xml which is a first pass.
 

Attachments

Last edited:
Even more suspiciously after WU ran and same KB was insatlled that was already integrated, Kernel Mode Driver Framework wdf*.sys started consuming 12% CPU from DPC latency.

Whaaaattt ??? (confused)
 
Status
Not open for further replies.
Back
Top