Windows 10 SVF Repository

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Thanks a lot GezoeSloog, outstanding effort.

I think few people realize how much it takes to do all those svf's that you do and just take it for granted and can't be bothered to even leave a simple Thanks.

 

Please provide this

FROM
en_windows_10_enterprise_version_1607_updated_jul_2016_x86_dvd_9060097.iso
TO
en_windows_10_multiple_editions_version_1511_updated_apr_2016_x86_dvd_8735185.iso

(OR)

en_windows_10_multiple_editions_version_1511_updated_apr_2016_x64_dvd_8705583.iso
TO
en_windows_10_multiple_editions_version_1511_updated_apr_2016_x86_dvd_8735185.iso

thanks in advance. I didnt know that it is possible to convert from one edition to the other and i simply downloaded the enterprise edition. If only i have known i would have surely got the multiple edition instead of the enterprise edition as the source is MULTIPLE edition for all SVF files.

 

You need to login to view this posts content.

 

please svf
14901.1000.160805-1700.RS_PRERELEASE_CLIENTENTERPRISE_VOL_X64FRE_Es-eS.svf

 

No sense from ESD to ESD - SVF size is too big.

 

Did anyone make SFVs for these? I can't find them anywhere.

pp_windows_10_enterprise_n_version_1607_updated_jul_2016_x64_dvd_9055909.iso
pp_windows_10_enterprise_n_version_1607_updated_jul_2016_x86_dvd_9057140.iso
pp_windows_10_enterprise_version_1607_updated_jul_2016_x64_dvd_9054262.iso
pp_windows_10_enterprise_version_1607_updated_jul_2016_x86_dvd_9059634.iso

 

You need to login to view this posts content.

 

I have that link but unfortunately it doesn't contain the SFVs for the 4 ISOs mentioned above.

 

@johnye_pt

Enterprise is the same 4 VLSC & MSDN

 

This should be written in big red letters at the top of the page

 

Just looked at the SHA1 and they're the same many thanks

 

Hello friends, I see some insider program or something like that in ltsb. Does it matter ?. Ltsb is not in development stage and it is full fledged as enterprise edition, right?

 

Its flagged as EnterpriseS and EnterpriseSN. In every MSDN released windows 10 you can find insider program, the use is optional.

 

Hi Guys...
i'm bit lost here...
is this iso "14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US.ISO" ( decrypted from esd ) equal to "SW_DVD5_WIN_ENT_10_1607_64BIT_English_MLF_X21-07102.iso" or "en_windows_10_enterprise_version_1607_updated_jul_2016_x64_dvd_9054264.iso" or none of them?

i'm confused of what svf to get to ltsb version since this "SW_DVD5_WIN_ENT_10_1607_64BIT_English_MLF_X21-07102_TO_en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.svf" failed to extract the ltsb version...

thanks in advanced...

 

It's equal in behaviour and build but not the same iso/sha-1 because the iso created by the ESD is an unique iso, it's made on your pc and has it's unique checksums.

The ENterprise VLSC and Enterprise MSDN iso's are exact bit for bit copies and share the same checksums.

For "SW_DVD5_WIN_ENT_10_1607_64BIT_English_MLF_X21-07102_TO_en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.svf" to work you have to download the VLSC iso or the MSDN iso and rename it to "SW...MLF...iso".

 

ISOs created from ESD differs by 32 bytes only.
So ESD to ISO + prepatch + SVF should work

 

I guess it's in the headers of boot.wim and install.wim (GUIDs?)
I don't know whether these bytes affects the setup process.
If not - they should be replaced by zeros on ESD to ISO creation