When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

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

Microsoft released a new Windows 10 build to the Fast ring a little earlier than usual today, after a week with no builds. Build 18932 includes some new Eye Control improvements and notification settings, but it also comes with a pretty long list of fixes issues.

Most notably, Microsoft is seemingly converging settings synchronization engines into a single platform that's more reliable and less complex. For now, that means settings syncing will be disabled in 20H1 builds, but it should be good news for future releases. Here's the full list of improvements:

  • We’re in the process of converging settings sync engines to reduce complexity and improve reliability of sync. As of today, the older settings sync engine will be turned off for 20H1 builds and changes made to settings that have not yet been migrated to the new settings sync engine will stop being sent and received until that work is complete. Some settings may not be migrated. The full list of settings that have been supported for sync are available here, but the list is subject to change during 20H1. Synced settings that are impacted by this change include settings pertaining to taskbar orientation, wallpaper, theming, and others. If there’s a setting you’d like to particularly be prioritized as we work on this, please let us know. Please note, you may notice a one-time receival of synced settings changes after you upgrade or reset your PC, but after that it will stop.
  • We’ve updated our indexing behavior to exclude common developer folders, such as .git, .hg, .svn, .Nuget, and more by default. This will improve system performance while compiling and syncing large code bases in the default indexed locations such as user libraries.
  • We fixed an issue where the update might have failed the first time you tried to download it with a 0xc0000409 error code.
  • We fixed an issue where recent updates might have failed with a 0x80070005 error code.
  • We fixed an issue for Home editions where some devices couldn’t see the “download progress %” change on the Windows Update page.
  • We fixed a race condition resulting in some Insiders seeing a large number of explorer.exe crashes in recent builds. This is also believed to be the root cause for some Insiders finding that Control Panel wasn’t launching – please let us know if you continue seeing issues after upgrading to this build.
  • We fixed an issue resulting in some Insiders finding that their File Explorer search box was rendering in an unexpectedly small space and crashed when clicked.
  • We fixed an issue where Settings would crash if you tried to add a language on the previous build.
  • In Word, after showing a “flash message” on a braille display, Narrator is now correctly showing just the current heading.
  • We made a small backend change to the updated Windows Ink Workspace to help improve the launch time.
  • We fixed an issue resulting in Task Manager unexpectedly showing 0% CPU usage in the Performance tab.
  • We fixed an issue that could result in a black remote desktop window for a few seconds when disconnecting from a remote desktop session.
  • We fixed a issue resulting in Direct3D 12 games crashing in the previous flight.
  • We fixed an issue that could cause certain apps to crash when you input Asian characters.
  • We fixed an issue for the Chinese Pinyin IME where, if you were in the middle of finalizing a phrase and clicked away, the next thing you typed wouldn’t show the characters.
  • We fixed an issue with the Chinese Pinyin IME where the mouse over highlight could get stuck on a particular candidate in the candidate window.
  • We fixed an issue with the Chinese Pinyin IME where the candidate window wouldn’t display when typing in the Microsoft Edge search box (Ctrl+F).
  • We fixed an issue resulting in not being able to use touch to open context menus on websites in Microsoft Edge after using pinch to zoom in and back out.
  • Narrator search mode will now reset scoping to all elements each time it is opened.
  • The data looks good, so we’re now rolling out the fix for taskbar unexpectedly dismissing when invoking Start if set to autohide to all Insiders in Fast.
  • We fixed an issue where the Bluetooth Hands-Free audio driver (bthhfaud.sys) could get stuck when making or breaking a synchronous connection-oriented (SCO) link to the headset. This would cause all audio on the system to stop working until the system was rebooted.

The build comes with a surprisingly low number of known issues, though some long-standing ones are still here. Here's the full list:

  • If you’re seeing failures installing games via the Xbox app, you can retry the install. If it continues failing, you may want to roll back to Build 18922.
  • There has been an issue with older versions of anti-cheat software used with games where after updating to the latest 19H1 Insider Preview builds may cause PCs to experience crashes. We are working with partners on getting their software updated with a fix, and most games have released patches to prevent PCs from experiencing this issue. To minimize the chance of running into this issue, please make sure you are running the latest version of your games before attempting to update the operating system. We are also working with anti-cheat and game developers to resolve similar issues that may arise with the 20H1 Insider Preview builds and will work to minimize the likelihood of these issues in the future.
  • Some Realtek SD card readers are not functioning properly. We are investigating the issue.
  • Tamper Protection may be turned off in Windows Security after updating to this build. You can turn it back on. In August, Tamper Protection will return to being on by default for all Insiders.

Of course, there may be more issues than the ones listed here. If you want to get Insider builds with less risk, 19H2 builds have started making their way to the Slow ring, so you may want to opt for that. It's worth noting that you won't be able to get 19H2 builds if you've already received updates in the 20H1 cycle. You'll need to roll back to the May 2019 Update in order to do that.

Report a problem with article
Next Article

Pay What You Want for the Complete Linux eBook Bundle

Previous Article

Microsoft rolls out Windows 10 build 18932 to the Fast Ring with Eye Control improvements

Join the conversation!

Login or Sign Up to read and post a comment.

0 Comments - Add comment