Today, Microsoft released the first Windows 10 build from the 19H1 development branch, along with a new Redstone 5 build for the Fast ring. The two builds - 17723 and 18204 - are the same in terms of new features, but the latter is a preview of the next version of Windows 10 after the one released this fall.
But alongside of the new features, there are also a whole bunch of fixes, improvements, and known issues. Once again, the notes are the same for both builds. Here's what got fixed and improved:
We fixed an issue resulting in the “…” menu not working in multiple apps (including Microsoft Store, Photos, and Screen Sketch) where clicking on any of the items would just make the menu dismiss.
We fixed an issue where in certain cases on PCs with multiple monitors, all the windows might have appeared shifted “up” and mouse input going to the wrong location.
We fixed an issue where SNMP and the Windows Event Log service might start using an unexpectedly high amount of CPU in the last flight.
We fixed the issue with Windows Defender Application Guard no longer working after installing the Build 17713.1002 Cumulative Update.
We fixed an issue from the last flight where upon rebooting in order to start upgrading to the build, the system would boot back into the current build rather than the new one.
We fixed an issue resulting in upgrades to the previous build failing with error 0x8007001f.
We fixed an issue from the previous flight where Window Recovery Environment (WinRE) would not launch and resulted in “Reset this PC” and “Advanced startup” flows to be broken and appear to do nothing. We also fixed an issue from the flight before last (not visible in the last flight due to the aforementioned bug) where “Reset this PC” would initiate and rollback without completing the intended reset.
We fixed an issue resulting in some laptops experiencing a CRITICAL PROCESS DIED bug check when the PC was put to sleep by closing lid and the connected power disconnected.
We fixed an issue resulting in ShellExperienceHost.exe crashing when trying to pin apps to Start Menu via drag and drop.
We fixed an explorer.exe crash when launching the Default Apps Settings page via WIN+R ‘control /name Microsoft.DefaultPrograms /page pageFileAssoc’.
We fixed an issue where .mkv files were using a generic app icon in File Explorer instead of a thumbnail.
Delivery Optimization Settings now has a new icon.
We fixed an issue where suggestions on the main page of Settings would appear after a delay, making the Settings categories shift unexpectedly.
We fixed an issue where Notification Settings listed every possible quick action in the enable/disable quick actions section, even those not applicable to the PC being used (including two Focus Assist entries).
We fixed an issue where the systray overflow area could end up drawing slightly below the taskbar.
We fixed an issue resulting in the network state in the taskbar potentially becoming stale in recent builds (showing there was no connection when there was, and vice versa).
We fixed an issue where pinging PCs by name on the same LAN would do a case-sensitive name check.
We fixed an issue where using v6v4tunnel to establish a tunnel didn’t work.
We fixed an issue in Command Prompt from the previous flight where if a typed string wrapped around to a second line, you could only delete it up to the line break.
We fixed an issue resulting in Task View / Timeline crashing on launch for some Insiders in recent builds.
We fixed an issue where right-clicking an activity in Timeline was missing the “clear all from day” option.
When you open a PDF using Microsoft Edge, the activity will now be listed in Timeline.
We fixed an issue where sometimes you would see windows unexpectedly quickly reorder after exiting Task View without selecting a window.
We fixed an issue from recent builds where the clock in the taskbar was leaking graphics device context handles (HDCs) every time it redrew, leading to performance issues the longer a PC was running. Multiple factors can impact performance, so if you’re continuing to notice any issues after upgrading to this build, please log feedback including a performance trace with a short repro and description.
We fixed an issue resulting in not being able to distinguish the border between two overlapping Command Prompt windows.
We fixed an issue resulting in the tops of apps in tablet mode being clipped (i.e. missing pixels).
Thanks everyone for sharing your feedback about the new welcome screen string prompting you to lock your PC. For the time being we will be reverting this to the previous string “These updates will protect you in an online world”.
We’ve made some tweaks to the design of the Cortana & Search landing page, specifically in situations where Cortana isn’t enabled/supported.
We fixed an issue resulting in Microsoft Jigsaw hanging on launch in recent builds.
The settings menu in Microsoft Edge (“…”) is now acrylic.
When you right-click a book in the Microsoft Edge Books pane, you’ll now see an option to share the book.
We fixed an issue that could result in Microsoft Edge spellchecking even though spellchecking was turned off in Settings.
We fixed an issue where using the mouse wheel in Microsoft Edge would unexpectedly do a forward/back through browser history if focus was in the address bar and “Scroll inactive windows” was disabled.
We fixed an issue where when using certain sites to listen to music in Microsoft Edge, your mouse might experience a small freeze if moving when the song changed.
We fixed an issue resulting in apps like Adobe XD crashing on keypress in recent flights.
We fixed an issue that could result in a deadlock on certain devices after using the pen to ink.
We fixed an issue where the touch keyboard would still have a launch animation even if “Show animations” was turned off in Ease of Access Settings.
We fixed an issue where launching regedit.exe (or any .exe that requires elevation) from a non-elevated cmd window using the “start” start command produced a “parameter is incorrect” error.
We fixed an issue causing Narrator speech to fade when waking from sleep mode.
We fixed an issue where the error “Your fingerprint couldn’t be recognized. Try using a different finger.” was displaying unexpected characters in place of the apostrophe.
Here are the known issues:
The clock & calendar flyout may not appear until bringing up Start or Action Center (and then they will both appear at the same time). This same issue may also result in notifications not appearing until Start or Action Center is opened.
We’re progressing in our work on adding dark theme in File Explorer and the Common File Dialog – you’ll notice improvements in this build, although we still have a few things left to do. 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.
On Build 17723 (but not Build 18204), 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 the Narrator Quickstart launches, Scan Mode may not reliably be on by default. We recommend going through the Quickstart with Scan Mode on. To verify that Scan Mode is on, press Caps Lock + Space.
When using 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.
If the Narrator key is set to just Insert and you attempt to send a Narrator command from a braille display then these commands will not function. As long as the Caps Lock key is a part of the Narrator key mapping then braille functionality will work as designed.
There is a known issue in automatic dialog reading where the title of the dialog is being spoken more than once.
For more information about Narrator new keyboard layout and other known issues, please refer to (Intro to New Narrator Keyboard Layout doc).
There's also a known issue that's for developers:
If you install any of the recent builds from the Fast ring and switch to the Slow ring – optional content such as enabling developer mode will fail. You will have to remain in the Fast ring to add/install/enable optional content. This is because optional content will only install on builds approved for specific rings.
As always, it's recommended that you read through the known issues before installing a new Windows 10 build.
Microsoft also announced that it will be doing another Bug Bash from July 27 through August 5. During that time, Insiders will be able to complete Quests in the Feedback Hub to find bugs. It will focus on Redstone 5, so presumably, if you're on 18204, you won't see the Bug Bash.
6 Comments - Add comment