Don't overthink it, the tool allows you to obtain iso files that are not available to the public for download direct from MS such as business editions. The tool provides a desired version of the iso file including MVS, VLSC, and Techbench versions which are official MS releases. You can use Rufus to write the iso to USB media for installation.
Just happened across a typo, I believe... The "READ_ME.NFO" in the files folder has the sources x86 & x64 mismatched for LTSC 2019 17763.1
Ok, so I live in sub-Saharan Africa and I am trying to use this tool with the very limited internet (1Mb/s down) to get MVS 17763.194 business and I keep getting a problem whereby it finishes downloading and then I get a checksum error. From reading this forum, it seems like it may be the antivirus, but I have disabled it and tried again, but again the same problem. I'm ready to completely uninstall the antivirus and try again, but after three failed attempts I just can't afford to buy more data to download another 4.7GB. I have all of the encrypted files downloaded. Is there anyway I can create the .iso from these files using the tool. I've tried to restart the process again in the tools menu, but it wants to restart the download. Any help is much appreciated.
I want to download Windows 10 Refresh 1809 17763.253... How can I achieve that? I try svf.iso.converter.aio.cmd and svf2iso.exe, it only offer me the 17763.107 build
There is no Windows 10 Refresh 1809 17763.253 Your only option is to download 17763.107 then update it Latest update is build 17763.292
17763.253 = 1809 Jan. 2019 Refresh ISO, available at the CMD version of the tool. Available 1809 builds: 17763.1 (MVS) 17763.107 (VLSC) 17763.194 (MVS) 17763.253 (MVS)
The Windows 10 Refresh 1809 17763.253 is under "[M] MY VISUAL STUDIO DOWNLOADS" "[0] START 1809 PROCESS 4 [17763.253]"
Okay that's weird... why put it on My Visual Studio Downloads... anyways thanks undertakerben... downloading now
Because the files come from MVS. I only made the 17763.107 SVF patches, for the tool to use, from VLSC because MSFT made some errors with the language code in the 17763.107 MVS filenames.
The operation broke in the middle. Make sure your Antivirus isn't interferring (create explicite exclusion for the work folder). Delete the SVF file and restart the same process. At the end of the target creation it should hash check the target and state SUCCESS!, else something failed.
Few days back I've had a 32 bit conversion, my antivirus (eset) didn't hinder the process. Anyway I would disable it during the process and see what happens. Update: Disabling the antivirus made no change in iso creation. The tool ended with the same result.