No, nothing wrong or severe error, it's just a messege from wimlib-imagex whlie integrating tokens you can safely ignore it
Thank you abbodi1406 for creating the script and providing the files. Which scenarios I can use coresinglelanguage isos? It can be activated using kms host? It can be activated using the known tools? It can be activated using a modded bios? Thanks!
Those ISOs are meant for so called emerging markets (whatever this means) and should prevent them being reselled ... so kinda protection . KMS and OEM_DM Keys to activate, unfortunately modded BIOS makes no sense as these OEM_DM Keys are unique for each machine and cannot be shared without them being blacklisted soon.
In OEM machines (e.g. HP or Lenovo) Yes to your two questions. s1ave77 answer the third question above this post.
I found this method of creating a bootable ISO from ESD some where, dose it work and is it reliable? Open an iso Windows 8 bootable DVD image delete the install.wim add the install.esd save as
Thanks for that, but I'm stuck straight away. When I start ESD Decryption it just says "Incorrect usage or file name", its the GB files I want to decrypt. Is there a guide to accompany the tool?
2. Extract the 7z contents to a folder with proper path (e.g. C:\ESD). 3. Copy/Move the downloaded ESD file to the same folder. 4. Open Command Prompt as administrator in the same current folder (or Run CMD as administrator then change location to the used above directory). 5. Execute: Code: decrypt ESDfilename.esd example: Code: decrypt x86fre_coresinglelanguage_en-us.esd
Great, thanks. One last question, sorry to be a pain but I'm sure it will be useful to the other clots like me looking in. I can see 4 options, option 4 appears to be a bog standard installation DVD, is this the best option to go for?
Save for the polka and incest, it never hurts to try something new. I did receive a warning about 22543 streams having an incorrect reference count. Because I'm an inherently lazy -------, I renamed "SuperLong_ESD_Filename.ESD" to "test.ESD", so I'm pretty sure that was the cause of the warning. Everything else went well. Used Rufus to put the ISO on a flash drive. Installed and ran perfectly, even with secure boot enabled.