Fixes

• We fixed an issue where Sticky Notes windows couldn’t be moved.
• We fixed an issue resulting in language packs failing to install on the previous build. Anyone impacted by this may have noticed some parts of the UI weren’t displaying in your preferred language.
• We fixed an issue resulting in Task Manager showing an incorrect icon for Microsoft Edge Canary.
• We fixed an issue resulting in the Snip & Sketch App launching in the background instead of foreground (on top of all windows) when the app was invoked via pen click.
• We fixed an issue where using the arrow keys in the taskbar volume flyout was unexpectedly backwards in Arabic, inconsistent from the direction it went in other slider controls.
• We’ve done some work to improve the performance when loading the Windows Update history page.

Known issues

• We’re aware Narrator and NVDA users that seek the latest release of Microsoft Edge based on Chromium may experience some difficulty when navigating and reading certain web content. Narrator, NVDA and the Edge teams are aware of these issues. Users of legacy Microsoft Edge will not be affected. NVAccess has released a NVDA 2019.3 that resolves the known issue with Edge.
• We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.
• The Documents and Downloads sections under Privacy show a broken icon next to their page name (just a rectangle).
• We’re investigating reports that app icons in the taskbar are having rendering issues, including defaulting to the .exe icon.
• We’re investigating reports that the battery icon on the lock screen always shows close to empty, regardless of actual battery levels.
• We’re investigating reports of IIS configuration being set to default after taking a new build. You will need to back up your IIS configuration and restore it after the new build is installed successfully.
• Quickly switching between WSL distros using the File Explorer integration could cause a transient access error. We’ve identified the cause of this issue and are releasing a fix soon.