Mine still says 4.09 GB, wonder if it already knows I've upgraded, and just sent me clean install software, who knows
Just in case anyone else is in the same predicament as me. here's the deal: running win 7 home, do anytime upgrade, enter generic 7 pro key. accept license agreement. hit upgrade. it will then fail, saying key is bad. restart pc. upgrade will take effect. credit: murphy78, google
ok, so here is why I didn't wait once I knew there was no time bomb in it. There is no official version and there never will be. There was an RTM that the PCs going on sale tomorrow were build from but that is it. MS says W10 will never be done and that is why there is still insiders and test builds that will continue for a long time if now forever. So if you installed with something two weeks ago or tomorrow or a month from now it doesn't matter, it's all the same as long as you keep up on updates. It is also why Gabe Aul kept saying "why does everybody care about RTM, it doesn't matter?". People will be installing something tomorrow that says 16405, mine already says 16405 and may say 16406 before today is over.
They want a billion legal devices with insiders for ever, sounds like science fiction , but that is exactly what happens right now
WU process is designed to go as it was designed without iso in the first place. Later isos might be available but not sure upon because MSDN is the place for specialists to run these on their behalf and even pay for!!
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