Yes, I've reclassified these builds as high for the time being because though someone else reported them as low, I'm not seeing it now I'm using the latest copy of our detection application. Previously, there was a bug where it some times fetched the high builds when you requested the low or medium builds, which might be how these errors have crept in. There's definitely a tonne of medium builds that haven't been marked as such on BuildFeed though. I'm going to get a review going of the flight levels for builds already on BuildFeed so we can say definitively what builds are where.
OK, so now I've had a chance to discuss things with other contributors to BuildFeed, it looks like the bug in our tooling was relatively minor and didn't make any difference to the content on BuildFeed. Instead, there's a rather curious issue. If you set it your priority to Low, you will not find any builds - even going through each lab in the PC Settings and trying to get a build will turn up no builds available. However, some builds do still get pushed to the Windows Update datastore. Why this is, we're not sure, and it leaves us unsure how to classify these builds. They're not getting offered on the client side to Low flight level users, but they are still getting revealed to them. One such build was the now-infamous 9880.winmain. I've decided that BuildFeed will classify them as the level they explicitly appear in - so 9880.winmain is high, but that we'll make a note if data about the build is being leaked to another flight level in the Source Details field. Hope that clears things up.
Lets clear out the confusions qad's tool is meant for only decrypt the ESD, nothing else. abbodi1406's tool is based on qad's tool & wimlib/DISM to create ISO with ESD(decrypted)/WIM inside. wimlib doesn't support decrypting (encrypted) ESDs. 1. Microsoft always delivers encrypted ESDs, so abbodi1406's tool is the perfect solution. 2. While converting the ESD to WIM, some parts are always random. As Microsoft doesn't publish any 'official' ISO for the later builds so it is impossible to 'match' the hashes.