you are part of VLSC or MSDN, something like that? Only way to get a legit 8.1 VL. Maybe you are confusing the term for VL or the word Legit? or do you mean the hardware itself is legit?
PC's have 7 Home Premium and 8.1 Core/Bing ... Did a pirated VL install on all of them cause I found that to be the easiest way
yes, but I'd recommend going to microsoft.com/genuine/validate and make sure it passes test. Then during upgrade, make sure your internet is enabled so it can communicate with the activation server.
Does this tool only download the MURICA version? EN-US? Because it's what the URL and files seem to indicate. Or does it download other language versions? Like the same Windows language version already installed on the PC. I don't want it downloading the Yankeestan version and then using a language pack. It's not the same thing.
They have different language versions. Change the langcode in the url for yours. ex: replace en-us with ru-ru or whatever.
Why the hell when i download 2 times the same Win10 Home Edition with the same Arch x64 and same language but i end up 2 different .ESD checksum? Media Creation Tool do have internal checksum to verify download, but what makes it different everytime?
the time it was created for one. every split second will change it, decryption of the esd changes the esd as well.
I was thinking the same thing today. Might be more in the making, or maybe just keys change pro to pro vl. unsure yet.
Dunno. I read that they're updating vlsc on aug1. If they move the vl versions to that it's going to be even more of a pain in the ass.
I was thinking that before MS put LTSB on MSDN. I really thought that LTSB would be on VLSC only. So, Im confused at their decision process atm lol
I honestly hope they just did away with Pro VL and Pro N VL. Pro N VL is the bane of my damn existence.
I'm not sure if it is an issue with the x86/x64 (both) ISO from the Media tool but adding ei.cfg to both 'x86/sources' and 'x64/sources' paths doesn't allow me to see an index list of versions. Not sure if this is because of the dual architecture ISO or the fact that it may be detecting my computer came with Windows 8.1 Pro initially and is pulling the OEM key.