Last week's Windows 10 Insider Preview in the Fast ring was build 19592, and as it turns out, there won't be a new build this week due to a flight-blocking bug. Moreover, it turns out that last week's build is a fair bit buggier than was initially thought. Four more known issues have been added to the list
Here's the list:
- We’re investigating reports that app icons in the taskbar are having rendering issues, including defaulting to the .exe icon.
- We’re investigating reports that the battery icon on the lock screen always shows close to empty, regardless of actual battery levels.
- We’re looking into reports of IIS configuration being set to default after taking a new build. You will need to back up your IIS configuration and restore it after the new build is installed successfully.
- We’re working on a fix for an issue causing webcams to not function correctly when attempting to make a video call in Microsoft Teams. The webcam should be unaffected when using Microsoft Teams via the browser.
Some of these issues seem somewhat significant, depending on what you depend on your PC for. The good news is that there should be a new build next week, but the bad news is that once you're on the Fast ring, you're pretty much stuck there unless you do a factory reset.
This is because the Fast ring is no longer tied to a development branch. It used to be that the Fast and Slow rings were the same development branch, so if you got tired of the instability of the Fast ring, you could switch to Slow. There was also a "magic window" period where the Fast ring aligned with the RTM build, allowing you to switch your PC to production.
That's not the case anymore, as the Fast ring is just the development branch. That means that your machine is always ahead of the curve, and it's never going to line up with a production version of Windows, or even the Slow ring. It also means that as you accept more builds, some will be more stable than others, and there may be deal-breaking bugs that you have no choice but to deal with.