Whats your problem. Just because you don't get a new build today you are going to act like a 2 year old. Grow up and get a life baby
Probably isn't even part of the Insider Programme. The whole point of the programme is for the betterment of the OS achieved through the feedback provided by the people who interested in helping to accomplish this. It's the reason why I am a little insistent that only genuine users of the programme should be using these builds, at least as a genuine user of the programme you accept responsibility for any issues arising from its use. Furthermore, at least any issues, whether technological, aesthetic, or interaction, can be reported upon and resolved. If you're just using it for sh!t$ and giggles, then please don't hesitate in going back to 10586 (aimed at the initiator not the respondents). Microsoft was delaying the release with good reason, isn't it pretty stupid to demand a build that is known to have a serious showstopper bug in it? Even with the bug fixed they need to test the new build to ensure it is at least 'generally safe' for testing by insiders. This of course does not mean there aren't serious bugs still present, and if you're not happy with that prospect then you shouldn't be using these builds regardless of any poor excuse as to why you think it is your right to.
I think, at least in my mind, I was expecting more builds with more bugs and it would be up to us to decide the danger level in the Fast Ring as to whether we could handle it or not. And who even knows what the PCI bug is/was anyway? I'd prefer access to more builds with the known issues clearly stated and then I can decide whether to accept the risk or not. At this point these builds are coming out so slowly the cadence resembles the fast ring before they "upped" the frequency. I think that's where some of this frustration is coming from.
so you're saying the builds are either BSOD every 5 minutes or close to perfect? please I think you're making a very simplistic explanation of these builds. This build in particular was tested for what, 2 to 3 days at LEAST before the issue was spotted? It wouldn't have been a "good candidate" as Gabe said early on if it BSODd like you are implying. There's a large spectrum of build quality and my point is that, aside from fatal flaws, let us decide what risk we're willing to accept. If MS feels that the feedback is not valuable then pass on it but we're running a build from 4/2/16. In the 18+ days since then there hasn't been a single build that doesn't BSOD every 5 minutes? I hope that's not the case because the Anniversary Update will be the 2017 update instead of the 2016.
2/3 in 5 files I attempt to download on this build give me some garbage error about the signature missing or invalid.. Sometimes I can download the file & run buuut a few times even that hasn't worked >.< Is it a well known bug ?