Microsoft has just announced the release of Windows 10 Insider build 19628 for Insiders in the Fast Ring. Once again, this is a small update with a single fix and a minor new feature. We invite you to check out the full list of changes, including a couple of known issues below:
General changes & improvements
- We’re adding initial support for DNS over HTTPS, so that you can opt into using encryption when Windows makes DNS queries. Follow the instructions in this blog post to opt in as it will be off by default.
Fixes
- We’ve fixed an issue causing some devices fail to update with error code 0xc0000409. If you continue to experience this error, please let us know by filing new feedback in Feedback Hub.
Known issues
- We’re aware Narrator and NVDA users that seek the latest release of Microsoft Edge based on Chromium may experience some difficulty when navigating and reading certain web content. Narrator, NVDA and the Edge teams are aware of these issues. Users of legacy Microsoft Edge will not be affected. NVAccess has released a NVDA 2019.3 that resolves the known issue with Edge.
- We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.
- We’re working on fixing an issue for a future Insider Preview build where in Settings > Privacy the Documents and Downloads sections show a broken icon next to their page name (just a rectangle).
- 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 looking into reports that taskbar preview thumbnails aren’t rendering consistently (showing a blank area).
Another thing to note about this new Fast Ring build is that it’s coming from the new “MN_RELEASE” development branch. According to the team, this is just a temporary change and the “RS_PRERELEASE” branch will be used again to ship new builds to Fast Ring Insiders. “As our engineers work in development cycles internally, we may prioritize work being done in a specific branch and may need to move Insiders between branches,” the team said today. We’ll see how it goes, but builds coming from the “MN_RELEASE” branch are still not tied to a specific release, in that case 20H2.