Sorry if this question is off-topic, but is there any difference between an MVS ISO file and a VLSC ISO file? I am asking since I created ISOs from the SVF files that WZOR published recently.
Refresh LTSC on both is the same: https://forums.mydigitallife.net/th...-17763-1-107-pc-r.77945/page-190#post-1483770 The business iso's i can't test yet, but probably will also be the same.
17763.134 doesn't exist as iso (it's the latest public CU). Either 17763.1 or 17763.107 are available as iso (17763.107 only Techbench Consumer iso on the tool).
Please help me in my confusion: does that imply that the best I can get for a en_windows_10_business_edition_version_1809 ISO image is a 17763.1 build? Thanks a lot!
No, he gets 17763.1 wit the tool, i didn't create the MVS 1809 business refresh iso svf patches, yet. Atm, only Consumer = MVS = Techbench is available in 17763.1 and 17763.107 on the techbench section of the tool.
Just to get this straight, with the GUI tool the MVS ISOs are in the pipeline but the Techbench ISOs are up-to-date [that bit is clear, 1809-2 Oct] but are these ISOs the consumer edition? If they are it will save me the wait.
FYI: Tool is only waiting for last Server 2019 Refresh SVFs to be created and uploaded by @Enthousiast. New version should appear tomorrow if everything goes as planned and feature 1809 Oct Refresh VLSC LTSC, Business and MVS Server 2019 ISO creations.
If someone knows an official permalink to the (eval) standard server 2019 oct. refresh iso, it will be much appreciated when posted here
That's the core business of the tool: download EVAL, download svf and convert the eval to non eval by svf. Code: 19:39:06 CHECKING MVS PREREQUISITES 19:39:06 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:39:06 Language: fr-ca 19:39:06 ISO Name: SW_DVD9_Win_Pro_Ent_Edu_N_10_1809_32-bit_French_Canadian_MLF_X21-96510 19:39:06 ISO Hash: afc0691ab6317239c6085902d7691b8482757a97 19:39:06 EVAL Name: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-us 19:39:06 EVAL Hash: eee2167b0ea9fe9654357c06d44a9c44eff62f1d 19:39:06 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:39:13 CREATING MVS ISO 19:39:13 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:39:13 Language: fr-ca 19:39:13 ISO Name: SW_DVD9_Win_Pro_Ent_Edu_N_10_1809_32-bit_French_Canadian_MLF_X21-96510 19:39:13 ISO Hash: afc0691ab6317239c6085902d7691b8482757a97 19:39:13 EVAL Name: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-us 19:39:13 EVAL Hash: eee2167b0ea9fe9654357c06d44a9c44eff62f1d 19:39:13 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:39:14 Downloading EVAL ISO... 19:40:06 EVAL ISO exists. 19:40:06 Checking hash... 19:40:27 Check Hash: eee2167b0ea9fe9654357c06d44a9c44eff62f1d | SUCCESS! 19:40:27 Downloading Target SVF... 19:40:27 SVF Name: SW_DVD9_Win_Pro_Ent_Edu_N_10_1809_32-bit_French_Canadian_MLF_X21-96510 19:41:09 Creating Target ISO... 19:41:20 Target ISO exists. 19:41:20 Checking hash... 19:41:41 Check Hash: afc0691ab6317239c6085902d7691b8482757a97 | SUCCESS! 19:41:41 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ @s1ave77, minor thingy but MVS should be VLSC? (really nothing important)
It’s just that up until now the EVAL ISO has had to be converted manually. It would appear that this is no longer the case and the conversion is now carried out automatically, if this is correct the process has been greatly improved.