This is not true, these ESD files are same. You just need to install the proper version of Windows 10.
I made an iso of the esd, did a bootable usb of the iso. Run the setup file on the usb in windows 7 and updated and checked that it was activated. Used the same usb for a clean install, and still activated.
@dosibox cmd (admin) wuauclt.exe /updatenow I understand it started the upgrade, Can you confirm that?
Has everyone that received the ESD through $Windows.~BT and converted to ISO matched SHA1 of known releases?
Instead of comparing SHA1 of the ISO files, we should compare the hash of ESD files, because there might a timestamp (or some specific information) inside the iso that we created.
My Windows 8 Home x86 esd (windows update July 28th downloaded) converted to ISO SHA1 is : 349E52B5F1F2B4Fb852589963E4143A61F8B01E8
it most likely wont as it will include all updates to date, thats why the build no is 10.0.10240.16384
I mentioned that in my earlier post. here's all the info: ead103b4ec907a8668cbdac34f426a0b6ea386af *\$Windows.~BT\Sources\Install.esd d12ada208cc78bf0b5a76498c43ed9df420e84cf *en_windows_10_pro_10240_x64_dvd.iso (aboddi esd -> iso)
Ok, now that i've downloaded that BT folder, it has nearly 6.4Gb, when does it starts installing it? Cuz I already had 3 beers while waiting.. and for some reason i get failed to install updates in windows update. I also have a legit W8.1 client.
Can you define homebrew in this context? Also, why is that true? Aren't all Install.esd the same (for build)?