Sorry, I am out of ideas. Normally just disconnecting and reconnecting works because you have to verify to reconnect and then it's done.
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.