This only apply to encrypted ESD files ESDs are no longer encrypted since 16299, so the backup option is not shown or needed It does not exist
Thank you for the answer. I was asking as after I decrypt the esd into an iso image and I checked it with "windows and office genuine iso verifier" it shows "not genuine (msdn) - Hash is not found in base!" When I do the same thing but with the .svf alternative it shows genuine. I've never get genuine iso from esd. Is it something wrong that I do, or this is how it should be and it doesn't matter? Thanks again.
Why do expect ESD converted to ISO to have static hash? it will be always different from official ISOs the content of the same editions in both will be the same it's just different containers
In my experience, the ESD decryption has always resulted in the same size ISO for me, even if there are different date and time stamps for the Windows component files. If the ISO was a different size each time you decrypted it from the ESD, then it might be something to be concerned about. But even so, the structure of the ISO is the same as an ISO you would get from MSFT. The expert scripters here on MDL are people you can trust.
Two files can not have the same binary checksum without being bit-identical (or the checksum algorithm having collisions due to it being too weak). The ESDs might possibly be bit-identical, the ISOs are definitely not. There are also functional checksums which will ignore certain aspects of the files when comparing. One example would be a text checksum ignoring line endings.
Where do you see only Home? The ISO should contain: Code: Client Business Volume ISO Edition List: Windows 10 Education Windows 10 Education N Windows 10 Enterprise Windows 10 Enterprise N Windows 10 Pro Windows 10 Pro N This ISO should contain: Code: Client Consumer Retail ISO Edition List: Windows 10 Home Windows 10 Home N Windows 10 Home Single Language Windows 10 Education Windows 10 Education N Windows 10 Pro Windows 10 Pro N N editions exist only for the countries for which MSFT is obliged to include them. To me it seems you are using an outdated and probably unsupported ESD > ISO converter? Use the recommended ESD > ISO
@Enthousiast ...Thanks for detailed info. I got the Home from the title of the ISO produced by the ESD->ISO converter. .The full title is 'en_windows_10_home_19041_x64_dvd.iso' . The converter I used was qad - decryption program and it is credited to Eric Biggers - wimlib. Question still remains is this: If I have to reload W10 from the disk I have, I think it's 1903, can I use the 21H2 disk to update it?
How old/outdated would that one be? With a properly converted ISO (and at least 19042) it should work, yes.
@Enthousiast ...thanks again for reply. It says on the readme that the crew who developed it are from MDL. I'm still a noob here at MDL and I don't know where to look for current stuff. I took the compressed files from page 1 of this thread and I think I got a link to the decrypter there. Not sure.
Error: 0x80070002 using uup-converter-wimlib-75u & uup-converter-wimlib-76 with 22000.466 & 22000.434 An ISO is created but it displays an error during creation. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22000.1 An error occurred trying to open - D:\W10UIuup\Windows10.0-KB5008353-x64\update.mum Error: 0x80070002 Error: 2 The system cannot find the file specified. Image Version: 10.0.22000.1 An error occurred trying to open - D:\W10UIuup\Windows10.0-KB5009566-x64\update.mum Error: 0x80070002 Error: 2 The system cannot find the file specified.