i dont know but it looks not clean way..i need orijinal iso... downloads the SVF to create the en-us ISO after it will download the SVF for the chosen language..
The general misconception that s1ave77's svf2iso tool is flawed or puts isos together incorrectly is well, incorrect. The tool gathers the files needed directly from Microsoft. If people were to upload homebrew iso's on here (not allowed btw) then they would have had to get them via the same tool or via their own MDL accounts. It's up to you to either get yourself a japanese iso from the link I provided or get yourself an MDL account and get it from Microsoft. Either way you would end up with the same exact iso and build number at this point in time. You can also add the updates manually into the iso and reach build number 17763.134 with the links provided in this page. It takes literally 5mins to do it all with a good internet connection. Your choice.
People which are the differencies between EVAL .iso and not EVAL .iso? So still waiting for LTSC NON EVAL .iso?
The only concern for me now is whether the file-deletion bug of 1809 is resolved for sure. For the record, I am planning to try LTSC 1809 (en-gb) on VMware as soon as the storm has cleared: then I will know for sure what GPO and privacy tweaks I will have to implement to make Windows 10 behave properly my new machine, which will have the RTX 2080. When I installed the evaluation version via https://forums.mydigitallife.net/th...rprise-n-ltsc-2019.76325/page-99#post-1481228, the setup seemed to think I am installing the Home or Pro version: but then again I may have used the older version or there is something specific to the evaluation version.
the "file-deletion" bug was fixed if it is at least build 17763.55 (KB4464330); the "refreshed" version of LTSC 1809 (build 17763.107) should also contain the fix
ms should work with svf save time download gbs all the time :\ any svf from .1 to .107 ? and server 2019
Reading thru the latest posts, i get teary eyes, all info is published many times over and cumulated at the OP of the sticky 1809 thread, @Tito, links at the OP of this thread. You can offline update the refresh iso with the new updates, but it's better to integrate updates into a baseline iso (not containing superseded updates, like the 17763.107 refresh iso has). The svf2iso tool can download Techbench ISO's (consumer), MVS iso's (LTSB/C, Consumer and Business, by downloading the EVAL Source ISO + needed SVF patch, and it creates the original ISO you selected at the start) and it can convert SVF > ISO manually.
Its time for you to learn about hash verification of files. It doesn't matter from where you download the iso's, you just need to verify the file with official sha-1 hash, (will be available soon)
there small different between .1 to .107, so its doesn't necessary to redownload the iso just svf to the last version
Did you ever create thousands of SVF patches and think of all the different needs different members can have, when we would do all they want there would be many different extraction paths, one wants 17763.1 > 17763.107, others want this and others want that. It would mean that there would be a repository for every need, that takes days of work, TB's of online filehosting. To be honest, nobody on a tech site, with all the offline update options published, like W10UI, MSMG, and manually by dism commands, the refresh iso's aren't even needed, actually not advised to use at all.
the newly released ISOs (17763.107) from WZOR contain an EI.CFG that identifies the edition as "EnterpriseS" the old ISOs (17763.1) did not have any [Edition] section in their EI.CFG file should a LTSC sku identifies itself as an "S" edition? is this old news?
why so much just 32bit en-us xxxx.1 to xxxx.107 64bit en-us xxxx.1 to xxxx.107 server 2019 en-us xxxx.1 to xxxx.107 and then from xxxx.107 en-us to any other lang so each person should have en-us iso and svf to his lang with this he can jump any place he like even with 2 steps just not need to search much for the right svf or combine the patch, with smartversion or ms would do base iso
