A new day, and a new Windows 10 PC build. That’s how fast Microsoft’s promised insider build roll out has been for PCs, and even though these new builds don’t really bring much to the table, it is still appreciative of Microsoft to provide new codes in a rapid manner for devs to play with.
So this new build. numbered 14251, apart from the usual bug fixes, has specifically got some much needed fixes for gamers.
For example, in a big sign of relief, Microsoft has 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.
Apart from this, there are a few fixes in the display section as well. MS has fixed the issue where applications such as Narrator, Magnifier, and third-party assistive technologies may experience intermittent issues or crashes. Also, your File Explorer would not crash now, an issue which had been popping up when DPI settings were at 175%.
Talking about this new cycle of build releases, Microsoft’s Gabe Aul says,
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.
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.
As for known issues, this build has the following ones :
- 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
- 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.
- F12 Developer Tools will not load in Microsoft Edge. Should be fixed in the next build.