Windows 10 ESD Repository

@kamyshoviy
yes

v66f = v66 + fixed %_www% line

 

Sorry, I was bored...
What do you think, will we see new ESDs anytime soon? From the list below (Releases and ESD time stamps) you would think so...?
The most recent 21H1 ESD is starting to spoil/ smell.

1507: 07/09, 09/09
1511: 10/29, 02/12, 04/26
1607: 07/15, 11/19
1703: 03/17, 06/07, 07/10
1709: 09/28, 11/09, 12/13
1803: 04/10, 06/19
1809: 09/14, 10/29, 01/08, 03/12
1903: 04/01, 06/12, 07/09, 08/09, 09/09
1909: 09/18, 10/07, 01/09
2004: 02/18, 05/11, 07/10, 08/08, 09/07, 10/09
20H2: 08/14, 09/27, 10/09, 10/12, 11/06, 11/19
21H1: 03/05, 04/09

 

I think 19043 will get another ESD set

 

hopefully before MS releases 19044 (21H2)

 

Who need another 19043 ESD ? It's have problem with Meet Now and heavy OS.

 

ESD>ISO Converter changelog for 60f says that it added support for Server editions ESDs
https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/#post-992731

but on the post with the links
https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/#post-992532

there aren't links for Server ESDs (in 1809 sections), where are the links for server ESDs?

 

Prepared for Server ESDs

 

So at the moment MS links for server ESDs aren't available right?

 

Can't remember but when they were out, they would be published here.

 

You mean that in the past there were links available but now they're not?

 

No, there was info available that indicated server 2022 would be on ESD too, server 2022 LTSC already is available on UUP dump.

 

Am I correct to assume that checksums for created editions from ESD to ISO files isn't verifiable?

Like for example I created this ISO,

Code:

19043.928.210409-1212.21H1_RELEASE_SVC_REFRESH_CLIENTENTERPRISE_VOL_X64FRE_EN-US

with the folowing checksums

Code:

MD5: 6feaf26cfe1a5947e573bfea801e7c2d
SHA1: 559e87826b040561f38d1bd023475fa9445be784
SHA256: a9d3553ff6e53fd72d84a4fa02dcc74e0a2b9ce69bbfbfab19f964ed10b1e71f
CRC32: 08bf9eeb

However I can't find mentions of these online anywhere and I made the ISO with standard wim and not compressed.

I guess if people were to create the same ISO based on the same properties they might get the same checksums.

I used this ESD for creation

Code:

19043.928.210409-1212.21h1_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_en-us

It's not that big of a deal per se, but knowing that what you got is OK is a big relief.

I think I'm finally ready to leave 1909 and test 21H1.

 

ESD hash is verifiable, but ISO hash isn't.
This is mostly due to the somewhat random nature of compression algorithms used to make the install.wim/esd.
Also when making ISO there may be slight difference fom time to time.
Even a single byte changed will completely change the hashes.

 

Thanks for chiming in!

I guess I don't have to worry that much about it being corrupt and everything in the process of making the ISO went smoothly.

Let's burn this!

 

Just a heads up, if you chose wim format then you probably won't be able to burn it to a standard 4.7G SL DVD

 

Thanks!

I think I have a couple of spare Verbatim Dual Layer discs lying around, funny as it may be I only use optical media for Windows these days.
I'm a little bit old fashioned when it comes to just that.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I still own numerous CD-R, CD-RW, DVD-R, DVD-RW, DVD+R, DVD+R DL, DVD+RW, BD, BD-DL, BD-RE media, as well as multiple burners. Not alone you are.

I also still own many Floppy disks, 3.5", 5.25" and even one 8". Not relevant for storing Windows Setup, I fear.

 

You need to login to view this posts content.