Hi, I have downloaded this file: 22621.525.220925-0207.ni_release_svc_refresh_CLIENTCONSUMER_RET_A64FRE_it-it.esd and then converted with esd-decrypter script but I don't understand why after conversion the ISO file name is different: 22621.525.220924-1919.NI_RELEASE_SVC_IM_CLIENTCONSUMER_OEMRET_A64FRE_IT-IT.iso Where I'm wrong?
@Pikylusk Nothing wrong, it's cosmetic ESD name (label) is set manually by Microsoft, it cannot be detected from ESD contents itself just edit decrypt.cmd and change 0 to 1 Code: set ISOnameESD=0
How am I supposed to verify the hash of the refresh releases? I see a hash value at the end of the filename of the 22h2 base release. but all the refresh releases lack the hash value in the filename. give me a hint.
https://forums.mydigitallife.net/posts/1700014/ products cab https://forums.mydigitallife.net/se...post&o=date&c[user][0]=204274&c[thread]=83747
thank u very much. I missed the connection between the products.xml and the hashes.. maybe if someone could add something like "if you want to check the hashes, see the products.xml <here>" - in the first post with the ESD links. just to answer upcoming questions beforehand.
22621.525 and 22621.382 links has clientconsumer arm64 ESD builds with Home edition is there any way to get the same clientconsumer arm64 builds for the base 22621.1 build?
No Code: WSUS releases: 1803+1809 : only clientconsumer arm64 1903+1909 : both 2004+later: only clientbusiness arm64 19042.631 accidentally got both