They make the appropriate versions public via the media creation tool. It does basically the same thing that downloading an esd here and decrypting it via the decryption script does.
If SFC /SCANNOW passes ok, does this mean Windows is ok to use regardless of esd file hash difference?
sfc /scannow has nothing to do with the authentic of the iso itself. It only tries to repair nonfunctional files if there are any
I think that is why the plan is to do it in waves..give it to a few tomorrow and then see what kind of problems develop. It might be awhile before the second wave starts and then everybody will be back here to get the ISOS and do it themselves anyway.
You sure you didn't hash it *AFTER* you decrypted it with the tool? decrypting it changes the contents.
Is there any way to backup and restore W10 activation successfully? Im thinking upgrade w8.1 -> get activated -> backup activation -> clean install (really need this, my partitions and stuff are really messed up) -> restore activation Or any other way to achieve the same result?
I used it when I was downgrading back to the legal OSes my machines came with before upgrading to w10. It makes ISOs that are both OEM and Retail combined which made it easy for me as some were OEM and others were retail Pro.
We don't know how to backup online activation since win8.1 (maybe sooner? not sure) We can back up phone activation, but not online activation.
Yep. And since we are all be legal - we'll all be able to take off our iso when we need. This system (Windows as a Service) is more and more similar like android to me... Probably the next version will be called Windows Lollipop
You can skip backing up the activation, there should be no need... just make sure that after you upgrade windows 8.1 to Windows 10 the first time that it gets activated... at this point, microsoft will start recognizing your PC from the HWID. After that, install from ISO, do a reset, whatever you want to do. Don't enter a product key when you install from ISO on a clean install and once the computer connects to the internet, it will activate by itself using your HWID. You can always backup your activation if you want to be completely safe though. But it should not be necessary.
So how tomorrow the build will be 10240.16405.150725-1815.th1 ? I installed KB3074683, but only the UBR is 16405.
Still as stated in this thread what about pre-install OEM systems that have a key in the bios what changes are made to that if a key is no longer needed for activation & its base on hardware id if a user does a upgrade on a system like that they get a activated windows 10 (ok) they then choose to do a clean install & again it activates (ok) But what if the user wishes to return to their previous OS is the key that is store in the bios now block & it fails activation-Even if the user restores to the system built in recovery partition because the M$ server deems the system to be a windows 10 machine As Anyone who as such system upgraded yet I know user are given 30days to try win 10 But if you can`t return YOUR system to how you want it then this so unfair I know some will say why go back but their could be lots of reason compatibility issues dislike layout NO CONTROL OVER WINDOWS UPDATES as this M$ a licence to release un-tested update & patches to mess user system up so you spend more time working out which update cause the error M$ haven't taken any notice of all their insider its bug after bug
I'm pretty sure they're one and the same. I believe ms rushed the update through to fix the previous buggy 4681. I've tested it and it supersedes the previous ones: 74, 79, 80, and 81.