Windows 10 ESD Repository

Yes, @Enthousiast thankfully tested upgrade and it worked

fixed.

 

I see another advantage for AddUpdates=2 - use it for a base image and you'll never lose it. Just replace the updates with newer ones, later.

 

But remember to follow the naming scheme
1 for SSU, 2 for other updates, 3 for LCU

 

What's that LCU ?

 

Last Cumulative Update!

 

Finally

 

Anyone who has some log files from v 30?

 

You need to login to view this posts content.

 

Hi. I got error while conversion .esd to .iso (to .iso with compressed .esd and also to .iso with standard .wim). Base .esd i downloaded twice. To conversion I used esd-decrypter-wimlib-50? Any advices?

 

What exact esd file are you trying to convert to ISO?

 

18362.239.190709-0052.19h1_release_svc_refresh_CLIENTCONSUMER_RET_x64FRE_pl-pl.esd downloaded from tb.rg-adguard.net.


edit:

sha on page above is a8b5e23b03549240a86a4076480a5289219866f8
sha of my .esd is 09db216761ef1f134f977dbae1d879977a154f89 (the same for both .esds)

 

You need to login to view this posts content.

 

The sha can't be the same for two esd files, unless you mean the same file.

These are the checksums of the ESD:

Code:

Name: 18362.239.190709-0052.19h1_release_svc_refresh_CLIENTCONSUMER_RET_x64FRE_pl-pl.esd
Size: 3416807882 bytes (3258 MiB)
CRC32: 9C638D64
CRC64: 4DB0728E454FD1E0
SHA256: B798BB6B71F43721B0A93A2BE22C63F6B74D80B6C793901F0946FD2EA7059058
SHA1: A8B5E23B03549240A86A4076480A5289219866F8
BLAKE2sp: CDD0EE309040B94314AD35164D636505F46CC8C6018B7D45ECB7D61CB927CDD2

Your download seems to be corrupted.

 

I used your link to download .esd and converted it with no problems

It's weird .esd file downloaded (with IDM) twice from tb.rg-adguard.net was corrupted.

 

The ESD's are all downloaded directly from MSFT servers, the only thing causing this is locally on your network/hardware/software.

 

I'm getting this filename for the Consumer x64 English version ESD with v50

18362.239.190629-1845.19H1_RELEASE_SVC_PROD1_CLIENTCONSUMER_OEMRET_X64FRE_EN-US.ISO

Did the install.esd way (option 2)

Is this ok? I was assuming the date would match the ESD file of 18362.239.190709-0052.19h1_release_svc_refresh_CLIENTCONSUMER_RET_x64FRE_en-us.esd

 

Yes, OK
matching ESD date label will require updating the script and setting it manually
i didn't see it's really needed this time

you can add this to line 548 if you want

Code:

if %revision%==18362.239 (set _label=18362.239.190709-0052.19h1_%_rsr%_CLIENT&set branch=19h1_%_rsr%)

 

Just rename it manually after decryption. It takes more time to edit the script than copy the filename from the ESD to the ISO file.

 

Thank you, just wanted to make sure you knew.

 

uup-converter-wimlib v31

- Fixed the upgrade issue occur when using ISO created with External updates mode
thanks to @Enthousiast and @Carlos Detweiller for reporting