Hm, I cannot produce that error, really. I tried. I put SVF_Batch_Extractor to some new folder, without source and SVF, run, close, smv.exe and SVF_Batch_Extractor.cmd are deleted. There is clearly inside config.txt: (for delete both files) Code: ;!@Install@!UTF-8! InstallPath="%%S" RunProgram="SVF_Batch_Extractor.cmd" Delete="SVF_Batch_Extractor.cmd" Delete="smv.exe" ;!@InstallEnd@! Tried again, wake now, 2016 LTSB x64 ISO as source and 2016_ltsb_x64_to_2016_ltsb_x86.svf. 2016 LTSB x86 ISO is here and smv.exe and SVF_Batch_Extractor.cmd are deleted. Really do not know how to produce error.
Obviously, but this is a response to the "SVF_Batch_Extractor.exe" that is a sfx containing smv.exe and SVF_Batch_Extractor.cmd My SVF Batch Extractor.bat on the other hand simply includes the smv.exe utility ascii-encoded inside the script itself. "a more true to it's name" as being actually a batch file If the former one had any purpose, then there is a purpose for my variant too Btw, you've quoted the older link. Changed to force current directory in case it's run as admin (not needed, but still)
Oh boy, are truely that egocentric or just trolling . YOU DO NOT LIKE ANY TOOL BESIDES THE ONES YOU CREATED YOURSELF, WE GOT IT NOW! The 'Extractor' part in my solution is an neccessary thing to join all files after downloading. Can your solution offer the whole SVF library (not to mention it would need @Enthousiast's permission) for all the supported builds?
How did I manage to ruffle your feathers now?! You and Enthusiast must be brothers, always taking everything I write like a personal attack or affront. Cheer up FFS! So: I was not even aware of that Batch_Extract_370_x86.rar, I just chimed in as response to 3zero3 doing that sfx that Enthusiast mentioned it had issues cleaning up. I obviously find it useful to do the job quickly from a single file instead of needing to unpack a rar of the tool + batch file, and I'm generally against spammed exe's (sue me!) Then had a laugh at the "name dilemma" post by 3zero3 and instantly come up with the idea to pack the tool in the batch script itself hence the "more true to it's name". At what point was anything about threatening (because you do seem to feel that) your tools or Enthusiast's hosting or whatever?! As for the "My" that was purely semantic. The batch file is not even "branded". And btw, you don't hold any copyright on the smv.exe tool itself, or the launch options used for that matter. Can it be used with pretty much any .svf + source, yes or not? We are also on a discussion forum where ideas, suggestions and alternative solutions, good or bad, should be encouraged, because in the end progress benefits all of us. I won't tell you that if you don't like that to try a blog or something, instead I'm gonna try to stay outside your bubble. Peace.
To many post, to many links, but i cant find the treasure XD i am looking for: W10 enterprise LTSC 2019 es-mx (or es-es) X 64 iso can someone help me?
At the OP you can find an index of most repositories, when you click on 17763, you end up here: https://forums.mydigitallife.net/threads/windows-10-svf-repository.63324/page-128#post-1468363 @s1ave77 his TB/MVS/SVF iso download tool offers them too: https://forums.mydigitallife.net/th...3-ltsb-2016-2015-server-2016-techbench.77028/
@Enthousiast, I have a question about "Enterprise 2019 LTSC (17763.1 aka 1809) SVF Repo" on page 128. What means 370 x86 of Patch?
@austin_5118 what iso do you have downloaded? Code: 17763.1.180914-1434.rs5_release_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us_to_en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958.svf 17763.1.180914-1434.rs5_release_CLIENT_LTSC_EVAL_X64FRE_EN-US_to_en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958.svf en_windows_10_consumer_edition_version_1809_updated_sept_2018_x64_dvd_5c2f3f9a_to_en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958.svf en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_4c97c86c_to_en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958.svf
en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958.iso But wait, to backtrack a bit, I'm not exactly sure what SVF's really are. If I'm content with the ISO I have, and don't plan on changing OS's, then do I need an SVF? Is it just for changing ISO type, or do you need them for something else as well to make your targeted ISO work properly
use a great tool that i've just discovered here to get your windows 10 edition easily, it's called SMRT SVF iso converter => https://forums.mydigitallife.net/th...3-ltsb-2016-2015-server-2016-techbench.77028/