Here are the known issues in Windows 10 Insider Redstone Preview build 14295

Mark Coppock

It wouldn’t be a Friday without a new Windows 10 Insider build, or so it seems sometimes. Build 14295 was released this morning, and although it didn’t introduce any new features, it did offer up a few fixes. Of course, no new build would be complete without some known issues.

Without further ado, here are the known issues in build 14295:

Known issues for PC

  • We are aware of issues with Narrator and other screen reader apps being unable to read the menu options in the Feedback Hub, as well as issues with Narrator not reading selected text in the Feedback Hub, Cortana, and other apps. We’re working diligently to fix these bugs as soon as possible and apologize to Insiders impacted by this.
  • If you use Hyper-V and have a Virtual Switch configured for your network adapter, you may see an error indicator (red-colored “X”) for your network adapter in the notification area of your taskbar. The error indicator is incorrect and your network adapter should continue to work just fine.
  • On some PCs with TPM chips, such as the ASUS Zenbook UX31, you may experience glitchy audio and jumpy movement when using the trackpad due to the “tpm-maintenance” task running constantly in the background instead of once per boot-up like it should. As a temporary workaround, you can disable the tpm-maintenance task in Task Scheduler (under \microsoft\windows\tpm).
  • PCs that use Windows Hello or a PIN to sign-in to the device will launch the Microsoft Passport service. When this happens, there is an issue in this build where Bluetooth will then repeatedly scan for devices. This causes a few issues on the PC including reduced battery life, audio glitches, responsiveness issues with Bluetooth keyboards and mice, a decrease in Wi-Fi throughput on Wi-Fi/Bluetooth combo chipsets, and a decrease in throughput for Bluetooth file transfers. As a workaround, you can disable the Microsoft Passport (NgcSvc) service by opening an elevated Command Prompt, run “reg add HKLM\System\CurrentControlSet\Services\NgcSvc /v Start /t REG_DWORD /d 0x4 /f” and then reboot. However, you will not be able to use Windows Hello or a PIN to sign-in to your device. The service will be re-enabled again when you update to the next build.
  • After upgrading to this build from Build 14291, attempting to connect to a Miracast receiver the connection will fail. The workaround to get out of this state is to go to this registry key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters” and select “StandaloneDhcpAddress” and change the value from “192.168.173.1” to “192.168.137.1” (value type is REG_SZ). Then retry the connection to the Miracast receiver.
  • We are seeing reports of some apps such as QQ crashing. We are currently investigating, and this bug may also impact older apps such as Windows Live Mail and Expression Encoder 4.

Known issues for Mobile

  • After updating to the most recent builds from our Development Branch, a system API failure occurs after the update that causes the Microsoft Band 1 or 2 to have sync issues. To get out of this bad state, you can reset your phone on this build, re-pair your Microsoft Band, and syncing should work again.
  • After upgrading to this build from a previous build from our Development Branch, attempting to connect to a Miracast receiver the connection will fail. There is no workaround for this issue unfortunately on Mobile.
  • The Gadgets app will not detect the Microsoft Display Dock on phones running Windows 10 Mobile Insider Preview builds, and thus cannot update the firmware version. If you have a dock which has already been updated to version 4 then this will not affect you. If you have a dock that has not been updated, then you may experience some minor issues with USB-C stability. You will still be able to use your dock and Continuum.

As always, make sure none of these issues are important before hitting that update button. Let us know in the comments below if you run into any other issues.