Microsoft has released a new build to Windows Insiders today, and like all new builds that bring new features and improvements, also comes with a number of changes and known issues to be fixed in a future build.
- We fixed an issue resulting in PDFs opened in Microsoft Edge not displaying correctly (small, instead of using the entire space).
- We fixed an issue resulting in mouse wheel scrolling in many UWP apps and XAML surfaces being unexpectedly fast in recent builds.
- We’ve made some updates to the taskbar to reduce the number of times you may see the icons redraw. Most noticeably when interacting with the recycle bin, although in other scenarios as well.
- Antivirus apps must run as a protected process to register with Windows and appear in the Windows Security app. If an AV app does not register, Windows Defender Antivirus will remain enabled.
- We fixed an issue resulting in the System unexpectedly consuming a high amount of CPU for prolonged periods of time when enumerating Bluetooth devices.
- We fixed an issue resulting in Cortana.Signals.dll crashing in the background.
- We fixed an issue that caused Remote Desktop to show a black screen for some users. This same issue could also cause freezes over Remote Desktop when using VPN.
- We fixed an issue resulting in mapped network drivers potentially displayed as Unavailable when using the net use command, and displaying a red X in File Explorer.
- Improved compatibility of Narrator with Chrome.
- Improved performance of Magnifier centered mouse mode.
- We fixed an issue where the Pinyin IME would always show English mode in the taskbar, even when typing in Chinese in the previous flight.
- We fixed an issue resulting in languages showing an unexpected “Unavailable input method” in their list of keyboards in Settings if you added the language via Language Settings in recent flights.
- Thanks everyone who’s shared feedback about the new Japanese Microsoft IME introduced with Build 18272. For the moment the IME version will be returning to the one that shipped with the October 2018 Update while we take your feedback into consideration.
- We’ve added support for LEDBAT in uploads to Delivery Optimization peers on the same LAN (behind the same NAT). Currently LEDBAT is only used by Delivery Optimization in uploads to Group or Internet peers. This feature should prevent congestion on the local network and allow peer-to-peer upload traffic to back off instantly when the network is utilized for higher priority traffic.
Among those issues includes an issue that causes the Settings app to crash when changing passwords, checking storage on external drives, or when opening Speech Settings. Additionally, Windows Security has issues preventing it from checking its virus protection status, and Dynamic Lock has been disabled in this build due to a “merge conflict.” Here’s the full list.
- The hyperlink colors need to be refined in Dark Mode in Sticky Notes if the Insights are enabled.
- Settings page will crash after changing the account password or PIN, we recommend using the CTRL + ALT + DEL method to change the password
- Due to a merge conflict, the settings for enabling/disabling Dynamic Lock are missing from Sign-in Settings. We have a fix, which will flight soon.
- Settings crashes when clicking on the “View storage usage on other drives” option under System > Storage.
- The Windows Security app may show an unknown status for the Virus & threat protection area, or not refresh properly. This may occur after upgrade, restart, or settings changes.
- Delete previous version of Windows in Configure Storage Sense is not selectable.
- Settings will crash when opening Speech Settings.
- Insiders may see green screens with error System Service Exception in win32kbase.sys when interacting with certain games and apps. We have a fix that will flight in an upcoming flight, we appreciate your patience.
- There’s an update block for this build in place for a small number of PCs that use Nuvoton (NTC) TPM chips with a specific firmware version (184.108.40.206) due to a bug causing issues with Windows Hello face/biometric/pin login not working. The issue is understood and a fix will flight to Insiders soon.
Microsoft will continue to refine the Windows 10 experience as we get closer to the next major release of Windows 10, which is currently under the codename of 19H1. For now, we encourage you to share your experience and what issues you face in this build in the comment area below.Further reading: 19H1, build 18290, Known Issues, Windows 10