[TOOL] s1ave77s S-M-R-T SVF ISO CONVERTER v0.51.01 [1903/LTSC2019/Techbench]

@s1ave77

I really do not know anything about autohotkey, but I see that You forget to add (number) 6:

Code:

Run, %comspec% /c (%smv% BuildPatch "%SVFName%" "%ISOName%.iso" "%SVFName%.iso" -nbhashbits 24 -compressratio 192 -sha1 -sha25)

to:

Code:

-sha256

 

Instead of -sha256 it's better to add -nomd5
and do not waste time for computing not published alternative hashes.
SHA-1 ought to be enough for anybody

 

I did exactly for mine SVFs.

But without:

Code:

-nbhashbits 24

 

MVS LTSC 17763.107 refresh also lacks N, VLSC 2019 LTSC = MVS 2019 LTSC

 

@s1ave77 Big thanks for your excellent work ! It helped me a lot !

 

Sir;
Enthousiast suggested I post this:
tool svf2iso
selection: LTSC19_2_VLSC, business,x64,N-version,en-us
this got me:
14:39:26 CHECKING MVS PREREQUISITES
14:39:26 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
14:39:26 Language: en-us
14:39:26 ISO Name: SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_MLF_X21-96425
14:39:26 ISO Hash: d5b2f95e3dd658517fe7c14df4f36de633ca4845
14:39:26 EVAL Name: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-us
14:39:26 EVAL Hash: 369e645a197bc2ca8309cb80467a85a16eacd1a7
14:39:26 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I was able to activate with KMS_VL_ALL but he felt the wrong image was downloaded

 

My test:

Code:

23:39:07 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
23:39:16 CREATING MVS ISO
23:39:16 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
23:39:16 Language: en-us
23:39:16 ISO Name: SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_MLF_X21-96425
23:39:16 ISO Hash: d5b2f95e3dd658517fe7c14df4f36de633ca4845
23:39:16 EVAL Name: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-us
23:39:16 EVAL Hash: 369e645a197bc2ca8309cb80467a85a16eacd1a7
23:39:16 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
23:39:16 Downloading EVAL ISO...
23:40:22 EVAL ISO exists.
23:40:22 Checking hash...
23:40:46 Check Hash: 369e645a197bc2ca8309cb80467a85a16eacd1a7 | SUCCESS!
23:40:46 Downloading Target SVF...
23:40:46 SVF Name: SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_MLF_X21-96425
23:40:59 Creating Target ISO...
23:41:13 Target ISO exists.
23:41:13 Checking hash...
23:41:37 Check Hash: d5b2f95e3dd658517fe7c14df4f36de633ca4845 | SUCCESS!
23:41:37 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

When you ended up with the EVAL iso, most likely the AV interfered, check the AV logs and quarantine.

 

Twice Ive downloaded Server 2019 and twice the hash has failed.

f**k this tool.

 

On behalf of @s1ave77 cause he's a gentleman not me: f**k you asshole.

 

First time user of this program. It downloaded this first '17763.1.180914-1434.rs5_release_CLIENT_LTSC_EVAL_x64FRE_en-us' the added and SVF to make it 'en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958' so if I install this new ISO, will KMS_VL_ALL activate this version for longer than 90 days because the first version says EVAL. Also off topic a bit here but how do I automate KMS_VL_ALL to run at different intervals to reactivate LTSC instead of doing it manually?

 

Also is there an N or KN version of the LTSC ISO I mentioned above?

 

2019 LTSC 17763.1 has N versions, 17763.107 doesn't.

KSM_VL_ALL can activate the non eval.

For KMS_VL_ALL info: read it's readme

Code:

================================================================
# Auto Renewal:

To install this solution for auto renewal activation, run these scripts respectively:

1-SppExtComObjPatcher.cmd
install/uninstall the Patcher Hook.

2-Activate-Local.cmd
activate installed supported products (you must run it at least once).
you may need to run it again if you installed Office product afterwards.

================================================================

 

Hello,
I understand the main files come from My Visual Studio portal.
I don't get which is the source of the SVF files.

 

The svf files originate from my svf repo's, all made from original MVS/VLSC iso's.

With main files you mean the source iso's? Most are eval iso's from technet evaluation center.

The techbenh iso's originate from official MSFT servers and are direct msft downloads.

 

so the SVF's are the differences between the original MVS/VLSC iso's and the eval versions.
Right?

 

You need to login to view this posts content.

 

@Enthousiast, In my case I have a legal en_us LTSB2016 ISO with a legal product key.
When I have to install it in a virtual machine (I use Linux as main OS), updating takes ages.
When I try to download recent ISOs, say LTSC2018, my product key does not work.

Do you know if there is a (Microsoft) link to download the LTSB2016 build 14393, so that my product key will work?
I mean an ISO or an ESD (which I could convert to an ISO).

 

1. your product key isn't legal, when used outside of it's business environment it was stolen from.
2. Keys that work on LTSB don't work on LTSC.

 

What makes you speculate that I have stolen it? I am legally entitled to use on my computer (the laptop I was given) the LTSB edition. Chances are that I am entitled to use the LTSC, I don't know for sure. BTW, I tend to prefer LTSB since it works out of the box with SMB shares. With LTSC I have to tweak the registry (but the provisioning script to tweak is in the SMB share itself).

LTSB is perfect (I don't need to be cutting edge), but it wastes a lot of time to upgrade after the setup.
I would simply have my current LTSB ISO with updates already slipstreamed in it. Unfortunately with the introduction of the Media Creation Tool, the practice of slipstreaming is outdated, and for good reasons, just I am told the MCT does not work for enterprise editions.