Complicated? It only asks you which options you want to use and you press the corresponding number...
The basics are still the same: https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/page-77#post-1380516
It seems, it does not support .387 at the moment. Anyway, I am not gonna risk it, I have already lost 15GB of disc space because of adguard and since my partition is 32GB, that is not little. I am stuck with it, till reinstall.
It supports all ESD's, just drag and drop the ESD on the decrypt.cmd and select what you want, as @Mr.Magic explained. You lost 15GB? Did the tool error and not clean up after running? Clean it up and it will be back, run in an elevated cmd: Code: dism /Cleanup-Wim If it ran successfully, you should be able to delete the mount folder. ps, afaik, there is no 18362/3.387 ESD (or did i miss some info?).
Both these tools need to be run in admin mode. (Perhaps a check for this should be incorporated into the tools themselves.) Apart from that, it is dead easy. 1. Download the tool. 2. Extract to an empty folder. 3. Download the ESD. 4. Move the esd into the folder you used in 2. 5. Run the tool decrypt.cmd as admin. 6. Press the number corresponding to your choice. I used 2 (for one edition), then in the next step I used 6 for Windows 10 Pro. 7. Press Enter and wait. It will create the iso.
Not auto elevate, just detect current mode and if not admin, prompt the user to run it in admin mode.
That did the trick, thank you, I was about to format to get it sorted out. Thanks, this is what I needed, a few simple steps.
Forgive me this remark, but do we now need to explain how to unpack a tool too? How did you run it before?
Boss, you've been here 10 years, and were probably in the expert category even before that. This site has 1.1 million members. Surely it is reasonable to expect that some of them will be newbies.
I never tried it before, when I saw several pages long tutorial, there is not even a download link, I had to download it from WZOR just now. EDIT: Nevermind, I downloaded 18363.356.190918-2052.19h2 and it created 18362.356.190918-2318.iso, that is silly. I will just wait for ISO. EDIT: I have tried again and now I can not even unmount it and have only 3GB left. Luckily I have found some real smart people, who can create and share ISOs (unlike unwilling MDL), so downloading german .387 ISO.
It's pre-release per Microsoft words 1909 will never be final, because it's not real new build any 1903 + enablement pack + latest CU = 1909
There is no new build, there is just one update that bumps it to the mock 18363/1909 and enables the 1909 features, all other updates are 18362 based. 1909 will just be a 1903 refresh iso, with 1909 EP integrated as the only difference.
uup-converter-wimlib v39 - Enhanced 18362/18363 differentiation and set proper branch 19H2/19H1 (thanks to @Enthousiast for testing) - Lowered required Host OS to Windows 8.1 for ARM64 update integration (using this workaround) - Added visible script version
why is the download link from the produxt.xml for the english RLS 1909 not available any more, were there any problems?
Hi. I've recently understood what SFVs are for, but I can't figure out what ESDs are for yet. I know that ESDs are compressed files. I think I read somewhere that they save ~30% compared to WIMs. I know there's a script made by abbodi1406 to decrypt ESDs and end up with an ISO. What I don't understand is what would be the difference between downloading an ISO and downloading an ESD to then convert it into an ISO. Is there any advantage at all if what I ultimately want is an ISO? I'm thinking there should be some perks in that, but I can't see them... Otherwise, why would there be a separate thread, right? Could someone clarify that for me?