It's Wednesday again, and that means Microsoft is rolling out a new build of Windows 10 to Insiders in the Dev channel. This week, we're getting build 20190, and it includes a couple of new features, including a new post-update experience and improvements to the graphics settings.
Builds in the Dev channel are no longer tied to a specific Windows 10 release, which means that new features may or may not make it to the next feature update released to the general public. Features will be brought into the Beta channel whenever Microsoft is ready to make them public, and from there they'll be tested with that group of Insiders until they're fleshed out.
Of course, in addition to a couple of new features, today's build comes with its usual array of fixes and improvements to make the experience a little better. Here's what's changed:
Based on feedback, we’re updating the new Japanese IME to support switching between Hiragana and Katakana by using CTRL + CAPSLOCK and ALT + CAPSLOCK (respectively), as was supported with the previous version.
- We fixed a Windows Subsystem for Linux 1 related error that would output: ‘The I/O operation has been aborted because of either a thread exit or an application request’. Please see this Github issue for details.
- We fixed an issue that could result in explorer.exe being unresponsive on touch-capable devices after resuming from hibernation.
- We fixed an issue with the new search box in the default apps settings pages, where search results would appear to draw on top of one another when deleting characters from the search box.
- We fixed an issue where if you switched to an English keyboard using WIN + Space and then switched back to the Chinese Pinyin IME, typed punctuations would Chinese even if “Use English punctuations when in Chinese input mode” was enabled.
- We fixed an issue where when Narrator was enabled it could result in the on-screen PIN pad unexpectedly appearing when focus is set to the login screen.
- We fixed an issue resulting in Features on Demand (FOD) failing to enable with error 0x8000FFFF in recent builds. This is also believed to be the root cause for some Insiders finding that the sfc /scannow command would repeatedly fail citing a pending reboot.
- We fixed and issue that could result in the calling window (for example, Microsoft Edge) hanging if an authentication prompt was raised and then not interacted with and timing out.
Despite the new fixes, there are still a few known issues with this release, which you'll need to be aware of before jumping in:
- We’re working on a fix for an issue where some Microsoft Store games protected with Easy Anti-Cheat may fail to launch.
- We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.
- We’re working on a fix for an issue where the min/max/close buttons are stuck in their original positions after resizing a UWP app. If you move the app window the position should update.
- We’re investigating reports that the new taskbar experience for pinned sites isn’t working for some sites.
- We’re working on a fix to enable live preview for pinned site tabs.
- We’re working on enabling the new taskbar experience for existing pinned sites. In the meantime, you can unpin the site from the taskbar, remove it from the edge://apps page, and then re-pin the site.
- We’re working on a fix for an issue where pinned sites don’t show all open tabs for a domain. In the meantime, you can fix this by pinning the site’s homepage rather than a specific page (e.g. pin microsoft.com rather than microsoft.com/windows).
- We’re working on a fix for an issue where Alt + Tabbing to a browser tab sometimes moves the previously active browser tab to the front of the Alt + Tab list as well.
- The letter headers in the Start menu’s all apps list have unnecessary left padding when the all apps list was set to hidden.
The build should install automatically if you're enrolled in the Dev channel, but you can check for updates right now if you don't want to wait.
1 Comment - Add comment