Is the German-ISO File from vlsc version above available meanwhile? What is the exact name and hash value? Sorry, I did not mean the ltsc version. I did mean the business edition (Enterprise) from MS Volume Licensing Service Center.
It might list different file dates, but all of the esd-sourced isos will be different in the meta data. All of the hashes will be different.
Somewhere @mkuba50 published info about being able to recreate the same iso (or was it install.wim/esd only) from esd or uup multiple times, i have to search for it.
If you export ESD to WIM on a single core computer using imagex and then replace WIM identifier, then you will get always the same WIM, that can be used as source for svf patches. When using wimlib-imagex it is only needed to replace WIM identifier, but cannot be used as svf patch source.
Ok, so the post i saw from a member about @abbodi1406 his ESD>ISO tool being able to recreate iso's with the exact same sha-1 is not correct?
Ran ESD>ISO v40 twice and this is the result: Code: f70548e0e5812d37b18facf9e530298be2ccd13b *17763.107.101029-1455.RS5_RELEASE_SVC_REFRESH_CLIENTPROFESSIONALVL_VOL_X64FRE_EN-US.ISO f70548e0e5812d37b18facf9e530298be2ccd13b *17763.107.101029-1455.RS5_RELEASE_SVC_REFRESH_CLIENTPROFESSIONALVL_VOL_X64FRE_EN-US.Test.ISO
Should be correct, because if I recall correctly @abbodi1406 implemented the wimlib-imagex and identifier replacement method that I have posted a long ago. Someone needs to test this.
Most likely, the slow ring will soon start receiving builds of 19H1. https://forums.mydigitallife.net/th...t-cur-rs_prerelease.78320/page-3#post-1481454