After Microsoft decided not to release its weekly build of Windows 10 on Wednesday due to a breaking bug, the company still managed to push one out before the end of the week. Build 20197 includes a single new feature, bringing disk management into the Settings app, but it also includes a long list of fixes and improvements.
First, there’s a slew of changes to the behavior of certain features. For example, only up to five Microsoft Edge tabs can now show in the task switching interface (Alt-Tab). Here’s the full list:
- We’re updating the ALT + Tab behavior with Microsoft Edge tabs to now have a default of displaying at most 5 tabs, rather than any recent tabs. If at any point you’d like to change this, you can under Settings > System > Multitasking.
- We’re exploring including a Web Browsing section in the Settings header, and Insiders may start to see this.
- Going forward only the currently active profile picture will display under Your Info in Settings.
- Based on feedback we’re turning off ESENT Warning Event ID 642.
- It’s now possible to select the new Microsoft Edge as your desired app in Assigned Assess.
- We’ve updated Narrator so that now when using the Microsoft Pinyin IME, Narrator is able to distinguish candidate characters/words by providing detailed reading information.
There’s also a very long list of fixes:
- We fixed an issue where the letter headers in the Start menu’s all apps list had unnecessary left padding when the all apps list was set to hidden.
- We fixed an issue where ALT + Tabbing to a browser tab sometimes moved the previously active browser tab to the front of the Alt + Tab list as well.
- We fixed an issue where if you’d pinned a website to your taskbar and then moved your Microsoft Edge window with that site open over to a different virtual desktop, the pinned sit wouldn’t show the corresponding open tabs on that new desktop.
- We fixed an issue where the sysprep command was failing with the error 0x80073CFA in the last few builds.
- We fixed an issue where Group Policy Editor was showing a popup error about WnsEndpoint_Policy in the last few flights.
- We fixed an issue where the Get-Volume PowerShell command wasn’t recognizing volumes in the exFAT format.
- We fixed an issue impacting explorer.exe launch performance when booting up and logging in for the first time.
- We fixed an issue where pinned File Explorer folders in Start would appear with a darker background than other tiles in light mode.
- We fixed a race condition that could result in the Font Settings page crashing.
- We fixed an issue where Font Settings and Themes Settings were displaying the old style of Microsoft Store icon.
- We fixed an issue that could result in the Network Status page in Settings showing an old network name, rather than the one that you’re currently connected to and inconsistent with what the network flyout displayed.
- We fixed an issue resulting in certain VPNs with the option “Automatically use my Windows log-on name and password (and domain, if any) enabled no longer connecting automatically.
- We fixed an issue resulting in some Insiders experiencing a bugcheck in recent builds citing a hyperguard violation.
- We fixed an issue when using the search box in File Explorer, where pressing the enter key would result in keyboard focus jumping to the quick access section of the navigation pane rather than to the search results.
- We fixed an issue with the Microsoft Pinyin IME, where typing certain phrases would result in the candidate pane unexpectedly dismissing.
- We fixed an issue with the Microsoft Pinyin IME, where when using double pinyin style, when typing something like “goldb;du” where the first candidate could be an English word the conversion wouldn’t work.
- We fixed an issue when typing with the Japanese IME that could result in not being able to input symbols using Shift+
into password fields sometimes.
- We fixed an issue that could result in certain apps crashing when typing incorrect combinations with the Chinese Traditional DaYi IME.
- We fixed an issue with the Microsoft Bopomofo IME where it was consuming Shift key up events when they resulted in IME mode toggle actions.
- We fixed an issue that could result in a CTFMON.exe when changing focus to certain apps (like Outlook) while typing with an IME.
- We fixed an issue where ImmGetCompositionString wasn’t returning the correct IME composition string for YOMI text fields.
- We fixed an issue where the Windows key on the full touch keyboard layout wouldn’t become highlighted after tapping on it in recent builds.
- We fixed an issue when using Narrator where Scan Mode wouldn’t stay off in Microsoft Teams.
- We fixed an issue resulting in Microsoft Flight Simulator failing to launch on the previous two flights with an error citing: “The filename, directory name, or volume label syntax is incorrect”.
Despite that, however, there are still a few known issues with this build. A notable one is that games from the Microsoft Store that are protected by Easy Anti-Cheat may fail to launch, but there’s more:
- 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).
Even though there’s a few issues with this one, the amount of fixes make it a build you might not want to miss if you’re already in the Insider program. Of course, issues are likely to come and go during the development period, especially seeing as the next major feature update is at least a few months away.