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

D̶o̶e̶s̶ ̶a̶n̶y̶o̶n̶e̶ ̶k̶n̶o̶w̶ ̶w̶h̶y̶ ̶t̶h̶i̶s̶ ̶i̶s̶ ̶c̶o̶n̶s̶t̶a̶n̶t̶l̶y̶ ̶o̶c̶c̶u̶r̶i̶n̶g̶ ̶f̶o̶r̶ ̶m̶e̶?̶
EDIT: it fixed itself today somehow and just worked for some reason, last four or five times it didnt work but i never changed anything to get it to work. Sorry to bother you folks but i guess if it happens to someone else just tell them to try again on a different day.

 

Hello s1ave77, thanks for giving this option to download the Windows 10 ISOs.

Earlier, I had used your tool to download the 1607 Win 10 LTSB ISO. I want to do it again, this time with the latest version of Win 10 LTSB, which now seems to be called LTSC.

Using your Command Line Version tool, first I tried the Techbench Download because it said Win10 in brackets; then I selected (5) WINDOWS 10 1809 [17763.107] (contains N versions), then 64 bit, and then 08 Eng-US. It asked me if I wanted to download this:

[ INFO ] TB ISO: Win10_1809Oct_English_x64.iso
[ INFO ] Hash : bee211937f3ed11606590b541b2f5b97237ac09d
[ INFO ] Size : 4.73 GB

If instead, I selected My Visual Studio Downloads in the beginning and selected [8] START LTSC 2019 PROCESS [17763.1], it asked me if I wanted to download this:

[ INFO ] Source: 17763.1.180914-1434.rs5_release_CLIENT_LTSC_EVAL_x64FRE_en-us
[ INFO ] Hash : fba7f17ffdf018e4cffd49a9819d719d3708cf09
[ TO ]
[ INFO ] Target: en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958
[ INFO ] Hash : 0b8476eff31f957590ade6fe671f16161037d3f6

When I went to the Microsoft site and filled in the options (ISO - LTSC), 64 bit, ENG (US), MS offered me this:

17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-us.iso

which is 3.8 GBs.

So why are there differences in the downloads, and what option should I select? What I would like to do is:

01. Download the latest 1809 LTSB/LTSC ISO
02. Download it from the Microsoft site itself.
03. Use your tool to convert it into a standard ISO (instead of a Trial ISO).

So how do I go about doing this?

 

Hello guys, can't see any computers on my network using this windows LTSC convert, how fix this? No problems w PRO version or any other.

 

Set Function Discovery Resource Publication service to auto. If you have non win10 machines on your network also enable smb1 in the features section of control panel programs and features. Also check settings correct in advanced sharing section of control panel network and sharing center.

 

Hello. I have a very low laptop which has 2gb RAM and an old 2 core processor. My question is, should I get LTSB 2016, or LTSC 2019 for a better performance?

 

Hi, great tool, thanks for the effort from all involved.

I'm using the CMD to create an en-gb Windows 10 jan 2019 ISO. Consumer and Business both target the Dec 2018 ISO\SVF and the script fails because it's unable to find the Jan 2019 SVF.

Does it need updating or is there something I've missed on my end?

EDIT - Fixed in #1130

 

For 1809 Process 4 17763.253 there is no SVF for EN-GB, other languages like EL-GR and ES-ES show OK in the target and ISO is created successfully.

 

Update, fixed the EN-GB [07] error.

In svf.iso.converter.aio.cmd replace the lines at :B1809_4 STREAMLINED

Code:

echo uk-ua^|73d9db306e46abe6de2796f047f665da2b9e7406^|en-uk_windows_10_consumer_editions_version_1809_updated_jan_2019_x86_dvd_ab7247a3^|idFerQyU8irC4dy
echo uk-ua^|8ca457c4e1e8e24c866a4a33c20c895fe4c11f5f^|uk_windows_10_consumer_editions_version_1809_updated_jan_2019_x86_dvd_0309bdc3^|idFerQyU8irC4dy
echo uk-ua^|a4fd006b6471a0313b9d8b9c6a3e9496610705ab^|en-uk_windows_10_consumer_editions_version_1809_updated_jan_2019_x64_dvd_e762a65f^|idFerQyU8irC4dy
echo uk-ua^|eb35abaaaa96e070cefe7669224208332972d88d^|uk_windows_10_consumer_editions_version_1809_updated_jan_2019_x64_dvd_97549fa1^|idFerQyU8irC4dy
echo uk-ua^|30fa86d97198d515d33247d8537c46e50be78783^|en-uk_windows_10_business_editions_version_1809_updated_jan_2019_x86_dvd_464411b9^|idFerQyU8irC4dy
echo uk-ua^|f4cd9fa03365bf002908410c84f60487f4c4e432^|uk_windows_10_business_editions_version_1809_updated_jan_2019_x86_dvd_b57384cf^|idFerQyU8irC4dy
echo uk-ua^|eb51c0e97e310b40e2f7c5efaaa5ec874ce35474^|en-uk_windows_10_business_editions_version_1809_updated_jan_2019_x64_dvd_d13c4e6a^|idFerQyU8irC4dy

with

Code:

echo en-gb^|73d9db306e46abe6de2796f047f665da2b9e7406^|en-uk_windows_10_consumer_editions_version_1809_updated_jan_2019_x86_dvd_ab7247a3^|idFerQyU8irC4dy
echo uk-ua^|8ca457c4e1e8e24c866a4a33c20c895fe4c11f5f^|uk_windows_10_consumer_editions_version_1809_updated_jan_2019_x86_dvd_0309bdc3^|idFerQyU8irC4dy
echo en-gb^|a4fd006b6471a0313b9d8b9c6a3e9496610705ab^|en-uk_windows_10_consumer_editions_version_1809_updated_jan_2019_x64_dvd_e762a65f^|idFerQyU8irC4dy
echo uk-ua^|eb35abaaaa96e070cefe7669224208332972d88d^|uk_windows_10_consumer_editions_version_1809_updated_jan_2019_x64_dvd_97549fa1^|idFerQyU8irC4dy
echo en-gb^|30fa86d97198d515d33247d8537c46e50be78783^|en-uk_windows_10_business_editions_version_1809_updated_jan_2019_x86_dvd_464411b9^|idFerQyU8irC4dy
echo uk-ua^|f4cd9fa03365bf002908410c84f60487f4c4e432^|uk_windows_10_business_editions_version_1809_updated_jan_2019_x86_dvd_b57384cf^|idFerQyU8irC4dy
echo en-gb^|eb51c0e97e310b40e2f7c5efaaa5ec874ce35474^|en-uk_windows_10_business_editions_version_1809_updated_jan_2019_x64_dvd_d13c4e6a^|idFerQyU8irC4dy

 

To confuse things further MS have change the filename from "en-gb" to "en-uk", probably what caught you guys out. Thanks for the credit

 

At least the en-UK files are on the filehost

 

You need to login to view this posts content.

 

Is there a way to upgrade from Win 10 LTSB to LTSC without deleting programs and games?

 

This is not the thread for discussing that, simple ISO upgrade doesn't offer to keep all files and apps?

 

I'll give it a shot and update this comment
sorry for asking in the wrong place

EDIT: updating from LTSB 1607 to LTSC 1809
started Setup.exe and got an error saying "This version is not current" so I disabled my ethernet connection and started it again, selected the option to keep files and apps, and the update ran successfully!
I expected this to be a pain in the ass but i'm pleasantly surprised

Thank you, I appreciate the work you all do here.