Here's what's fixed, improved, and still broken in Windows 10 build 17730

Today, Microsoft released Windows 10 build 17730 to the Fast ring. Along with some minor new features, the big deal is that Your Phone is finally active, allowing users to connect with their phone and send text messages, interact with their image gallery, and more.

But as always, there's a long list of fixes, improvements, and known issues. Here's what got fixed and improved in build 17730:

  • We have fixed the issue impacting WDAG, Remote Desktop and Hyper-V. Remote Desktop Client (mstsc.exe) users should no longer see an error dialog complaining about low virtual memory when a connection is being established. And users can use enhanced sessions in Virtual Machine Connection (vmconnect.exe) again.

  • Thank you everyone who has given us feedback on the “Block Suspicious Behaviors” feature that was recently added to Windows Security. For the time being we’re removing it from the build while we work on addressing some of the things you shared with us.

  • We fixed an issue resulting in the volume slider in certain apps performing poorly with touch in recent flights.

  • We fixed an issue resulting in certain apps, like the Twitter app, not rendering content when navigating after a while.

  • We fixed an issue where expanding the Driver Updates dropdown in View Update History in Settings didn’t list anything (even when there were items to list) in recent builds.

Here are the general known issues:

  • Clicking a link to launch one app from another app may not work for some Insiders. We’re investigating.
  • We’re progressing in our work on adding dark theme in File Explorer and the Common File Dialog, but 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.
  • You may still 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.
  • 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 Microsoft Edge, the text does not get selected properly.
  • We’re investigating a potential increase in Start reliability and performance issues in this build.
  • After setting up a Windows Mixed Reality headset for the first time on this build with motion controllers, the controllers may need to be re-paired a second time before appearing in the headset.
  • When using a Windows Mixed Reality immersive app, saying “Flashlight on,” may fail to activate the flashlight feature even though the status appears as active on the Start menu.

Finally, there's still one known issue 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 Windows 10 Redstone 5 development begins to wind down and we head into the final stretch before RTM, you can expect to see more frequent builds, such as how the Fast ring got two this week. You can also expect the list of known issues to get shorter and shorter.

Redstone 5 will likely be finalized next month, before rolling out generally in October. If you're on the Fast ring, you can install build 17730 by heading to Settings -> Update & security -> Windows Update -> Check for updates. If not, go to the Windows Insider Program tab to get started.

Report a problem with article
Previous Story

Microsoft releases Windows 10 build 17730 to the Fast ring with Your Phone and more

Next Story

T-Mobile debuts LG Q7+ with Full Vision display, USB Type-C and more

2 Comments - Add comment

Advertisement