RELEASE: S-M-R-T SVF ISO CONVERTER v0.08.01 +++ FEATURE UPDATE RELEASE +++ Changelog v0.08.01 --changed SVF process to use x86 smv.exe for all architectures
Does the GUI version get updated accordingly? Does it need to be? Can you please explain how they relate to each other? I was assuming its just a front-end for the cli version, but I don't see nearly as many updates for it. Thanks for the great tool!
GUI version is different and handles most stuff in native AHK (EVAL ISO download is http request hence no aria), exclusions being SVF downloads from the share and the conversion with smv.exe.
Greetings s1ave77 I'm quite the normie here, so I recently dl'ed your tool to download an official MSDN Windows 10 Enterprise 2016 LTSB and it's an eval version... Does this tool convert the iso into an normal version? I do have an LTSB 2016 Serial from my workplace but i couldn't get my hands on the iso from my IT departement... Could you explain how to transform the iso? I have the GUI version of your application Thanks in advance btw this is the console 19:52:51 CHECKING MVS PREREQUISITES 19:52:51 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:52:51 Language: en-gb 19:52:51 ISO Name: en-gb_windows_10_enterprise_2016_ltsb_n_x64_dvd_9058303 19:52:51 ISO Hash: 0629bf04aa2a61e125ee6eddf917db471dcb8535 19:52:51 EVAL Name: 14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_EN-US 19:52:51 EVAL Hash: ed6e357cba8d716a6187095e3abd016564670d5b 19:52:51 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:52:55 CREATING MVS ISO 19:52:55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:52:55 Language: en-gb 19:52:55 ISO Name: en-gb_windows_10_enterprise_2016_ltsb_n_x64_dvd_9058303 19:52:55 ISO Hash: 0629bf04aa2a61e125ee6eddf917db471dcb8535 19:52:55 EVAL Name: 14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_EN-US 19:52:55 EVAL Hash: ed6e357cba8d716a6187095e3abd016564670d5b 19:52:55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:52:57 Downloading EVAL ISO... 19:58:55 CHECKING MVS PREREQUISITES 19:58:55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:58:55 Language: en-gb 19:58:55 ISO Name: en-gb_windows_10_enterprise_2016_ltsb_n_x64_dvd_9058303 19:58:55 ISO Hash: 0629bf04aa2a61e125ee6eddf917db471dcb8535 19:58:55 EVAL Name: 14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_EN-US 19:58:55 EVAL Hash: ed6e357cba8d716a6187095e3abd016564670d5b 19:58:55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Looks like you aborted the process. To generate the MVS ISO you'll need to let the tool do its job, it will download the EVAL and then the needed SVF patches. Start the process and ... WAIT!
Hello guys! New ISOs released in MSDN for Windows 10 April 2018 Update V.1803: "version_1803_updated_sep_2018_x64_dvd" = RTM Build 17134.1.rs4_release.180410-1804 + September 11, 2018 KB4457128 = OS Build 17134.285 Cheers, KK
We know https://forums.mydigitallife.net/threads/windows-10-svf-repository.63324/page-126#post-1463588
Almost there Only have to create and upload the sha-1 files, and do a full sha-1 check of the used source iso's
Already found all needed info for the database file. Only missing the EVAL to Condumer/Business en-us source ISO SVFs.
Ah you need those in svf, not in svfsfx format, will extract them and re-upload for you Will take a while
Hello, I just registered. First of all, thanks for this tool. I was able to download Win 10 Enterprise LTSB eval and convert it to the "normal" version. The reason I downloaded the LTSB version is because it doesn't have many of the regular MS apps, and I plan to make it even lighter using NTLite. My laptop came with Win 8 preinstalled, which I later upgraded to Win 10. The license is saved in the motherboard itself, and the few times I have reinstalled Windows, I have never had to enter the license as it automatically picks it up from the motherboard. At present, I have Windows 10 Home on C: drive. I want to install LTSB on D: drive. I'll be using the Microsoft Toolkit to activate it. My question is, will the C: drive Win 10 Home be able to detect that I have installed a copy of LTSB on D: drive and activated it using other means, and then cancel my original license (of Win 10 Home)? Will the license of the D: drive LTSB be stored in the motherboard as well? When activated, the LTSB license will probably be stored in MS servers, and they might be able to see that I have two copies of Windows on my laptop. I don't know if they do this, but I'd rather stay safe than lose my Win 10 Home license. If there are going to be problems, I'd rather not install the modified LTSB I have now, and instead install the 3 months trial and later, when the time period expires, try to extend the license, or format and reinstall LTSB again. Thanks.
Not really related to the subject of this topic. LTSB has an EI.CFG which lets you skip the key question and ignore the MSDM for Home. When you are finished installing i would suggest you to use KMS_VL_ALL by @abbodi1406 to KMS activate LTSB.
I got a hash mismatch error on my first run so I reran the script and it completed without error. It feels like the script did not wait long enough for the download to complete. Or it could be user error .. Thanks for the effort s1ave77.
Just downloaded the new toolS-M-R-T SVF ISO CONVERTER v0.09.01 , when open it it says in top v0.08.01, havent you changed that or did you upload the old tool? Thanks.