I did not know "Manifests, mums and catalogs cannot be recreated using deltas". So deltas are not miracle for future. I was thinking also they can be created. I can also solve hash problem with editing manifests and write which hash/file i want to be in there. Now i realized that if update try to make delta from my changed file it can give an error because the hash of base file and expected hash inside update msu will not be same!! Need to check and prove. Maybe updates creates deltas just in time from current files or expects certain hashes in a list? Just i remembered again. I change at least tree files from enterprises winsxs folder because it complains hash mismatch inspite of it is original iso. This happens when the original iso is MSDN iso. UUPDUMP isos does not have such problems. I guess hash mismatch because of microsoft changes some files or applies deltas or writes signitures to files when creating MSDN isos. But does not change manifest hashes maybe. This means manifests hashes and file hashes inside winsxs folder does not matches each others all time at MSDN isos. Anyway inspite of i change files from winsxs folder my all isos was updateable. If there was such winsxs file hash check update should can find it. As soon as it works i do not care.
Whether to use other manifests or mums depends on the build you are doing. example: 14393.0 Starter uses packages from 15063.0 which as such is quite obvious that other files will be used combined with 14393.0, which may not be able to be updated via windows update only CU offline. but creating builds using the same files and same version will not be a problem. (in my opinion)
where is xinso i missing him, do any of you if he is part of any forum ? , this was place for me to see interesting stuff, now i have feel of downfall since new thread
xinso is still on this forum, although with little activity, I don't know if it's from another forum.
as i wrote earlier, i manage to install system successfully, but with "previous version of setup". when choosing default version of setup, there is error "windows 11 installation has failed" (about 76% image extracting)
You can capture like this https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-31#post-1856840
Oh I understand, compare files and do it manually. Although I was hoping to find some tool that compresses these packages to esd.
The install.wim must be in the same folder where the script is, example: BuildEdi.cmd cleanup.cmd install.wim
Hi, I will try it if I have free time again. I've really liked this for a long time. we have and use the same tools. Use WinSxSv1 to capture the real package, and then use PureSXS to capture the essence of EnterpriseS/G. But for 26100.1, we have to dig deeper by opening up Microsoft-Windows-EnterpriseSEdition mum. It have wow64 package which we have to capture too. It will be perfect now. ;o))