mmmmmm.. ok thanks for info right now. It's time to begin the installation on a my friend sony vaio notebook..... *EDIT* Installation completed....... thanks for all info boys.
Thanks for confirming this. Not really surprised they were removed, as most consumers probably did even not know what those specific editions were for and might have gotten confused on which Professional edition to choose. I also assume Microsoft removing those from the Consumer ISO means that only the VL ones are available now normally(unless one has the .1 ISO image downloaded).
It doesn't really matter what pro (vl or oemret) you install, the used key is the deciding part wether the install will be oemret or VL. Proper coded KMS solutions will insert the gVLK on OEMRET installs before it runs the KMS activation.
o when the programme goes to create the iso first the program crashes and says its not responding and then i have this: [ INFO ] Creating Source ISO. [ INFO ] Name : en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483 extracting : en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.iso [ INFO ] Checking Source ISO Hash. [ INFO ] Hash : 031ed6acdc47b8f582c781b039f501d83997a1cf [ WARN ] Hash Mismatch [ INFO ] Hash : fa0037b0a222c957e753cbe9c6244379a7be9288 [ INFO ] Creating Source ISO. [ INFO ] Name : en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483 extracting : en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.iso [ INFO ] Checking Source ISO Hash. [ INFO ] Hash : 031ed6acdc47b8f582c781b039f501d83997a1cf [ WARN ] Hash Mismatch [ INFO ] Hash : fa0037b0a222c957e753cbe9c6244379a7be9288
the only antivirus i have is windows defender which i turned off before i ran the program. thre seems to be a hash mismatch between the source iso and the hash it checks it agaisnt.
Is this done in a VM? There are reports about the tool failing that way on x64 VMware guest machines. Else try to make an exclusion for the work folder. EDIT: The wrong hash for en-us source is the same as others got when using VMware.
no this is on a normal windows install. I exluded it from the working directory but i had the same results
Interestingly the wrong hash is the same as i saw in VMware . You can try to open the script in an editor and near the top find: Code: set "smv=files\ISO\smv_%vera%.exe" and change to: Code: set "smv=files\ISO\smv_x86.exe" Delete the downloaded SVF files. Then try again.
Are you on x86 OS? Here it all works fine: Code: 17:34:13 CHECKING MVS PREREQUISITES 17:34:13 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 17:34:13 Language: en-us 17:34:13 ISO Name: en_windows_10_business_edition_version_1803_updated_aug_2018_x64_dvd_5d7e729e 17:34:13 ISO Hash: 2b15efd7926ab9db9181cd7b599452cccc3774de 17:34:13 EVAL Name: 17134.1.180410-1804.rs4_release_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us 17:34:13 EVAL Hash: a4ea45ec1282e85fc84af49acf7a8d649c31ac5c 17:34:13 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 17:34:14 CREATING MVS ISO 17:34:14 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 17:34:14 Language: en-us 17:34:14 ISO Name: en_windows_10_business_edition_version_1803_updated_aug_2018_x64_dvd_5d7e729e 17:34:14 ISO Hash: 2b15efd7926ab9db9181cd7b599452cccc3774de 17:34:14 EVAL Name: 17134.1.180410-1804.rs4_release_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us 17:34:14 EVAL Hash: a4ea45ec1282e85fc84af49acf7a8d649c31ac5c 17:34:14 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 17:34:14 Downloading EVAL ISO... 17:35:38 EVAL ISO exists. 17:35:38 Checking hash... 17:36:04 Check Hash: a4ea45ec1282e85fc84af49acf7a8d649c31ac5c | SUCCESS! 17:36:04 Downloading Target SVF... 17:40:58 Creating en-us Source ISO... 17:41:16 Source ISO exists. 17:41:16 Checking hash... 17:41:47 Check Hash: 2b15efd7926ab9db9181cd7b599452cccc3774de | SUCCESS! 17:41:47 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Would be interesting to know why x64 smv.exe fails for some people. Additionally that it fails with mostly the same wrong file generated. Would like to know why smv_x64.exe generates an incorrect ISO instead of an error message. I usually get conversion errors in such cases.
FYI, I receive the Hash error on LTSB 2016 and W10 1803. Both were fresh installed (64-bit) without any additional software. Just hardware drivers. No Firewall or AV. Windows Defender was disabled during testing.