





Hi everyone,

Today, we are releasing Build 14257 Windows Insiders in the Fast ring.

As I mentioned last week, we’re at the beginning of a new development cycle for our next feature update to Windows 10. Teams are still early in their new feature work and changes in this build are mostly about laying the foundation for those features to start coming into builds. So you won’t see many visible changes quite yet. Also, the increased pace of the Fast ring (You’ll note that this build is only 6 revs newer than the last build we sent to the Fast ring) means that there will be fewer big changes between builds as opposed to this time last year when builds were about 30 days apart. There is a ton of coding work going on, but I want to set your expectations on how it will show up for you at our increased Fast ring pace.

We are seeing lots of bug fixes coming in from teams, including some which were reported by Insiders:

The issue of periodic app crashes or other memory related app errors due to a memory management change has been resolved. If you were having issues launching the Git client for Windows, you should now be able to launch it in this build.

The Connect button now shows up again in Action Center.

F12 Developer Tools will now load correctly Microsoft Edge.

We fixed an issue where suggested apps were being shown on the Start menu even though “Occasionally show suggestions in Start” was turned off under Settings > Personalization > Start.

We fixed an issue where if you try to change the Lock screen picture with “Get fun facts, tips, tricks and more on your lock screen” turned on it will revert back to the default.

We fixed an issue where the positions of desktop icons get jumbled up after switching DPI settings from 100% to 150% or 175%.

We also fixed an issue where pasting files into a new .zip file (compressed folder) in File Explorer by either right-clicking or Control-V would not work. You should be able to paste tiles into new .zip files just fine now.

Known issues:

If you choose “Reset This PC” under Settings > Update & Security > Recovery – your PC will be in an unusable state. There is no workaround if your PC gets into this state and you will need to reinstall Windows. This issue will be fixed in the next build. You can still rollback to the previous build if for some reason this build doesn’t work out for you. This bug also existed in Build 14251 so please avoid resetting your PC on these 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 “\Microsoft\Windows\WS\WSRefreshBannedAppsListTask” /F. This issue will be fixed in the next build.

The front-facing camera is unusable on PCs with Intel RealSense resulting in being unable to use Windows Hello or any other apps that utilize the front-facing camera.

After logging in to your PC, you may hit a UI issue in which Airplane Mode will incorrectly show as “on” even though your PC’s Wi-Fi is powered on. This is due to a timing issue between how the UI communicates and waits for the underlying platform to respond. The UI for Airplane Mode essentially does not wait long enough for the device’s physical radios to power on before reporting the current state. You can toggle the Airplane Mode on and off to get Airplane Mode back to showing the correct state.

As always – thank you for being Windows Insiders and make sure to send us feedback on any issues you run into with this build in the Windows Feedback app.

We know a lot of Windows Insiders will be celebrating the Lunar New Year this coming weekend. Building off our Ninja Cat heritage, we wanted to provide a fun new set of images to celebrate the Year of the Monkey – you can click here to download. Happy Year of the Monkey from the Windows Insider Program!

Thanks,

g