Using svf patch or esd for example i make image install.esd file from build 16288.2 and export install.wim to this file, only 400mb is non-different, is the same data,but the rest 800mb is different what the reason for this ? is ms using each time another encrypting compiler, or the optimization compiler make the dll and exe different each time thx, also for any suggestions btw i did a test with 32bit and 64bit same build and there big different
What image install.esd do you make and what install.wim do you export to it? What 400MB and 800MB are you talking about? Rest i can't make chocolate of.
I got install.esd modified and lited from build 16288.2 its around 1.2gb when i export a similar lited version of build 16299.15 to 16288.2 bulid install.esd image its going from 1.2gb to 2+gb btw when convert the install.wim of 16299 build to esd alone its 1.2gb but that given cos reason i mention that's why 400mb is same code for both builds and 800mb are always different i duno how code works but is it logical to assume those builds are mostly the same? code wise so its should be around 100-150mb different
The chopping probably causes files not being the same anymore and getting each a different hash and if that happens, it will increase the overall size of the install.wim/esd.
but its solid/esd compressing, the file name or hash wont matter to process its taking the files and cut them to chunks and then hash them and look for match ? if ms can find a solution for this, can save a lot of traffic for them they can bring same kind of baseline.esd and push new builds with just a differ esds and also big companies will enjoy this did a test with wim esd to install.wim and then export to it it expend from 1.6 to 3gb
MSFT find a solution for what? You chopped your wims, not MSFT. For example, this is the size of my 16299.15 AIO x64 nl-NL iso (it contains 26 indices/sku's). Nothing chopped, only pre-enabled dotnetfx3, integrated msie, MRP and ms dart 10: 3.34 GB (3,597,369,344 bytes)
Try do esd with both 32. 64 U will see big different , where its supported to be mosty the same files In the last builds the changes is like 16299.x For that matter where the update is quiet small each builds have big differents
It would be more understandable if you do not summarize each sentence you write are you creating svf patch from esd to esd or what?
ESD files usually do not work well with svf patches, because they are solid compressed did you try svf between install.wim?
The svf between my multi-architecture iso (2 separate install.esd) and the separate x86 or x64 one = 39.5 KB (40,472 bytes)