The 10011 versioning is an internal screwup on the build server for the TH1 lab. It happened with fbl_impressive in early 100xx builds too, and can be seen with things like Windows Media player to this day. It's probably going to be fixed for RTM, unless MS has a reason for doing this on purpose. As for the ISO vs ESD thing, not 100% sure about that, i was told it was original, but even if it's a converted image, the contents of it are legit.
Maybe, but that could've easily been a 100kb WU patch that didn't require MS to wait until next Wednesday, and having to compile several new builds (if these binaries were RTM binaries labeled incorrectly). Nah I'm sure this build was messed up for several reasons. Not to mention however it got leaked. Super old binaries don't just pop up out of nowhere in MS's builds lol.
BUT binaries like cmd.exe are old even compared to newest Insider versions (MS obviously has newer ones internally). Broken frankenbuild. TBH I thought Insiders were getting RTM - to test it so MS can do day 1 patches and touch up for Final on the 29th. MS can disable KMS/OEM activation and timebomb it, like all the other Insider builds..
TBH I thought Insiders were getting RTM - to test it so MS can do day 1 patches and touch up for Final on the 29th. The Final is not released until about 2 months after Jul 29 RTM
Dude, look at the compile date, the files in 10176 are NEWER, just labeled as 10011 due to a binary versioning issue when the build was compiled. Whoever set the build to compile didn't configure the flags correctly, that's all there is to it. If this was really 10011 binaries, this build would look like 10011.
No, because only some binaries are 10011, whereas others are 10176, and still others are 9600, etc. It's a frankenbuild, either because it was compiled incorrectly, or the leak came without the binaries included and were inserted post-leak. Also the "compile date" just refers to the date it was compiled. It has nothing to do with the VERSION of the file compiled. Obviously it was compiled recently, either by MS before it got leaked, or after it got leaked.
There were also two versions of 176 cut..almost 12 hours apart. Maybe this was the first and the second was to fix all the screwed up modules that still said 10011
Were they both leaked? Weird. Also I'm fairly convinced that those ARE 10011 modules, not incorrectly labeled binaries. If incorrectly-labeled modules were the only problem, then MS would've RTMed this week.
I don't know which were leaked but these were the two that were made and still reside in the RTM branch 10.0.10176.16384 (th1.150705-0552) 10.0.10176.16384 (th1.150705-1526)