Microsoft today released Windows 10 19H1 Insider Preview Build 18219. This build does not really pack a lot of new features, and mainly comes with some general improvements. Have a look below for the general fixes and known issues before you go about installing on your PC.
General changes, improvements, and fixes for PC:
- We fixed an issue resulting in Notepad’s “Search with Bing” feature searching for “10 10” instead of “10 + 10” if that was the search query. We also fixed an issue where accented characters would end up as question marks in the resulting search.
- We fixed an issue where Ctrl + 0 to reset the zoom level in Notepad wouldn’t work if the 0 was typed from a keypad.
- We fixed an issue resulting minimized apps having squished thumbnails in Task View.
- We fixed an issue resulting in the tops of apps in tablet mode being clipped (i.e. missing pixels).
- We fixed an issue where the taskbar would stay on top of full-screened apps if you had previously hovered over any grouped taskbar icon to bring up the extended list of previews, but then clicked elsewhere to dismiss it.
- We fixed an issue where the icons in the Microsoft Edge extension pane were drawing unexpectedly close to the toggles.
- We fixed an issue where Find on Page in Microsoft Edge would stop working for open PDFs once the PDF had been refreshed.
- We fixed an issue where Ctrl-based keyboard shortcuts (like Ctrl + C, Ctrl + A) didn’t work in editable fields for PDFs opened in Microsoft Edge.
- We fixed the issue where if the Narrator key is set to just Insert, sending a Narrator command from a braille display should now function as designed regardless if the Caps Lock key is a part of the Narrator key mapping.
- We fixed the issue in Narrator’s automatic dialog reading where the title of the dialog is being spoken more than once.
- We fixed the issue where Narrator won’t read combo boxes until Alt + down arrow is pressed.
- If you encounter hangs running WSL in 18219, a system reboot will correct the issue. If you’re an active user of WSL you may want to pause flighting and skip this build. We’re working on a fix.
- There are some improvements in this build but the dark theme File Explorer payload mentioned here is not there yet. You may see some unexpectedly light colors in these surfaces when in dark mode and/or dark on dark text.
- When you upgrade to this build you’ll find that the taskbar flyouts (network, volume, etc) no longer have an acrylic background.
- When you use the Ease of Access Make Text bigger setting, you might see text clipping issues, or find that text is not increasing in size everywhere.
- When you set up Microsoft Edge as your kiosk app and configure the start/new tab page URL from assigned access Settings, Microsoft Edge may not get launched with the configured URL. The fix for this issue should be included in the next flight.
- You may see the notification count icon overlapping with the extension icon in the Microsoft Edge toolbar when an extension has unread notifications.
- On Windows 10 in S Mode, launching Office in the Store may fail to launch with an error about a .dll not being designed to run on Windows. The error message is that a .dll “is either not designed to run on Windows or it contains an error. Try installing the program again…” Some people have been able to work around this by uninstalling and reinstalling Office from the Store. If that doesn’t work, you can try to install a version of Office not from the Store.
When using Narrator Scan mode you may experience multiple stops for a single control. An example of this is if you have an image that is also a link. This is something we are actively working on.
- When using Narrator Scan mode Shift + Selection commands in Edge, the text does not get selected properly.
- We’re investigating a potential increase in Start reliability and performance issues in this build.
In addition to the known issues above, there is still an ongoing problem where installing any recent builds from Fast Ring and switching to Slow Ring will disable developer mode. Microsoft is still working on this issue, and we hope that it is addressed in an upcoming build.