Are these the files you have in the folder? en_windows_10_consumer_edition_version_1809_updated_sept_2018_x64_dvd_491ea967.iso [en-gb]_en_windows_10_enterprise_ltsc_2019_x64_dvd_fc837a0b.exe
It actually did something just there. Ran for about 3 seconds. Iso is the same size now though. Unsure if it's worked.
I appreciate that, but I'd rather not have it installed on a short countdown like that. I'd prefer to get this done right.
Sorry, my bad. You have to convert en_windows_10_consumer_edition_version_1809_updated_sept_2018_x64_dvd_491ea967.iso first, to [en-gb]_en_windows_10_consumer_edition_version_1809_updated_sept_2018_x64_dvd_1ca92afa.iso Download [en-gb]_en_windows_10_consumer_edition_version_1809_updated_sept_2018_x64_dvd_1ca92afa.svf
I actually went another way these past 15 minutes. Got that same initial iso again, but tried the en-us svf instead and it ran first time. Base files: Win10_1809Oct_English_x64.iso [en-us]_en_windows_10_enterprise_ltsc_2019_x64_dvd_be3c8ffb.svf I got this output after the extraction process. en_windows_10_enterprise_ltsc_2019_x64_dvd_be3c8ffb.iso Modified: 31/10/2018 18:58 Size: 3.77GB Am I good to go?
Yes, except you have the [en-us] ISO Sorry this was the first time I tried this in a different language. But if you want the [en-gb] you first have to convert the [en-us] ISO to [en-gb] by downloading [en-gb]_en_windows_10_consumer_edition_version_1809_updated_sept_2018_x64_dvd_1ca92afa.svf
That's not an issue at all. en-us is fine. I have some DVD's turning up tomorrow so just a case of burning the iso, installing then using kms to activate and we're done?
Wow, is this thread real. This should be kept under Plexiglas, as a model. Everything to the point, so exotic. except for this post, of course. The perseverance of op, polite, but not backing off, and the patience and sufficient curiosity of the helpers. I am impressed. I don't post myself, often, because i fear that this king of exchange is from another planet. Not a distraction: I assume that the comment for en_gb could apply to other languages for which files are available under the same file naming conventions.
https://forums.mydigitallife.net/threads/windows-10-svf-repository.63324/page-184#post-1555942 MSFT, from time to time, does a weird thing with the locale code in the iso filenames. To check you can mount the iso or open it with ultraiso or winrar/7zip, etcetc and go to the sources folder, there will be a folder named en-US or en-GB, and so you can see what exact iso you got. Or use the forum search option and run the iso filename, without [en-GB]_ in front and set the search option to whatever127, so it will find a MVS post by him, next you can verify the sha-1 checksum.
In March 2019, Enterprise S (LTSC 1809) was re-released: en_windows_10_enterprise_ltsc_2019_x64_dvd_5795bb03.iso This is so Microsoft Windows 10.0.17763.316 Enterprise LTSC Version 1809 (release in March 2019). And in October, this edition was reissued (updated_oct_2019, Build 17763.805) ?
The re-release is Sep 2018 build 17763.107 en_windows_10_enterprise_ltsc_2019_updated_sept_2018_x64_dvd_be3c8ffb.iso Latest LTSC is Feb 2019 build 17763.316 en_windows_10_enterprise_ltsc_2019_updated_feb_2019_x64_dvd_5795bb03.iso
Thank. I understood. Tell me, was this reissue in February 2019 planned or emergency (unplanned)? And when will the next reissue of Enterprise S (17763 LTSC) come out? (Unless, of course, this is planned in M$).
17763.1, never existed, according to msft But it was the first official first 1809 release, next they had to re-release and it was 17763.107, but no N versions, and they still have to create them by EU enforcement, 17763.316 was the final refresh iso for 2019 LTSC, now containing N again. https://forums.mydigitallife.net/th...b-17763-xxx-pc-rs5.77945/page-51#post-1467631