I was hoping not to have to use enterpriseS.xml as starter.xml I was looking to try to make the image in the official style, but well if this makes it work I'll take it into account and thanks for always being here to correct me friend I'm not a great expert in this reconstruction but I'm going little by little.
You must first use the guide, this way you can achieve success guide by ace2: https://forums.mydigitallife.net/th...struction-project.80939/page-296#post-1713040
stuck with part1 6. capture starter package with sxs image path set to mount\windows (19041 core) in sxsexport - image has to be 15063 core?
15063 core? I don't understand what you're saying. you need the starter packages 15063.0 these are uploaded in the whatever127 archive of this thread in the index post #2 you don't need a 15063 iso image you just need the packages and follow the structure of the instructions to capture edition specific starter modified for 19041.1
requires repacking the updates, basically modifying some things to add cumulative updates (CU) Check this out to see what I mean: https://forums.mydigitallife.net/th...nstruction-project.80939/page-51#post-1630053
Spoiler: HashMyFiles Code: ================================================== Filename : sxs.7z MD5 : 3528bfb774fcd5e0328f45bf72879a26 SHA1 : f92d2fe91a5c7b89c86b27ab3b8f37d633fe4365 CRC32 : 3a2f658a SHA-256 : 183f5f62f548f2a1762927540348096c1e7447ab4f1fd9b0a7f3162026cbb980 SHA-512 : 9169b94c461b9bc420ed9e289a46c63985016108ca4d3df0e91502df0cf2421dce56bea9659f9dafa223cab0c1e3a8f257b1fc96f507e62ff8ea13baa7a5add6 SHA-384 : 8aac3e85d2df13c9e6b8aae82ee625f110d5b883bff8f285984e203ac0b39e2c93d3639cc0d9d64961e1969e61075975 Full Path : C:\Users\User\Desktop\sxs.7z Modified Time : 19/09/2024 15:26:54 Created Time : 19/09/2024 15:26:53 Entry Modified Time: 19/09/2024 15:26:54 File Size : 160,451 File Version : Product Version : Identical : Extension : 7z File Attributes : A ==================================================
Just out of curiosity, why do these lines have to be removed? Do they affect 14393.0 in any way? Or do these lines not exist in 14393.0? Sorry for my doubts, but since in x64 it was not necessary to remove these lines, I am surprised that in x86 it does have to be done.
Stop errors when applying Starter.xml, because these line don't exist in Core.xml or Professional.xml or EnterpriseS.xml 14393.0 x86 or x64.
Have rebuilt 26100.1 Core to Starter, - added Starter and Staged (not Removed) Core. Used the 26100 Edition package as source.
Can somebody explain me why everybody try to build starter edition? I understand that you want to upgrade to any edition. Probably desire to use one install.wim and upgrade to any edition. But there is two kinds of upgrade. One is upgrade with just entering a key. Other one is upgrade with upgrade iso with formating all partitions. Do you have an edition that can upgrade with just entering a key to any edition? Your upgrading means that or not? I also build such an install.wim but there is a problem that all editions have same packages. Normaly for example home n should not have media player but also in same install wim pro edition should have all packages. My all editions have all packages because they have to be. Changing licensing does not change what the features operating system has. Does your same install.wim just have starter packages and after upgrade your same install.wim make upgrade contained packages and adds more packages and features to edition? Until now from shared packages i guess it is not because shared packages only contains licensing files. If same install. wim gives same packages for all editions it is again stupid to use starter edition. I want to to hear answer of why need to build starter edition. I know that you want it because Microsoft is making that in that way. Probably Microsofts way and your way does not close each others in aim. You are just trying to copy it. I have not investigated a real starter edition yet. Downloaded one and not sure is it real or not. After investigation it will be more clear for me. Also i am curious if the update packages contains starter edition? If they dont because Microsoft never released starter edition your all aims again useless. I have seen some users grab starter packages from updates. If updates contains starter edition packages maybe it can be a little understandable that reconstructed wim can be updateable in the future.
The idea of building the Starter edition was mine, just the fact of recovering the missing packages from 15063.0, which Ace2 helped to build Windows 11 Starter (22000.1) and other builds is something different. I only wanted to create the x86/x64 starter edition, until now it was only possible on x64 because the x86 starter packages (15063.0) were missing until now. I will not publish other starter builds because I already fulfilled my goal of getting the missing packages from x86/x64 starter 15063.0. I will upload the x86 packages in the index soon.. (it weighs 399 MB it will take me a while) Here everyone is free to do any kind of rebuild.