This evening, Microsoft released Windows 10 Insider Preview build 14931 for PC to the Fast ring. So fire up Windows Update, it’s time to get busy.
As you may recall, Microsoft last shipped a Windows 10 Insider Preview build exactly a week ago, when delivered build 14926. That build included a few new features, such as Edge “Snooze,” an updated Wi-Fi settings page in Mobile, and more. This build, besides being limited to just PC, doesn’t have any new features, Microsoft says. But it does come with a few notable app updates:
Maps. The Maps app finally supports both light and dark modes like a big boy app. But the bigger news, perhaps, is that Maps has new traffic condition tracking for your home and work locations.
Send and receive SMS messages. The Skype Preview app has been updated to support SMS Relay, as I reported previously. So you can now send and receive SMS text messages from your Windows 10 PC when Skype Preview is set as your default Messaging app in Windows 10 Mobile.
Feedback Hub. The Feedback Hub has been updated with dark mode support and other new features.
USB Audio 2.0 support. Windows 10 now includes a so-called in-box class driver for USB Audio 2.0, at least in unfinished, pre-release form. This first version supports playback/render only, but future versions will add recording/capture and more.
Various fixes. Build 14931 fixes a few minor issues with the previous build, the most notable of which is a black screen that would appear on sign-out and prevent the user from signing in again.s
Known issues. As with most Windows Insider builds, this build comes with a few known issues, none of which look too serious to me. Check out the Microsoft blog post for more information.
As noted above, this build is for PC only, but that’s because the previous build apparently caused some issues. “After upgrading to Build 14926, some Insiders reported that the pin pad is no longer visible to unlock their phone even after rebooting the phone and some phones lost the ability to use their SIM card,” Microsoft’s Dona Sarkar explains. “In both cases, a hard reset of resolves the issue. Based on the feedback we received from Insiders, we have decided not to release a new Mobile build this week until we get fixes for these two issues.”