No it's the same thing, the good script recognizes both Edit: It'sn't the same thing ok thanks i ever read this , but i thought that it was possible to use your tool just for one image.esd Sorry
full ESD has several indexes, including install.esd which has never been the same thing and never will be Open both with 7zip and you'll see
It is not the same, As shown here: https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/page-182#post-1843203 And the reply by the creator of both tools: https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/page-182#post-1843203 Most likely it detects it because of the .esd at the end.
i tryed with another LTSC 2021 unattended version with .esd who he has three versions and it's the same thing. It's prompt 4 images. I 'll try it with an official esd to see if it's good. Thanks
Do you understand what esd-decrypter even do and what files it works with? why do you need any script for install.esd? just add it to your ISO if you want to convert to install.wim, use WIM <> ESD
Yes i read your readme for esd-decrypter " Automated command script to process Microsoft Windows full ESD file (encrypted or decrypted), and convert it into a usable state (ISO / WIM / decrypted ESD)" But i'm confused, sorry, may be it's not for what i want now. thanks
Usually, I sort SKUs after conversion, by re-exporting them to a new WIM. It's time consuming, so, I ignore Insider and test releases completely.
uup-converter v109f - Fixed creating LCU msu from psf/wim files i didn't update readme, but "SkipLCUmsu" option has no effect on above scenario for 22621-22635 builds thanks to @Clusterhead, @TS2008, @Enthousiast for reporting