I doubt it so soon as you say, even the partners haven't received nothing new, and this despite Gabe has said that there were still some build to release.
sounds like they havent release anything do to the cause of surface 3 error.....and thats MS bread and butter machine looks like their trying to get it fix.
If it's something that serious then it's a show-stopping bug that would affect more than their Surface devices. When they've mentioned show-stopping bugs before, people freaked. When those same people who freaked demanded it be released anyway, we got 10130 that had a serious bug that killed all sound and still had the explorer.exe crash on shutdown/restart. This is why they aren't soo fast to release anything right now until that new build that includes the fix, to whatever the bug is, is done and tested. @orlaf You really don't have much room to be talking about others who are complaining about no new builds. You made a post that was nothing more than the word "blah" repeated over and over because you were annoyed. Very immature, yet you're trying to point out immature behavior by others?
Edit: They have released more than a bugged build, and now they are carried away by the concern to leave one decent. Chris123NT was right, all their actions are all a ploy to not lose face in front of dozens of angry users.
Microsoft will not release a build with same or more bugs as the last because, it would look bad and spread panic and bad news all over the web, they would not want this bad rep so near to the RTM date of 29th July.
Looks like firefox release a new update that fixed the glitching title bar. That was a different shade of grey.
New Windows 10 mobile build 10136 is out now and ready for download. It came out 10:37 tonight so maybe we will get a new build also.
I guess, we won't see any new PC build this week. Reason: They'd sent 4 builds into OSG ring, but didn't release one to Insiders. They might have some major bug(s) in their way. BTW, Windows Mobile build was released yesterday.
Nobody on mobile build 10080 will receive the 10136 build. There is apparently a migration bug so Microsoft disabled the upgrade path. To use build 10136, you first have to put Windows Phone 8.1 back onto the device then do an update to 10136 after resetting up Windows Insider etc. There will be a future update for 10080 (supposedly), which likely means a new build entirely. This could be in a few days, or a couple of weeks... For desktop Windows, it's probably a combination of major bugs and getting it right. They're at the point where they can't have any major bugs in new builds, since it's this close to the release date. Also technically it should be a proper release candidate, not what people have been calling a release candidate. A release candidate should, by definition, be a candidate for release. This means relatively bug free, and no other changes unless it is deemed absolutely necessary to do so. Also, these changes shouldn't have been planned to add in later, they need to be a result of the ongoing findings. Apparently they're still doing changes to it, so 10130 isn't a release candidate, and it's possible that the next released build isn't either (although it would probably be close to being one). Seeing as there are some obvious bugs introduced between 10130 and 10135, it seems Microsoft are really pushing themselves to have it ready on time. Remember this release is different to previous Windows releases. With previous releases, even though it was ready on (example) 29 July, the public didn't get it until a couple of months later. This gave a grace period to fix up any bugs before it's widespread adoption. However, come 29 July, people will be updating old, messy, haggard Windows 7 systems to Windows 10 en masse. They really can't risk bricking these systems. Also, people are mindful of this so the updates close to the release date need to be relatively polished. So, in answer to them wanting the next build of Windows to be perceptively excellent, the answer is, 'absolutely'. It's probably why there have been so many potential builds that haven't actually been released. It would be bad if they release a build as bad as 10135 at this late stage, and it would be even worse if they made a build as bad as 10080 was for mobiles. Windows 10 builds on phones have always been slower that Windows 8.1, but build 10080 is painfully slow and can take a long time to even show the start screen. This was a step 'up' from the previous build where the alarm didn't work, or didn't go off properly on schedule, and when it did go off you couldn't turn off the snooze function no matter what you did with the alarm (only option was to turn the phone off and on again). The frequent crashes in very program was obviously annoying too. So, at least they had the sense to delay the mobile Windows a little, although going by the progress of it so far even September may be a bit of a push. I think there's one thing that is obvious though, everyone is handing out for a new build! Build 10150 hopefully, it is yet another release with what seems to be a full suite of x86 and x64 builds in different languages.
If we don't get a build today ( Thursday ), we will wait next week for a new build. If they release a build it possibly will be 10146