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

Today, Microsoft released Windows 10 for PCs build 17728 to the Fast ring, and the most notable new feature is Your Phone, which will actually be coming soon. The feature will allow you to connect your PC to your phone, sending texts, dragging and dropping from the photo gallery, and so on.

But of course, it comes with a long list of fixes, improvements, and known issues. Here's what got fixed and improved in Windows 10 build 17728:

  • We fixed the issue resulting in the Clock & Calendar flyout sometimes not appearing until you clicked Start or the Action Center. This same issue impacted both notifications and the taskbar jump lists appearing. Thank you to all the Windows Insiders who gave feedback on this issue.

  • We fixed an issue resulting minimized apps having squished thumbnails in Task View.

  • We fixed an issue where when open Task View would crash if you pressed Alt+F4 and Timeline was enabled.

  • We fixed an issue where Timeline’s scrollbar didn’t work with touch.

  • We fixed an issue where the top border of UWP apps would still be accent colored even if having an accent colored border was disabled in Settings.

  • 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.

  • As some keen eye’d Insiders noticed, we’ve been working on our scaling logic and you should find apps resize better now after monitor DPI changes. As always, we appreciate feedback in this space, so let us know if you have any issues.

  • 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 an issue where the icons in the Microsoft Edge extension pane were drawing unexpectedly close to the toggles.

  • We fixed an issue where the enabled/disabled state of Fast Startup would be reset to default after upgrading. After upgrading off of this build your preferred state will persist.

  • We fixed an issue where the Windows Security icon in the taskbar notification area (systray) would become a little bit blurrier every time there was a resolution change.

  • We fixed an issue where the USERNAME environment variable was returning SYSTEM when queried from an un-elevated Command Prompt in recent builds.

  • 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.

Here are the known issues:

  • 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.

  • There is an issue impacting WDAG, Remote Desktop and Hyper-V. Remote Desktop Client (mstsc.exe) users will see a misleading error dialog complaining about low virtual memory when a connection is being established. As a workaround, they can ignore that error dialog by just leaving it there. If they dismiss the error dialog, the connection will be severed. And users won’t be able to use enhanced session in Virtual Machine Connection (vmconnect.exe). As a workaround, they can stick with the non-enhanced session.

  • 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 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.

  • 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.

There's also 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.

And of course, Microsoft would like Fast ring Insiders to participate in the latest Bug Bash, which started on Friday and runs until August 5. All you have to do is sign into the Feedback Hub and complete Quests and Surveys.

If you're on the Fast ring, you can install today's build by going to Settings -> Update & security -> Windows Update -> Check for updates. If not, you can go to the Windows Insider Program tab and click Get started.

Report a problem with article
1533068919_screen_shot_2018-07-31_at_1.27.31_pm
Next Article

Honor's Note 10 phablet makes its long awaited debut; 6.95-inch display and 5,000mAh battery

1517951636_rs5-pc-a
Previous Article

Microsoft releases Windows 10 build 17728 to the Fast ring with Your Phone coming soon

0 Comments - Add comment

Advertisement