I have a question, is the Windows 10 Enterprise MDSN version the same as the VL (Eopen) version? My boss doesn't give us access to the new ISO's at work on our Eopen/VLK site so I end up having to go searching for them, looking for an untouched version. Thanks,
At techbench the VL 16299.15 iso is called InsiderPreview_Enterprise iso. At MVS the iso is called Multi-Edition_VL What language ISO do you want?
Hi, So to give you some idea what I really mean. the previous ISO release from MS for 1703 Windows 10 enterprise VL was called SW_DVD5_WIN_ENT_10_1703_64BIT_English_MLF_X21-36478.ISO. I guessing the the 1709 has 1709, I am just not sure that the MLF_X21 # is. Thanks,
Enterprise on VLSC or on MSDN (now both called MyVisualStudio) both are VL and are the same. From now on there is no single index iso anymore, enterprise is now part of the Multi-edition_VL iso. 15063 Enterprise VLSC = SW_DVD5_WIN_ENT_10_1703_64BIT_English_MLF_X21-36478.ISO = MSDN = en_windows_10_enterprise_version_1703_updated_march_2017_x64_dvd_10189290.iso
Well here is something interesting then. I initially downloaded the 1703 MSDN Windows 10 Enterprise and tested on a VM with my VLSC key. It said invalid key. When i eventually found the 1703 ISO from MS's VLSC and installed that it excepted the key no problem. Moving forward with 1709 what do I need to download in order for my VSLC key to work?
There is no VLSC and MSDN anymore, all is MyVisualStudio now. The keys should be accepted by all Enterprise installs, they are 100% exactly the same and all VL.
Ask I said already the 1703 MSDN version didn't accept the VSLC key, so what do you recommend for 1709?
Both ISO's are exactly the same: Code: SW_DVD5_WIN_ENT_10_1703_64BIT_English_MLF_X21-36478.ISO CRC-32: be8e89bb MD4: 4241d6bf2b50348e6ebb11661ddfb6e8 MD5: 0df79911ceff0f8b5cf4e4aeb1bd1039 SHA-1: 77d5e7c91b5dbbee410fb6c57cb944238bf7176a Code: --------------------------- Checksum information --------------------------- Name: en_windows_10_enterprise_version_1703_updated_march_2017_x64_dvd_10189290.iso Size: 4247986176 bytes (4051 MB) CRC32: BE8E89BB CRC64: 51DC95418525E5E4 SHA256: 466C1CD1E7B9BCF3B984D5A41E24500D4945C0B71B2B6B446D68D26A9C0F2320 SHA1: 77D5E7C91B5DBBEE410FB6C57CB944238BF7176A BLAKE2sp: BB211BE1E88EF3E16FE84A369089F2AC7B527D182B74C1EBDF92BF024AF0C487 --------------------------- OK --------------------------- Code: --------------------------- Checksum information --------------------------- Name: Windows10_InsiderPreview_EnterpriseVL_x64_en-us_15063.iso Size: 4247986176 bytes (4051 MB) CRC32: BE8E89BB CRC64: 51DC95418525E5E4 SHA256: 466C1CD1E7B9BCF3B984D5A41E24500D4945C0B71B2B6B446D68D26A9C0F2320 SHA1: 77D5E7C91B5DBBEE410FB6C57CB944238BF7176A BLAKE2sp: BB211BE1E88EF3E16FE84A369089F2AC7B527D182B74C1EBDF92BF024AF0C487 --------------------------- OK --------------------------- So all will take the same VL key.
Are there any 1709's yet? I just downloaded an ISO from a torrent that has Windows 10 Pro, Ent, Home and Education in non-N and N for 1709. Tried the Ent non-N and it refused to accept my VSLC key.
Just grabbed Windows 10 Insider Preview (build 17025) -> Windows 10 (All Volume edition) Insider Preview - Build 17025 -> English -> x64 and installed it on my Esxi 6.5. Tried my VLSC key and it fails. Tells me it's not a valid key. To confirm the key isn't botched I install the VLSC ISO for 1703 and applied the key, and it accepted it. I know the ISO's might look the same but I suspect MS must be changing something within them otherwise this key would work. lol Downloaded the Insider Preview from TechBench (link from here)
Searching MS Technet forums I need to find the "Windows 10 (multi-edition) Version 1709 VL" ISO. There is a lot of talk about the VLSC version, I have use the VL if I use anything else it won't work. After looking on TechBench and not seeing any VL copies of Windows 10 1709 I thought I would try a insider preview which didn't work. Yes my key works on all versions of Windows 10 VLSC.
Regarding adguard's techbench when i select only microsoft word for office 2016 the size is identical with the full package !! how is that even possible