Thank you guys for the ESDs, upgraded just fine on two machines, not a single issue fortunately. Now I'm gonna wait for Microsoft to release MFC version 2004 for a PC running a Pro N copy.
Could anybody inform me, where I can find the SHA1 of the "19041.264.200511-0456.vb_release_svc_refresh" ESD's? I cannot find them on Google Thanks
Hi, i used mediacreationtool2004 to download windows 10 2004, but i need install.wim instead of install.esd. Using ESD Decrypter does not seem to work in install.esd. The window closes without creating install.wim. is this a bug?
Hi Enthousiast, sorry for my dumb question... i followed your fantastic tutorial in order to create the last iso (version 2004 (updated May 2020) with the corresponding esd (19041.264.200511-0456.vb_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_en-es.esd). The iso has been created without any problem but its hash does not correspond at all with the official one for Windows 10 (business editions), version 2004 (updated May 2020) (x64) - DVD (Spanish). My question is if I can't get an official .iso of msd after the conversion? Official .iso --> ea0a8cff12be08bd6763123b7a07f55c1de9d450 esd --> .iso --> d6bf16f7e0e76b0ddd49cb71bf207571955bcb38
ISOs, locally created from ESDs, will never have checksums that can be verified, every created ISO gets its own unique hash.
Ok, so it makes no sense for me to take resources from esd when it's considered "homemade". Thank you for the clarification!
Only MVS, Techbench and VLSC ISOs are centrally distributed by MSFT and can be verified by their checksums. The ESD>ISO created ISOs are fine for personal use, it's the same process as the MCT uses, but with some more options to choose from. You're welcome
UUP > ISO / uup-converter-wimlib v46 - EdgeChromium update will be added after cumulative update / cleanup (because it trigger pending operation and mess up upgrade) - Safe OS (WinPE) updates will be handled separately - Show when setup dynamic update is added - Identify updates types if possible