Microsoft today released Windows 10 Insider Preview build to Insiders in the Fast ring. Here’s a look at what to expect.
Microsoft today is releasing Windows 10 preview build 19613 to Insiders in the Fast ring. This release follows up last week’s build 19608 which had a few front-facing features. Today’s release doesn’t contain many new features (other than some Cortana app improvements) but does include a few fixes. Here’s a look.
Windows 10 Preview Build 19613
Here is the list of fixes contained in today’s build:
- We fixed an issue that was causing app icons in the taskbar to not display correctly, including defaulting to the .exe icon. This issue may have also caused some Insiders to have more reliability issues with explorer.exe.
- We fixed an issue impacting Windows Forms applications where the ImmSetOpenStatus() API wasn’t changing the IME mode correctly when setting focus to text fields while using the new Japanese or Chinese IMEs.
- We fixed an issue from recent builds for Insiders with multiple monitors, resulting in Visual Studio sometimes not responding to clicks.
- We fixed an issue where the doskey / listsize command had no effect.
- We fixed an issue where the doskey /reinstall command killed the commandline session rather than reloading doskey.
- We fixed an issue that could result in Settings crashing when uninstalling a font.
- We fixed an issue impacting some users that could result in Task Manager always showing 0 seconds for Last BIOS Time.
- We’ve made some improvements to address an underlying issue that could result in a black screen for some users for a while after logging in. If you continue seeing this issue, please try pressing WIN+Shift+Ctrl+B and then log feedback in the Feedback Hub.
Remember that Insider builds are meant for coders, IT admins, and Windows enthusiasts who want to test out new features and submit feedback to Microsoft.
These builds are not meant for inexperienced users. And not meant to be installed on your primary production system. Insider builds contain many stability issues.
For more on this build’s full list of changes, known issues, and workarounds make sure to read Microsoft’s full blog post.