okay so i am on a fake 1909 version and not the legit on that was released yesterday? i don't have that kb4517245 installed cant see it in my update history i added watermark in regedit!
This is a thread, specifically meant for Windows Install Media downloads. Might be better to ask this in the appropriate thread, 1809, 1903/9 or other build thread.
You can also simply use DISM and convert Pro to Ent. convert the esd to wim, mount, convert, save then convert back to esd...
@fbcjhgfr source iso: Code: en_windows_10_multiple_editions_version_1607_updated_jul_2016_x64_dvd_9058187.iso en_windows_10_multiple_editions_version_1607_updated_jul_2016_x86_dvd_9053863.iso
Ok, I'm trying to obtain/create a clean copy of Windows 10 Enterprise 1909 VLSC (which can be activated against a KMS server). I've read through several methods and I've created several copies, but I'm not sure which of these methods is preferable or if any has even created what I want. I'm hoping someone who is an expert with the methods discussed in this thread can read through my process and point me in the right direction. I think you'll see I did my due diligence with investigating and implementing the methods, I'm just not entirely sure which is the best/right way to do this. Method 1 I used was using the latest MediaCreationTool. I downloaded it from MS and ran the following: Code: MediaCreationTool1909.exe /Eula Accept /Retail /MediaArch x64 /MediaEdition Enterprise It created an ISO which has the following version inside: Code: C:\Users\bengalih\Desktop\1909>dism /Get-WimInfo /WimFile:y:\sources\install.esd /index:3 Deployment Image Servicing and Management tool Version: 10.0.17134.1 Details for image : y:\sources\install.esd Index : 3 Name : Windows 10 Enterprise Description : Windows 10 Enterprise Size : 14,781,260,269 bytes WIM Bootable : No Architecture : x64 Hal : <undefined> Version : 10.0.18362 ServicePack Build : 418 ServicePack Level : 0 Edition : Enterprise Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 21509 Files : 93935 Created : 10/6/2019 - 9:18:55 PM Modified : 12/3/2019 - 11:21:32 PM Languages : en-US (Default) The operation completed successfully. This looks like a valid Enterprise image, but I was unsure if *all* Enterprise versions are considered VLSC? I was confused because I had to use the /Retail switch with the media creation tool and I'm not looking for "retail", I'm looking for "VLSC". Method 2 Being unsure I looked for another method and found the SVF method and files repositories described here: https://forums.mydigitallife.net/threads/smartversion-tools-scripts.79415/ https://forums.mydigitallife.net/th...ll-media-techbench-mvs-iso-uup-svf-esd.72165/ I downloaded the following files: en_windows_10_consumer_editions_version_1909_x64_dvd_be09950e.iso [en-us] _en_windows_10_business_editions_version_1909_x64_dvd_ada535d0.svf I then ran the SVFtoSFX_370_x86 tool to conver the .svf to an .exe file and then applied that .exe file against the .iso. The resulting file was: en_windows_10_business_editions_version_1909_x64_dvd_ada535d0.iso Looking inside that file I see: Code: C:\Users\bengalih\Desktop\1909>dism /Get-WimInfo /WimFile:y:\sources\install.wim /index:3 Deployment Image Servicing and Management tool Version: 10.0.17134.1 Details for image : y:\sources\install.wim Index : 3 Name : Windows 10 Enterprise Description : Windows 10 Enterprise Size : 14,781,260,269 bytes WIM Bootable : No Architecture : x64 Hal : <undefined> Version : 10.0.18362 ServicePack Build : 418 ServicePack Level : 0 Edition : Enterprise Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 21509 Files : 93935 Created : 10/6/2019 - 9:18:55 PM Modified : 10/6/2019 - 9:35:51 PM Languages : en-US (Default) The operation completed successfully. This looks like the same valid Enterprise image, but I am still unsure exactly what *MVS* images are. I've seen some quotes on MDL that say MVS=VLSC, but are they really the same thing? What does MVS stand for? Method 3 Lastly I used the ESD method described here: https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/page-77#post-1380516 I downloaded the following: 18363.418.191007-0143.19h2_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_en-us.esd Then I converted it using decrypt.cmd to create a new ISO with the Enterprise WIM. The resulting image is as follows: Code: C:\Users\bengalih\Desktop\1909>dism /Get-WimInfo /WimFile:y:\sources\install.wim /index:1 Deployment Image Servicing and Management tool Version: 10.0.17134.1 Details for image : y:\sources\install.wim Index : 1 Name : Windows 10 Enterprise Description : Windows 10 Enterprise Size : 14,781,260,269 bytes WIM Bootable : No Architecture : x64 Hal : <undefined> Version : 10.0.18362 ServicePack Build : 418 ServicePack Level : 0 Edition : Enterprise Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 21509 Files : 93935 Created : 10/6/2019 - 9:18:55 PM Modified : 10/6/2019 - 10:32:57 PM Languages : en-US (Default) The operation completed successfully. Again, this looks like the *same* valid Enterprise image: Version : 10.0.18362 ServicePack Build : 418 I'm confused here because the ESD file I downloaded stated it was 18363.418. So how can one tell what is actually in these images? From the best I can tell from the DISM commands these are all the same Enterprise installs. I can assume that at least one of them will be a proper VLSC/KMS install (again, is there any other type of Enterprise install)? But, I don't really understand the discrepancies between methods. Method 1 (MediaCreationTool) seemed the easiest to do, and if you can create it that way, I'm unsure why I should use the other methods? While I wait for an answer I might try to install each one in a VM and see if I can at least determine if they work and if I can spot a difference. TIA
https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-282#post-1551877 Content of MVS ISOs: https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-310#post-1554274 Content of ESD: https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/page-127#post-1555556