Microsoft today released Windows 10 preview build 20251 to Insiders in the Dev Channel. Here’s a look at what’s new.
Microsoft today is releasing Windows 10 preview build 20251 to Insiders in the Dev Channel. This build follows up last week’s build 20241. Today’s release contains no new front-facing features but it does contain a list of fixes. Here is a look at what you can expect.
Windows 10 Build 20251
Here is the list of fixes contained in today’s new release:
- We fixed an issue resulting in the background of some dialogs to unexpectedly appear grey instead of white in the last couple flights.
- We fixed an issue resulting in the taskbar occluding the Power button in the Start menu for some Insiders recently.
- We fixed an issue resulting in some Insiders seeing a SYSTEM THREAD EXCEPTION NOT HANDLED bug check.
- We fixed a crash with opengl32.dll.
- We fixed an issue that could result in the Settings app hanging when checking for updates right after upgrade.
- We fixed an issue that could result in the Settings app sending a notification that just said “new notification”.
- We fixed an issue resulting in the Search Indexer not being able to retrieve metadata from HEIF and WebP files, so you couldn’t search for those files using metadata like date taken.
- We fixed an issue resulting in the Cast to Device option in Movies & TV (and other media playback apps) not taking any action when clicking on a listed device in recent builds.
- We fixed an issue in recent builds that could result in the screen you were projecting with Miracast freezing shortly after connecting.
Keep in mind that Insider builds are meant for coders, IT admins, and Windows 10 enthusiasts who want to test new features and submit feedback to Microsoft.
These builds are not meant for inexperienced users. They are also not meant to run on your primary production machine. Insider builds contain many known stability issues that can cause your system to become unstable or even crash.
For more on this build’s full list of changes, known issues, and workarounds make sure to read Microsoft’s full blog post.