Microsoft releases Windows 10 build 20170 to the Dev channel with improved sound settings

It's Wednesday, and that means that there's a new Windows 10 Insider Preview build in the Dev channel. Building on top of the massive feature-dump from two weeks ago, build 20170 has a one more. There was no new build last week.

This build just brings over more audio settings from the Control Panel, bringing them over into the Settings app. Here's the full changelog:

Improving your Sound Settings experience

Last week we mentioned we were planning on bringing more Control Panel capabilities forward into Settings, and here’s another one – we’re updating Settings > System > Sound > Manage sound devices to now let you know which device is default, and if not, enable you to set it as your default device or default communication device.

We’ve also updated the volume mixer to include a link to the per app audio settings, which you can use to redirect audio endpoints per app.

There is more work on the way in this area – stay tuned!

There are also a few miscellaneous changes and improvements:

As part of our ongoing efforts to update the iconography across Windows, Insiders will notice we’re introducing a new Settings icon in this build. The new Settings icon looks great on the Start menu with the theme-aware tiles introduced in Build 20161!

While we work on improving reliability, we’re temporarily turning off Notepad’s ability to persist open windows across restarts and updates.

An experimental implementation of Transport Layer Security (TLS) 1.3 is enabled by default starting with Insider Preview Build 20170. IIS/HTTP.SYS have TLS 1.3 enabled by default. SSPI callers can use TLS 1.3 by passing the new crypto-agile SCH_CREDENTIALS structure when calling AcquireCredentialsHanlde. SSPI callers using TLS 1.3 need to make sure their code correctly handles SEC_I_RENEGOTIATE.

That's about it for this build. It comes from the Iron development branch, although this build isn't tied to 21H1 specifically. That means that new features that you see now might not arrive in next spring's update, and might not arrive at all. This is the nature of the Dev channel, and being in a perpetual state of prerelease builds from the active development branch.

If you've got a PC with an AMD processor, it's worth noting that you'll have to skip this build, thanks to a bug.