Fixes and Known issues in Windows 10 Build 16193

Microsoft today released yet another Windows 10 Insider Preview version. Windows 10 build 16193 which represents the upcoming Windows 10 Fall Creators Update, code name "Redstone 3", is available now for Fast Ring Insiders.

This build comes with the following fixes and improvements:

  • PC Reset via Settings > Update & security > Recovery works again on non-English Insider Preview builds.
  • Navigating to Settings > Personalization > Lock screen should no longer crash Settings app.
  • We fixed an issue where Settings would crash on launch for Insiders using certain display languages, including Russian, French, Polish and Korean. If you were impacted by this on Build 16188, that means you won’t be able to open Windows Update to check for updates. However, your PC will download the new build in the background. Once the build is downloaded and staged, your device should automatically restart to install it when idle and outside of your configured active hours. Or you could go to Start and Power and choose to Update and Restart to install the build.
  • We fixed the issue causing XAML designers in Visual Studio and Blend for Visual Studio to show an exception when a XAML file from a Universal Windows Platform project is opened.
  • We fixed an issue resulting in some fonts not rendering properly in Greek or other single-byte system locales such as Hebrew or Arabic.
  • We fixed an issue where the “clear all” button in Action Center wouldn’t work if a notification had been expanded.
  • You can now use Ctrl + Win + N to directly open Narrator Settings.
  • We fixed an issue where the Windows Store App Troubleshooter was erroneously showing the message “Not Fixed” instead of “Fixed” after following the steps to troubleshoot the error “Windows Store cache may be damaged”.
  • We fixed an issue from recent flights that could lead to the PC no longer recognizing any USB device until the USB Root Hub had been disabled and re-enabled in Device Manager.

The list of known issues looks as follows:

  • Windows Defender Application Guard (WDAG) will fail to work on touch PC’s, showing a solid black window on launch. Non-touch enabled devices should not experience the issue. A temporary workaround if you would like to use WDAG is to go to Device Manager, expand Human Interface Devices and disable the “HID-compliant touch screen” and “Intel Precise Touch Device” if they are present. After a reboot try WDAG again. Re-enable these devices to restore touch.
  • [DEVELOPERS] The XAML designer in Visual Studio 2017 hits an error causing a squiggle error under ThemeResource references to XAML’s generic.xaml resources.
  • Some Insiders have reported seeing this error “Some updates were cancelled. We’ll keep trying in case new updates become available” in Windows Update. See this forum post for more details.
  • Surface 3 devices fail to update to new builds if a SD memory card is inserted. The updated drivers for the Surface 3 that fix this issue have not yet been published to Windows Update.
  • Outlook 2016 may hang on launch due to an issue where the spam filter gets stuck reading the Outlook Data File and the UI waits indefinitely for it to return. We’re investigating.
  • We are investigating reports that Microsoft Edge fails to open PDFs with “Couldn’t open PDF. Something is keeping this PDF from opening” error.
  • You will be unable to type in your password to log in to the Facebook, Instagram or Messenger apps. A workaround is to use the “Login with the browser” button.

Source: Microsoft.

Support us

Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options:

If you like this article, please share it using the buttons below. It won't take a lot from you, but it will help us grow. Thanks for your support!

Author: Sergey Tkachenko

Sergey Tkachenko is a software developer who started Winaero back in 2011. On this blog, Sergey is writing about everything connected to Microsoft, Windows and popular software. Follow him on Telegram, Twitter, and YouTube.

2 thoughts on “Fixes and Known issues in Windows 10 Build 16193”

  1. To enable alpha-numeric input in command windows you must run this as administrator:

    Reg.exe add “HKCU\Console” /v “ForceV2” /t REG_DWORD /d “0” /f

Leave a Reply

Your email address will not be published.

Exit mobile version
Using Telegram? Subscribe to the blog channel!
Hello. Add your message here.