Today, we are releasing Build 14251 Windows Insiders in the Fast ring.
Sharp-eyed Insiders likely noted the big jump in build numbers from our last preview build (11102). Historically, the codebase for mobile had a different OS version than the codebase for PC because they were developed by different teams on different schedules. With Windows 10, we became one Windows team and brought these two codebases together. We started by changing the version string displayed in the UI to be consistent, which is why you saw similarly labeled builds over the past year for both Mobile and PC, but the underlying binary version numbers were still different. As part of our work getting the common codebase ready for the next release, we decided to complete that work and sync the build numbers between mobile and PC. Because the mobile codebase used higher build numbers than PC, we needed to jump ahead a bunch of build numbers to ensure updates to future builds will continue to work. So that’s why build numbers went from 11105, 11106, and 11107 to 14251.
This build doesn’t have notable new features in it but I encourage you to check out the new Cortana improvements we released to Insiders earlier this week. TheJanuary update to the Xbox Beta app for Windows 10 is also now available with some really nice improvements for Insiders to try out and give us feedback.
This build does contain some really good bug fixes that Insiders will appreciate:
- We fixed the issue where some PC games would crash switching from windowed mode to full screen, upon game resolution change, or upon launch due to a bug in Windows graphics stack. So play your games! If you run into any issues – please let us know by reporting in the Feedback app and include the game title.
- We fixed the issue where applications such as Narrator, Magnifier, and third-party assistive technologies may experience intermittent issues or crashes.
- We fixed an issue where File Explorer would crash frequently when DPI settings were at 175%.
I also want to reiterate once again that with the change to release builds faster to Windows Insiders in the Fast ring, bugs like the ones we had in the last build (or the File Explorer copy UX from the prior build) are going to pop up. Sometimes it might be several builds before we get these bugs fixed. And there might be times where a build we release contains bugs we haven’t found in internal testing as well.
We’re at the beginning of a new development cycle for our next feature update to Windows 10, and that means teams will be checking in lots of new code as they integrate their feature payloads. Being an Insider means you’re getting the latest code changes, and working with new builds that are relatively new even for Microsoft employees. If this worries you, you can switch to the Slow ring and stick with less frequent but more stable builds.
- You might see a WSClient.dll error dialog after logging in. We’re working on a fix for this but as a workaround, you can run the following in Command Prompt with administrative rights: schtasks /delete /TN “MicrosoftWindowsWSWSRefreshBannedAppsListTask” /F
- The Connect button does not show up in Action Center. The workaround is to press Windows key + P and then click “Connect to a wireless display”.
- Due to a recent memory management change, you may see periodic app crashes or other memory related app errors. The workaround is to reboot your PC.
Source.. Windows Blog.If you like our report please share your support by subscribing to our community on Facebook, Twitter, Telegram or Flipboard. you can also join our support group Smartphone Assistant for any queries related to your devices