how to catch windows 10 updates esd links, with right filename

Hi, I don't know if I missed some programs in "mdl projects" section but I'm seeking for an application which lets to catch the links of the insider program esd (and all other esd listed in the windows update) with the right filename.

I tried the Windows Update MiniTool, it actually lets you copy two links from the insider esd listed (for instance insider preview 11102), but they are just alphanumeric adresses, not the official ones as the WTZ's ones

I tried the other esd autogenerator programs, in the mdl project section, but no app of them worked

I just have to download the insider preview from windows update, and then take the "install.esd" from $WINDOWS.~BT directory?

I wish I could catch the esd links with the right filename, not just take a generic "install".esd and decrypt it

 

so the wtz's esd are manually renamed with the information from datastore.edb, and then reuploaded?

how can I extract the exact file name and hashes of esd files from datastore.edb?

I used ESEDatabaseView from nir sofer, but I see lots of stuff and I can't find info about esd downloaded

If the database.edb doesn't have the exact esd filenames (that is "pro" "x64" "initials of country" etc...) how can I obtain them, so that I can manually rename the insider preview esd downloaded?

Is there a database available online, regularly updated, which lists all the names of insider and official esd releases about main countries, and pro/core/enterprise/x86-x64 versions, so that one can take the filesname from there?

 

I did some search for a tb file viewer but with no result

could you tell me which program I need to manage and view datastore.edb and tb files?

EDIT:

now I understood the hint; the program I was using (esedatabaseview by nirsoft) was correct to view software distribution database such as datastore.edb

I just needed to choose "tbfiles" from the above tables; now I found the correct official esd filenames, along with hash codes =)

thanks abbodi

 

I noticed a strange thing. The hash codes on the database are different from the ones of the esd download, and I'm sure it's the same insider preview release; the filename sizes are different too.

But I remember the download process went well without interruptions, then I took the install.esd from $WINDOWS.~BT

Why these differences? Is it because the esd file is then reconstructed inside that hidden directory so it gets a different size? Or I just did something wrong during downloading, so that I needed to redownload the whole esd file from windows update?

I could return to the previous build, then download the insider preview again but making sure that nothing goes wrong