I can't get it to work. I'm trying to select Windows 10 2016 LTSB in English but when it tries to go through the verification process, it says, "Mismatched".
It should work: Code: 16:15:27 CHECKING MVS PREREQUISITES 16:15:27 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 16:15:27 Language: en-us 16:15:27 ISO Name: en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483 16:15:27 ISO Hash: 031ed6acdc47b8f582c781b039f501d83997a1cf 16:15:27 EVAL Name: 14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_EN-US 16:15:27 EVAL Hash: ed6e357cba8d716a6187095e3abd016564670d5b 16:15:27 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 16:15:30 CREATING MVS ISO 16:15:30 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 16:15:30 Language: en-us 16:15:30 ISO Name: en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483 16:15:30 ISO Hash: 031ed6acdc47b8f582c781b039f501d83997a1cf 16:15:30 EVAL Name: 14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_EN-US 16:15:30 EVAL Hash: ed6e357cba8d716a6187095e3abd016564670d5b 16:15:30 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 16:15:30 Downloading EVAL ISO... 16:16:42 EVAL ISO exists. 16:16:42 Checking hash... 16:17:04 Check Hash: ed6e357cba8d716a6187095e3abd016564670d5b | SUCCESS! 16:17:04 Downloading Target SVF... 16:17:11 Creating en-us Source ISO... 16:17:22 Source ISO exists. 16:17:22 Checking hash... 16:17:44 Check Hash: 031ed6acdc47b8f582c781b039f501d83997a1cf | SUCCESS! 16:17:44 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
RELEASE: S-M-R-T SVF ISO CONVERTER v0.07.01 +++ FEATURE UPGRADE RELEASE +++ Changelog v0.07.01 --added 16299.15 (RTM) (thanks to Enthousiast) --changed 1709 EVAL links (thanks to Sajjo) --added 17134.228 (thanks to Enthousiast) --switched Server 2016 to working EVAL and new Repo (thanks to Enthousiast)
@s1ave77 just wondering why it was decided to set eval iso as base instead of techbench iso in this project? I suppose with en techbench iso as base, this project could have some advantages. for example - i guess anyone browsing mdl or google already have basic english knowledge and for that reason i assume most like to keep an en iso, and those people also like to keep an iso in their language i guess. apart from this many people have consumer iso's would like to convert it to business iso or n version and i suppose addressing these issues is the most imp aspect of this tool. in these examples having an eval iso creates an extra and unnecessary file and this extra burden can be safely avoided with en techbench iso as base?.
but techbench download method is also reliable and i never saw a problem in generating links with that. (except old releases as win 7? and office 2007) with techbench as base, svf patches can also be created for win 8.1 GezoeSloog svf repo can be mirrored to enth repo so it'll not require any extra svf creation work. edit - i guess with this win 7 mvs repo can also be done.
TB doesn't offer server nor LTSB. I don't mirror @GezoeSloog his work for a reason, i don't want to be a copycat like many are, these days, and i go another route with my patches (en>xx directly for all iso's and not first en>xx consumer and next consumer > business) and i did also svfsfx patches. And now @s1ave77 made a tool (with help from @mkuba50) to use my SVF Repo's. We haven't found a good official perma source for 7 SP1 patches.
I'm in no way here implying that my suggestion are good or should be applied, i'm just posting my suggestion as a form of only feedback. about LTSB i suppose they can be converted from techbench 1607 iso with very small size svf patches. i guess few people download server, for server you can use other sources than TB, i guess it can be adjusted. besides, all windows 10, 8.1, and 7 (ultimate available on TB) mvs iso can be made from techbench as source. while using eval as base it is restricted to only win 10 (i guess old win 10 releases are also not possible)
#1. Techbench has proved to be too unreliable to be a proper source. #2. LTSB is single edition where Techbench are multi edition, not sure what size SVF would be. Again #1. would apply. #3. Server is direct EVAL to any lang conversion, so not much to gain here. #4. see #1.
thats fine. but it would be a very impressive project development if it can provide whole mvs repo of win 7,8.1 and 10 without having to download extra (eval) big files.
@Enthousiast 7600.16385.090713-1255_x64fre_enterprise_en-us_EVAL_Eval_Enterprise-GRMCENXEVAL_EN_DVD.iso 7600.16385.090713-1255_x86fre_enterprise_en-us_EVAL_Eval_Enterprise-GRMCENEVAL_EN_DVD.iso ?
There are no 7601 Windows 7 Evaluation ISO's. 1. 7600 are useless for svf patches, any patch will be 1.5GB or more for SP1 ISO... Probably no one needs SP0 ISO. 2. Server 2012 R2 Evals are also useless because they are IR3, but MVS ISO's are IR5, so patch will be also huge... 3. Server 2008 R2 cannot be used as source for Windows 7 patches, because patches also are huge. I tested it a long time ago. "care.dlservice.microsoft.com" links are more likely to be broken (You already could see that Server 2016 needed link replacement), and "download.microsoft.com" links always work.