As you probably know, we validate builds that we produce
in internal rings where they're used by engineers in OSG and Microsoft.
White noise acts as a tinnitus masker by blocking out outside noise and masking
the internal ringing, buzzing or clicking that tinnitus sufferers experience.
In the current build going through
our internal rings now most of the known issues introduced with Build 10512 as well as many issues that have been reported have been fixed — mobile hotspot functionality now works, Quiet Hours \ Do Not Disturb has been fixed, pinch and zoom in the Maps app now works as expected and the delay in showing the date and time on the Lock screen has been improved.
We spent this week testing on individual devices, as well as providing the builds with this feature to
our internal rings so that we all could test it on our own phones which had been previously not usable.
IMPORTANT: Today, we are pushing a few builds out to into
our internal rings in addition to today's Fast and Slow builds and as a result of that, the builds for PC for the Fast and Slow rings is a little bit behind in rolling out and should be available in the next few hours depending on your region.
But with each blocking issue, we start back through
our internal ring validation with any additional changes that were ready at that time.
I am happy to say this build has progressed through all
our internal rings and now is ready for Windows Insiders.
The good news is that we believe we have fixes for the issues blocking us from flighting a new Windows 10 Insider Preview build, and we're going through
the internal rings now.
IMPORTANT: Today, we have pushed a few builds out to into
our internal rings and as a result of that, this build for PC is a little bit behind in rolling out within the queue to the Fast ring and should be available in the next few hours depending on your region.
We've been loving this build in
our internal rings as it is very fast and smooth, and makes a great daily driver.
However, as new builds with these fixes passed through
our internal rings, we discovered a few issues that we were not comfortable releasing to Windows Insiders until we had fixes for those as well.
We're at the point in the development of Windows 10 where nearly every build is getting out to
our internal rings, and passing the criteria for release to Windows Insiders.
The new criteria will be much closer to our criteria for flighting to
our internal rings, which means more builds will pass it and be released externally to the Fast ring.
«We spent this week testing on individual devices, as well as providing the builds with this feature to
our internal rings so that we all could test it on our own phones which had been previously not usable,» he added.
Once the upgrade is complete, just as we flight the OS through the rings, we will be flighting the service upgrades through
the internal rings first.
As we've reported several times this year, the next major update (Redstone 2) might be focused on mobile devices, so it's not surprising to see some new features already being tested in
the internal rings.
Microsoft is currently analyzing data and feedback from
the Internal rings, before making those builds available in the Insider Rings.
We will begin flighting the latest builds via UUP starting with
our internal rings first then to Insiders based on each ring's promotion criteria.
The criteria we use to release builds to Windows Insiders in the Fast ring will be much closer to our criteria for flighting to
our internal rings.
We believe we have solved the issue and are pushing new builds out through
our internal rings right now to test the solution.
This build number 16212 was pulled shortly after escaped out of
the internal ring, but those of the Insiders who install it on smartphones had completely unusable devices — entering a boot loop.
Windows 10 Mobile 14322 is still being tested in
the internal rings and if everything is fine, we can expect this build to arrive this week.