News

Microsoft Releases Windows 10 20H1 Build 19013

Microsoft today released Windows 10 20H1 preview build 19013 to Insiders in the Fast ring. Here’s a look at what you can expect.

Microsoft today released Windows 10 20H1 preview build 19013 for Insiders in the Fast ring. This build follows up last week’s build 19008 which mainly included a list of fixes and overall system improvements. This build includes more Kamoji and special characters and WSL changes. Also, some improvements to the Your Phone app. But other than that, it is mainly fixes and overall system improvements.

Note: Microsoft is moving the release date of 20H1 up three months and is set to roll out in December. The company has rearranged its release dates of feature updates to coincide with its Azure cycle. Windows 10 19H2 — November 2019 Update version 1909 — which is essentially a service pack is still set to release next month.

Windows 10 20H1 Preview Build 19013

This build included more “kaomoji” characters. “What are kaomoji? Basically, they’re faces with expressions you can make by combining various characters.”

Here is the list of fixes, changes, and improvements included in this latest Insider release:

  • We fixed an issue resulting in frames being skipped, starting with Build 19002, when running games and videos fullscreen.
  • We fixed an issue where initiating “Reset this PC” with the cloud download option wasn’t working when started from Windows RE.
  • We fixed an issue resulting in preinstalled apps (like Calculator) and other UWP apps being missing from the Apps & Features page in Settings.
  • We appreciate your patience while we worked on our sync engine. As of this build, wallpaper and theme syncing is now up and running again.
  • We fixed an issue resulting in Wi-Fi unexpectedly resetting (turning off and back on) frequently in recent flights.
  • We fixed an issue where Wi-Fi Settings might get stuck saying Connecting, even though the network flyout (correctly) indicated that you were Connected.
  • We fixed an issue where an update being temporarily suspended would result in an 0xc19001e1 error being displayed in Windows Update history.
  • We fixed an issue resulting in the “Open location” search result option not working if the search result was a folder.
  • We fixed an issue where if you moved Cortana’s window to certain places on your screen, and then closed the window, the minimize animation wouldn’t go towards Cortana’s icon on the taskbar.
  • We fixed an issue resulting in File Explorer not rendering correctly sometimes when using multiple monitors with different DPIs on the previous flight.
  • We fixed an issue where you could get into a state where it wasn’t possible to set focus to File Explorer’s search box in order to type your query.
  • We fixed an issue that could result in the app thumbnail disappearing when you right clicked it in Task View.
  • We fixed an issue that could result in the Send Message button in certain notifications not being visible when using High Contrast White.
  • We fixed an issue where the notification following WIN+Shift+S might have a blank space for the screenshot (rather than actually displaying the screenshot).
  • We fixed an issue resulting in Resource Manager unexpectedly not showing any disk activity.
  • We fixed an issue where, if you called SUBST with a path ending with a \ it would give a Path not found error.
  • We fixed a memory leak with running apps that repeatedly sent calls to adjust gamma.
  • Some of you have reached out about when trying to shutdown, seeing a message saying that an app named “G” was preventing shutdown. We investigated and found an issue where windows related to GDI+were only referenced as “G.” We’ve fixed this, so going forward, these will now have the name “GDI+ Window (<exe name>)”, where <exe name> will show the .exe name of the app using GDI+.
  • We fixed an issue resulting in speechruntime.exe using an unexpectedly high amount of CPU on the previous flight.
  • We fixed an issue resulting in Bluetooth devices potentially not reconnecting as expected after closing then reopening the device lid for certain devices.
  • We fixed an issue resulting in the Surface Dial not scrolling in recent builds if you switched to something like zoom and then back to scrolling.
  • Thank you Insiders who shared feedback about the 2-in-1 convertible tablet experience improvements we discussed here. For the time being, we’re returning to the current experience in retail.
  • We fixed an issue where Narrator would sometime report focus as the page instead of reporting the actual focused control within Chrome.
  • We fixed an issue where Narrator would not automatically start reading the Narrator user guide webpage and the YouTube webpage.
  • We corrected Narrator’s “Next Table” command so that it would work in Excel.
  • We fixed an issue where the text cursor indicator was visible on top of the lock screen background picture.
  • We fixed an issue where the text cursor indicator preview wasn’t displaying correctly in Settings when using dark theme.
  • We fixed an issue where when using dark theme, the hardware keyboard text prediction candidate window was unreadable due to black text on a dark grey background.
  • We fixed an issue that could result in the touch keyboard flickering when inputting emoji.
  • We fixed an issue where English punctuations were outputted when using the Chinese Pinyin and Wubi IMEs, even if input mode was set to Chinese under the default IME settings. Thanks for your feedback.
  • We’ve fixed an issue where the character width of alphanumeric characters when using the Traditional Chinese Bopomofo IME would change from half width to full width unexpectedly in some input fields. Thanks for reporting it! If you feel this issue hasn’t been fully addressed in the new version of Bopomofo IME, please let us know your feedback.
  • We’ve fixed an issue where after successfully updating to a new build, the Windows Update Settings page may have shown the same build needed to be installed.
  • We’ve fixed an issue where Optional drivers were failing to install.

Remember that with Insider builds you can expect a lot of bugs and other issues for both users and developers alike. Make sure to read Microsoft’s full blog post for all changes, known issues, and workarounds.


Click to comment
To Top